The Level 10 Meeting: The Single Most Important Meeting in Your Business
Most leadership meetings are expensive theater. Ninety minutes of status updates that could have been a spreadsheet. The Level 10 Meeting flips that pattern entirely — and it's the reason some service businesses execute flawlessly while others drown in good intentions.
I sat in on a leadership meeting last month at a consulting firm doing about $2 million a year. Seven people around a table. Ninety minutes blocked on everyone's calendar. The founder opened with "let's go around the room and share updates." By minute forty, three people were checking their phones. By minute seventy, the discussion had looped back to a topic they'd already covered. At minute eighty-five, someone raised a real problem — a partner who hadn't delivered an engagement in three months — and the founder said, "Good point. Let's table that for next week."
That meeting cost the company roughly $3,000 in loaded salary time. It produced zero decisions. The real issue got punted. And everyone left feeling vaguely frustrated without understanding why.
This isn't unusual. It's the default. Most leadership meetings in service businesses are ceremonial — they exist because someone once decided there should be a weekly meeting, but nobody designed what that meeting should actually accomplish.
Gino Wickman, creator of the Entrepreneurial Operating System, spent decades studying what separates companies that execute from companies that talk about executing. His answer is disarmingly specific: a single weekly meeting with a rigid structure, a fixed agenda, and one sixty-minute block where the hardest problems get solved — not discussed, not tabled, not delegated to a subcommittee. Solved.
The Architecture of 90 Minutes
Why Every Segment Has a Timer
The Level 10 Meeting — named because the goal is for every participant to rate it a 10 out of 10 — runs on a precisely timed agenda. Not approximately timed. Precisely. Every segment has a clock, and the clock is non-negotiable.
Here's what it looks like when adapted for a service business with a practitioner or partner ecosystem:
Good News (5 minutes). Each person shares one personal or professional win. This isn't fluff — it's a deliberate pattern interrupt. You're transitioning people from whatever chaos they were handling five minutes ago into a focused, collaborative state. When someone shares that their daughter scored a goal or that a client renewed a contract, the room's energy shifts. Five minutes. No more.
Scorecard Review (5 minutes). Your 5-15 weekly numbers. On track or off track. That's it. No explaining why something is off track — that goes on the issues list. The scorecard is binary: green or red. You're scanning for patterns, not solving problems. If revenue per active partner dropped for the third consecutive week, that's a pattern worth flagging. Flag it, move on.
Rock Review (5 minutes). Your 90-day priorities. On track or off track. Again, binary. If your Q3 Rock was "publish the first benchmark report" and it's week eight with no draft, that's off track. Don't explain. Don't defend. Just call it.
Client/Partner Headlines (5 minutes). Any news from the field that affects the business this week. A major client delayed their assessment. A partner landed a three-engagement deal. A competitor launched a similar offering. Headlines only — no deep dives.
To-Do Review (5 minutes). Last week's action items. Done or not done. The target is 90% completion. If your team consistently hits below 80%, the problem isn't the meeting — it's that people are committing to things they can't deliver. Tighten the commitments.
All of that takes 25 minutes. Which leaves the remaining 60 minutes for the only segment that actually matters.
IDS: The Engine That Makes It All Work
Sixty Minutes That Justify the Other Thirty
The remaining 60 minutes belong to IDS — Identify, Discuss, Solve — Wickman's protocol for turning problems into decisions. Throughout the first 25 minutes, issues accumulate on the list. The scorecard flags a metric off track for three weeks. The Rock review surfaces a stalled priority. A partner headline raises a competitive concern. When IDS begins, the team ranks them by impact and works from the top.
IDS is powerful enough to deserve its own deep dive. The short version: every issue gets a root cause (not a symptom), a focused discussion (once, no relitigating), and a concrete action with a specific owner and deadline. Some weeks you'll solve seven issues. Other weeks, one gnarly strategic problem consumes the entire block. Both are fine.
At the end of every Level 10 Meeting, each participant rates the session from 1 to 10. Track the average over time. If you're consistently below 8, something in the structure needs attention — usually too much time on status updates and not enough in IDS.
The Disciplines That Make It Work
Same Day, Same Time, No Exceptions
The Level 10 Meeting only works if it's non-negotiable. Same day every week. Same time. Same room (or same video link). Same agenda. Wickman is absolute about this: canceling the weekly L10 is a culture problem, not a scheduling problem.
Service business founders push back on this constantly. "But I have a client meeting that conflicts." "But two team members are traveling." "But we don't have anything urgent this week." Every one of these objections misses the point. The L10 isn't a meeting you hold when there are problems. It's a meeting you hold so problems don't compound.
Think of it this way: you don't skip a heartbeat because "nothing exciting happened today." The heartbeat is the mechanism that keeps everything alive. The L10 is your business's heartbeat.
Here are the disciplines that separate effective L10s from ones that decay within a month:
Start on time, even if people are missing. If the meeting is at 9:00 AM, Good News begins at 9:00 AM. Not 9:03 while you wait for someone's call to end. Starting late teaches everyone that the meeting doesn't actually start at 9:00. Starting on time teaches them it does.
End on time. Always. Ninety minutes. Not ninety-five because "we're almost done with this issue." Ending on time builds trust in the format. People know they can commit to the meeting without it bleeding into their next obligation.
No laptops for non-relevant work. If someone is half-attending while answering emails, they're not attending. The L10 requires full presence from everyone in the room. If the meeting isn't important enough for full attention, the team is too big.
"Missing one meeting is a signal. Missing two is a culture problem." — Verne Harnish
The hardest discipline is the founder's. Because the founder is usually the one most tempted to cancel ("I've got a big deal to close"), to extend ("this issue is too important to cut off"), or to dominate ("let me explain what I think the solution is"). The Level 10 Meeting works when the founder protects the format even when — especially when — it's inconvenient.
Why Service Businesses Need This More Than Anyone
In a product company, execution problems surface naturally. The product either ships or it doesn't. The feature either works or it's buggy. The metrics dashboard shows usage numbers in real time.
In a service business — especially one with a distributed practitioner network — execution problems hide. A partner who hasn't delivered an engagement in months might simply be "quiet." A methodology deviation might not surface until a client complains. A pricing erosion might happen deal by deal, invisible until the quarterly revenue review reveals that average deal size has dropped 30%.
The Level 10 Meeting is a visibility machine. The scorecard catches metric drift early. The Rock review catches strategic stalls before they become fatal. The IDS protocol catches cultural problems, competitive threats, and partner issues before they fester into crises.
Without it, your partner ecosystem runs on trust and hope. Trust that everyone is delivering quality. Hope that problems will surface before they damage the brand. Trust and hope are wonderful human qualities. They're terrible operating systems.
With the L10 in place, nothing hides for more than seven days. A metric turns red on Monday; by the following Monday, there's a to-do assigned to fix it. A partner goes quiet in March; by the second week of March, someone has been tasked with a diagnostic conversation.
The Level 10 Meeting isn't about making your week more structured. It's about making your problems smaller — by catching them before they grow.