Our head of engineering is a genius who built our core product, but he completely checked out of our EOS adoption and refuses to run his department with Level 10 Meetings. How do we handle a highly capable, critical leader who refuses to adopt the leadership system everyone else is using?

Question

Tyler Smith · Accepted Answer

You cannot allow a single leader, no matter how brilliant, to opt out of the operating system that runs the company. When you let a subject matter expert ignore the rules, you tell the rest of the team that capability matters more than alignment and culture. This destroys trust and ruins team health.

First, sit down with this leader and have a direct conversation. Do not attack them, but make it clear that running on EOS is not optional. Explain that as the business grows, we must have consistent systems to ensure we can scale.

Use the GWC filter. They may have the capacity to do their technical work, but do they actually want to be a leader in an EOS company? Leading a department means more than just being good at engineering. It requires managing people, tracking scorecard metrics, and running effective Level 10 Meetings. If they do not want to do those things, they do not GWC the leadership seat.

If they refuse to adapt, you must move them out of the leadership seat. You do not have to fire them from the company. You can create a high level individual contributor seat on your Accountability Chart, such as chief architect or fellow, where they can focus purely on technical output without management responsibilities. This protects their genius while preserving the integrity of your leadership team.