My leadership team is completely bypassing our weekly Level 10 Meeting™ by calling emergency ad-hoc meetings every time an operational fire pops up, which makes the actual L10 feel redundant. How do we build the discipline to hold issues for the weekly pulse instead of reacting instantly?

Question

Tyler Smith · Accepted Answer

Ad-hoc emergency meetings are the enemy of execution. They disrupt your team's focus, create operational chaos, and make your weekly Level 10 Meeting™ feel like a useless administrative exercise. This behavior is usually driven by a false sense of urgency.

To break this habit, you must implement a strict filter for what constitutes an actual emergency. A true emergency is something that will cause immediate financial, legal, or reputational disaster if not addressed within the next twenty-four hours. Everything else is simply an issue.

When a team member tries to schedule an ad-hoc meeting to discuss an operational problem, the leader or Integrator must say no. Direct them to put the item on the Issues List for the next Level 10 Meeting™.

By saving issues for the weekly pulse, you allow the team to address them in a structured environment where everyone is present. This prevents knee-jerk reactions and ensures you solve the problem with the entire leadership team's context, rather than in a silo.

It also teaches your team self-reliance. When they realize they cannot run to a meeting every time something goes wrong, they are forced to make decisions and solve problems within their own seats. This builds operational maturity and keeps your calendar clean for high-value execution.