tyler-smith.com · Questions & Answers

During IDS, our team constantly rushes to propose new company policies or create complex spreadsheets rather than addressing the actual root cause of an operational failure. How do we prevent leaders from putting band-aids on deep organizational issues?

Most leadership teams suffer from an addiction to action. The moment a problem is stated, leaders instinctively pitch solutions, usually in the form of a new policy, an updated process document, or an added approval layer. This is how organizations bloat their operations with administrative friction without solving the underlying defect.

In the EOS framework, the I in IDS stands for Identify. It is the most critical phase, and it should consume the vast majority of your problem-solving time. If you spend forty minutes on an issue, thirty minutes should be spent digging for the root cause, eight minutes discussing options, and two minutes deciding on a binary action item.

When an issue is raised, the Integrator must explicitly forbid anyone from proposing a solution until the root cause is named and agreed upon by the room.

Use the Five Whys technique. When an operational breakdown occurs, ask why it happened, and then ask why to the subsequent four answers.

In almost every business, root causes trace back to one of three failures: people, process, or vision clarity. Is the person in the seat lacking GWC? Is the documented core process missing, misunderstood, or not followed by all? Or is there a lack of alignment on the V/TO?

If your team attempts to solve a people failure with a process rule, or a lack of accountability with a new software tool, stop them immediately. Force the team to address the person or the broken process directly. Anything else is just an expensive band-aid.

Category: Level 10 Meetings

← All questions