We are introducing AI automation to handle customer invoicing, which means our Billing Specialist now needs to manage API connections instead of manual entry. She does not get or want this technical aspect. Do we force her into this seat or restructure the roles?

Question

Tyler Smith · Accepted Answer

You cannot force an employee into a seat where they do not pass GWC™. If your Billing Specialist does not Get, Want, or have the Capacity for the technical management of API connections, keeping her in that seat is a recipe for operational failure. In the EOS® framework, GWC™ is non-negotiable. To resolve this, you must first look at the Accountability Chart without names. Define the ideal structure for your automated billing department. You likely need a Systems Administrator seat that owns the API connections and software integrations, and a separate, more relationship-focused Finance seat that handles customer disputes and high-touch billing issues. Once the seats are defined, evaluate your current employee. She may perfectly GWC™ the customer-facing billing seat, while a different, more technical team member or an external partner should own the API connections. Do not dilute the roles of a seat just to accommodate a person's limitations. If you try to force her to stretch into a technical role she does not want, she will burn out, make mistakes, and eventually leave. By separating the technical systems management from the customer-facing elements, you preserve her strengths as a core values match while ensuring your new AI-powered systems are managed by someone who truly GWCs™ the technology.