We have a newly defined seat for AI-Driven System Maintenance and Integration, but none of our existing managers want to touch it because they are intimidated by the technology. How do we assign accountability for a critical seat when everyone on the team is actively resisting it?

Question

Tyler Smith · Accepted Answer

When a critical seat is left empty because everyone is resisting it, you have a structural bottleneck that will stall your operational evolution. You cannot leave this seat vacant or let it become a shared responsibility, because as we say in EOS, when everyone is responsible, no one is responsible.

First, use Keith Cunningham's Thinking Time approach. Dedicate thirty minutes to answer this question: How might we structure our technology maintenance roles so that our team feels supported rather than threatened by automation?

Often, the resistance comes from fear of failure or a cognitive gap. Look at your team's conative profiles using the Kolbe Index. If your current team consists mainly of high Fact-Finders and high Follow Thrus, they will naturally resist a seat that feels volatile, unpredictable, or poorly defined. They need structure and proven processes before they feel comfortable taking action.

To solve this, do not dump the entire seat on a resistant manager. Instead, simplify the seat roles on your Accountability Chart. Break the seat down to its bare essentials. If the immediate need is simply monitoring system uptime and coordinating with external vendors, define the roles that way.

If you still lack an internal candidate who can GWC the seat, you must look outside the organization or hire a fractional resource. In an AI-powered operating model, trying to force an existing team member who lacks the conative drive or technical capacity into an advanced technology seat is a recipe for system downtime and executive burnout. Build the seat for the needs of the business, and if the right person is not currently in the building, go find them.