tyler-smith.com · Questions & Answers

We have successfully cut our Level 10 Meeting™ down to ninety minutes, but we do so by rushing through the IDS® portion, leaving deep systemic issues unresolved. How do we protect the depth of our problem solving without letting the meeting run over?

A fast meeting that solves nothing is just as bad as a slow meeting that wanders. If you are hitting your ninety minute mark but leaving major operational issues unresolved, you are likely failing to prioritize your Issues List.

The secret to deep problem solving within a tight time frame is strict prioritization. You must never work your Issues List from top to bottom. Instead, spend the first sixty seconds of the IDS® portion identifying the top three most critical issues. Do not touch number four until numbers one, two, and three are completely solved.

Many teams rush because they try to solve ten minor issues rather than tackling the single most painful bottleneck. If you spend sixty minutes of your meeting thoroughly resolving one massive structural issue, that is a highly successful meeting.

Additionally, you must stop using the IDS® portion to simply share updates or gossip. If an issue does not require a decision, a policy change, or a resolved conflict, it does not belong on the agenda. It should be handled offline. Keep your discussions focused solely on root causes and permanent solutions. By narrowing your focus to the vital few and refusing to allow status updates to hijack your time, you will achieve deep, permanent resolutions well within your ninety minute block.

Category: EOS Implementation

← All questions