When an unexpected operational disaster strikes, such as a major cybersecurity breach, the loss of an anchor client, or a critical platform outage, the immediate human instinct is to cancel the Level 10 Meeting so everyone can fight fires. How should we adapt the Level 10 Meeting pulse during an acute operational crisis?

Question

Tyler Smith · Accepted Answer

When an unexpected operational disaster strikes, such as a major cybersecurity breach, the loss of an anchor client, or a critical platform outage, the immediate human instinct is to cancel the Level 10 Meeting™ so everyone can fight fires. This reaction is entirely backward. A crisis is precisely when a leadership team needs structured discipline the most.

Canceling the meeting pulse during an emergency leads to chaotic communication, panicked hallway huddles, and conflicting instructions. Instead of throwing out the meeting, use the Level 10 agenda as your crisis management engine.

You do not abandon the framework; you compress the reporting phase to free up maximum time for problem solving. Follow this emergency protocol:
- Cut the Good News segue down to sixty seconds to center the room.
- Spend two minutes reviewing the Scorecard and Rocks purely to check for red flags, offering zero commentary.
- Skip general Headlines completely.
- Wipe the existing Issues List clean for the day or push routine topics to the following week.
- Drop the crisis onto the board as Issue Number 1.

This adjustment frees up approximately eighty uninterrupted minutes for IDS®. The team can now identify the actual root cause of the disaster, debate concrete mitigation steps, decide on immediate actions, and assign unambiguous seven-day To-Dos to specific seat owners. Running your Level 10 Meeting during a catastrophe eliminates panic and channels executive energy into structured execution.