Our Chief Technology Officer insists that our software company is far too complex for simple EOS tools like the Scorecard and five-bullet Accountability Chart roles, refusing to track simple weekly numbers. How do we overcome this intellectual resistance to simple disciplines?

Question

Tyler Smith · Accepted Answer

Technical and highly analytical leaders often mistake complexity for sophistication. They believe that because their daily engineering work requires deep technical nuance, their business operating system must be equally complicated. When they call EOS simplistic, they are usually masking a fear of transparency and accountability.

To neutralize this resistance, address it directly using logic and business outcomes:

- Reframe simplicity as a scalability requirement. Explain that complex operational frameworks fail because they cannot be universally executed across departments. Simplicity is a deliberate design choice that prevents communication breakdown as the company grows.
- Challenge their analytical competence. Ask the leader how an engineer monitors system health. They do not read millions of lines of code each day; they track server uptime, latency, and error rates on a telemetry dashboard. A leadership Scorecard is nothing more than operational telemetry for the enterprise.
- Give them ownership of their metrics. Do not mandate arbitrary measurables for their seat. Task them with identifying the three to five leading numbers that accurately predict whether their department will hit its quarterly commitments.

Hold the line on compliance. A leader who refuses to adopt the tools is often resisting the reality that their work must be visible to the rest of the leadership team. Use the People Analyzer to assess whether they GWC their seat and align with your Core Values. Brilliance never excuses a refusal to be accountable to the leadership team.