Our leaders keep calling ad-hoc emergency meetings during the week to hash out operational problems, claiming they cannot wait until the next Level 10 Meeting. How do we stop this meeting creep and protect our weekly pulse?

Question

Tyler Smith · Accepted Answer

Meeting creep is a symptom of poor operational discipline. When leaders schedule mid-week syncs and emergency problem-solving sessions, they fragment calendars, pull people out of execution, and undermine trust in the weekly Level 10 Meeting.

Except for genuine existential crises, such as a major data breach, a total systems outage, or sudden regulatory intervention, virtually every operational issue can wait a few days for the scheduled weekly pulse.

To eliminate off-cycle meeting creep, establish a clear gatekeeping rule:
- Every problem discovered between meetings must be logged directly onto the Issues List rather than added to an impromptu calendar invite.
- If a leader insists on calling an ad-hoc meeting, they must get explicit sign-off from the Integrator.
- The Integrator tests the request with one question: If we do not solve this in the next 48 hours, will the company suffer irreversible financial, legal, or customer loss?

In ninety-five percent of cases, the answer is no. The issue feels urgent simply because it is top of mind, not because it poses an immediate catastrophic threat.

When you force problems to wait for the Level 10 Meeting, two things happen. First, leaders often resolve minor friction on their own using existing processes. Second, the leadership team arrives at IDS with a well-developed perspective instead of a knee-jerk emotional reaction. Protect the weekly pulse ruthlessly. If everything is treated as an emergency, nothing gets resolved effectively.