During our first 90 days running on EOS, our leadership team still defaults to informal hallway meetings and Slack fire drills instead of trusting the Level 10 Meeting. How do we break this reflex?
When teams begin their first 90 days on EOS, their muscle memory is built on immediate gratification. For years, an urgent email, a phone call, or a drive-by conversation in the hallway felt like productivity. Shifting that habit requires disciplined boundary enforcement from the Integrator and the owner.
Every time a leadership team member walks into your office or drops an urgent operational issue into Slack, ask one qualifying question: Is the business burning down right now, or can this wait until Tuesday's Level 10 Meeting? In ninety-nine percent of situations, nobody is bleeding and no customer is walking out the door. The correct response is simple: Drop it on the Issues List.
If you entertain the conversation outside the meeting, you train the team that the meeting is optional. You also rob the rest of the leadership team of context, creating informational silos and half-baked solutions that collapse a week later.
To break the habit quickly, establish three explicit operational rules:
- Never resolve an interdepartmental debate over direct messages or casual phone calls. Push the topic directly to the Level 10 agenda.
- If someone brings you a non-emergency problem, refuse to brainstorm solutions until the entire team is gathered.
- Celebrate when someone explicitly says, That can wait for IDS next week.
By week six, the volume of daily fires drops dramatically. Team members realize that hoarding issues for the structured 60-minute IDS portion of the Level 10 Meeting produces permanent systemic fixes rather than temporary band-aids. Breaking the drive-by conversation habit is the single fastest way to buy back five to ten hours of executive time each week.
Category: EOS Implementation