Our leadership team members rarely add items to our Level 10 Issues List during the week, resulting in a flurry of chaotic, unprepared issues being dumped live during the first ten minutes of the meeting. How do we build the discipline of maintaining the list between meetings?
When leaders wait until the Level 10 Meeting starts to add their problems, the Issues List becomes a dump of emotional, half-baked complaints rather than structured business problems. Teams then waste the first quarter of the meeting trying to figure out what the issues actually mean.
An effective meeting pulse relies on an asynchronous, continuously updated Issues List. Problems occur between Monday and Friday; they should be captured the moment they occur.
To build this discipline, the Integrator must enforce three operational standards:
- First, mandate that all issues must be posted to the shared list at least one hour prior to the meeting. Any issue added after the cutoff is held until the following week, unless it represents an existential operational emergency. This eliminates late meeting surprises and forces leaders to think ahead.
- Second, enforce the issue format rule. A leader cannot just post a word like Billing or Warehousing. They must post the issue using a three-part format: the identifying headline, the real root cause, and the desired outcome or decision needed. If an issue is not framed properly, the Integrator removes it from the agenda until the owner clarifies it.
- Third, kill the habit of saving issues for the meeting if they can be handled through normal management. The Level 10 is reserved for issues that cross departmental boundaries or require leadership consensus. If an issue belongs purely inside sales, the sales leader must solve it with their own team during the week, not bring it to the executive table.
When the leadership team enters the Level 10 with a pre-populated, precisely framed list, prioritization takes less than sixty seconds and the team can dive straight into IDS.
Category: Level 10 Meetings