90mmeeting.com · Questions & Answers

How do we tell whether our operating system is failing or our leadership team just isn't using it?

Look at actual leadership behavior before concluding that the framework is the problem. Switching systems is unlikely to help if the team carries the same avoidance and inconsistency into the replacement.

Review a few recent commitments and recurring issues. Establish whether priorities were genuinely agreed, ownership was explicit, progress was reviewed, and missed commitments led to a decision. This is an evidence-gathering exercise, not a search for someone to blame.

Then separate two possibilities:

- The system is understood and used consistently, but it leaves important coordination problems unresolved.
- The system's basic practices are repeatedly skipped, overridden, or treated as optional.

The first is a stronger case for considering a different operating system. The second points toward a leadership commitment problem, although unnecessary complexity may be contributing to poor adoption.

EOS deserves consideration when its simpler structure would make consistent use more realistic. Its attention to people, roles, and processes also helps frame the diagnosis beyond whether you have the right planning template.

My recommendation is to bring the pattern, not a verdict, into the EOS 90-Minute Meeting. Ask what EOS would require leaders to do differently and whether the team is willing to do it. There is room for improvement within structured systems, but no operating system can guarantee progress independently of how leaders use it. Make the adoption decision with that responsibility explicit.

Category: EOS vs. Other Operating Systems

← All questions