May 18, 2026
Hi Everyone,
Gino Wickman built the Level 10 Meeting after watching leadership teams rate their weekly meetings a 4 out of 10. The reason was structural. Teams spent the hour reporting status and ran out of time for problem-solving.
His fix was a fixed-time agenda where the largest single block is reserved for solving issues.
Today, we're breaking down a 60-minute version of that structure you can paste into your next meeting invite.
The 60-minute formula
The meeting has six blocks. Together, they add up to 60 minutes, with half the time spent solving problems.
Opening (5 minutes): Each person shares one piece of personal or professional news. Keep the whole block to five minutes, not five minutes per person.
Scorecard review (10 minutes): Walk through 5 to 15 weekly metrics. Each owner says only "on track" or "off track." Anything off-track drops to the issues list with no discussion in this block.
Quarterly priorities (5 minutes): Each owner gives a one-word update on their quarterly priority. Same rule, on or off track, with off-track items dropping to the issues list.
Last week's to-dos (5 minutes): Read down the list. Each item is "done" or "not done." Items that aren't done either go back on next week's list or move to issues, depending on whether they're still worth doing.
Issues (30 minutes): Pick the top three issues from the list. Work through them using the three-step IDS process (Identify, Discuss, Solve). The next section explains each step.
Recap (5 minutes): Read back each action with the owner's name and the due date.
Total: 60 minutes. Half of that is solving problems.
Making the 30-minute block produce decisions
This block has three steps – Identify, Discuss, and Solve. Without these steps, the team can spend 30 minutes talking and not reach a decision.
Identify: Before jumping to solutions, work out what's causing the problem. A metric being off-track is usually a sign of something else, like a hire that hasn't happened or a process that broke. Two or three minutes here makes the discussion that follows useful.
Discuss: Each person says what they think should be done. Keep it short. The goal is to put a few options on the table for the group to choose from.
Solve: The issue ends in one of two ways. Either someone takes the action with a clear name and date, or the group decides no action is needed and closes the issue. "We'll keep an eye on it" is not a valid ending. Without one of these two endings, the same issue will come back next week.
If you work through three issues in 30 minutes, that's ten minutes per issue on average, but the exact split can vary.
Try this today
Open your next weekly leadership meeting invite. Paste this in as the agenda:
- Opening (5 min)
- Scorecard, on or off track only (10 min)
- Quarterly priorities (5 min)
- Last week's to-dos, done or not done (5 min)
- Top issues, identify/discuss/solve (30 min)
- Recap with owners and dates (5 min)
Tell the team the first 25 minutes are for finding what needs solving, the next 30 are for solving the top three, and the last 5 are for capturing commitments.
We built a template you can use to run the meeting. Duplicate the tab each week, and the spreadsheet becomes a record of every meeting.
Go deeper
👉 EOS Worldwide: The Level 10 Meeting – the full agenda and structure from the framework's source, including the meeting rating system
👉 Commoncog: The Amazon Weekly Business Review – a deep look at how Amazon runs 400-plus metrics in 60 minutes through exception-based reporting
👉 Adam Fishman: How to Set Up a Weekly Business Review – guidance on running a 60-minute WBR in a 100-to-400-person SaaS or marketplace company
Coming up tomorrow
Tomorrow, we're looking at four word changes that move close rates and sales cycle length by double digits.
Have a great week!
P.S. If you try this structure for one week, let us know how the team rated the meeting on the 1-to-10 scale.