tyler-smith.com · Questions & Answers

One of our key department leaders complies with EOS® on paper but uses the Accountability Chart™ as a defensive shield to refuse cross-departmental work. How do we break this passive resistance to the tools?

The Accountability Chart™ is designed to eliminate ambiguity and clarify who owns what result. It is not an excuse to build departmental silos or refuse company-wide collaboration. When a leader responds to an operational bottleneck with that is not in my five roles, you do not have a tool problem. You have a Core Values and GWC™ problem.

Every seat on an Accountability Chart™ carries an implicit expectation of enterprise-first thinking. If a leader uses their defined seat to watch another department fail, they are violating team health. Address this directly in your next quarterly review or five-five-five conversation. Lay out the specific examples where their refusal to support cross-functional needs damaged company performance.

If the behavior persists, run the issue through IDS® with your Integrator. The Integrator owns the harmonious operation of the leadership team. Clarify the boundary immediately: five roles define where accountability stops, but company goals dictate where effort goes. If an unexpected crisis or high-priority Rock requires cross-functional coordination, leaders step in to solve it.

If an executive refuses to operate with that mindset, evaluate them on the People Analyzer®. A leader who executes their functional seat perfectly but damages team cohesion is a classic culture killer. Give them thirty days to shift from territorial defense to company-first execution. If they cannot make the shift, you must replace them with someone who gets it, wants it, and has the capacity to do the job.

Category: EOS Implementation

← All questions