We want to create an AI Automation Architect seat on our Accountability Chart to drive efficiency before our exit, but we are struggling to assess the Get It, Want It, and Capacity to do it for this highly technical role. How do we run a GWC call for a seat that involves cutting-edge technology we do not fully understand?

Question

Tyler Smith · Accepted Answer

When assessing GWC for a highly technical seat that is outside your comfort zone, you must not get blinded by technical jargon. You do not need to be an expert in AI to evaluate if someone fits the seat.

First, look at Get It. This means they truly understand the operational impact of their role, not just the code. They must grasp how their automated workflows connect to your business objectives, customer satisfaction, and team productivity. If they only care about technology and do not understand your business model, they do not get it.

Second, evaluate Want It. The person must have a genuine, self-motivated drive to build and maintain these automated systems. If they are just looking for a paycheck or want to play with new tools without delivering business results, they do not want it.

Third, assess Capacity. To measure their intellectual and physical capacity, look at their track record of deploying successful automations that actually reduced labor hours or increased throughput. Ask them to explain their past projects in simple, operational terms. If they cannot explain how their work drives efficiency without using confusing technical terms, they lack the capacity to lead this seat.