K7 Insights

Your Level 10 Meeting Stopped Moving the Needle

By Kyle Christensen · September 5, 2026

Part of San Diego Business Coaching

Let me ask you this. When was the last time your Level 10 Meeting moved the needle? If you had to think about it, the meeting has lost its purpose, and the fix you’re about to reach for (a new template, a different operating system) is the wrong one. The Level 10 agenda is fine. It works exactly as well as the people sitting in it, and when it stops working, the people drifted first. This is the post-mortem: five ways the meeting rots, and the reset. If you’re still deciding which system to run at all, start with how to choose a business operating system and come back once yours has had time to go stale.

What is a Level 10 Meeting, and why does it stop working?

A Level 10 Meeting is the weekly leadership meeting in EOS, the Entrepreneurial Operating System from Gino Wickman’s Traction. It runs 90 minutes, same day and time every week, on a fixed agenda: a five-minute segue, five minutes on the scorecard, five on Rocks, five on customer and employee headlines, five on last week’s to-dos, sixty minutes of IDS (identify, discuss, solve), and a five-minute conclude where everyone rates the meeting out of 10 (EOS Worldwide publishes the full agenda). Two-thirds of the meeting is supposed to be solving problems. That’s the whole design.

Housekeeping, because it matters here. “Level 10 Meeting,” “EOS,” and “Rocks” in this sense are trademarks of EOS Worldwide, and I’m using them to describe their thing, not mine. I was an EOS Implementer®. I’m not one anymore, and I went on to run most of the other operating systems so you don’t have to. No affiliation with EOS Worldwide today. The leadership meetings I install now borrow from EOS, Scaling Up, and 4DX depending on what the company needs, which is the whole argument of the operating-system piece. None of what follows is specific to EOS. Scaling Up’s weekly meeting rots the same five ways. So does the “Monday leadership sync” you built yourself.

Here’s why it stops working. You read the book because your team needed to step up. You installed the meeting, set Rocks, and for a year or two momentum followed, because structure was the thing you were missing. Then structure became routine. Nobody changed the agenda. Nobody skipped the meeting. It kept happening every Tuesday at nine with the same seven people, and somewhere in year two it stopped producing decisions and started producing attendance.

Drift is normal. Nobody plans it. It’s also entirely correctable, once you can see it.

What are the five ways a Level 10 Meeting goes stale?

Five patterns account for nearly every stale leadership meeting I’ve sat in. Most companies have at least two running at once.

The scorecard is all green, or all red, and nobody tells the story

Look at your scorecard from last Tuesday. If every number was green, one of two things is true: the targets are too easy, or the numbers you’re tracking don’t touch the outcome you need. If every number was red, and has been for two months, your team has already decided the numbers don’t matter and they’re waiting for you to notice.

Either way, the tell is the same. Nobody says why. A number gets read out, somebody says “on track” or “off track,” and the meeting moves on. A scorecard with no story behind it is a list, and the reason you built a scorecard was to argue about the story.

Picture a 35-person construction contractor in Escondido. Green on “bids submitted” for a year, red on “gross margin per job” for the same year. The bid count is easy to hit. The margin number is the only one that pays the crew, and it’s been treated as weather.

Rocks get kicked from quarter to quarter

A Rock is a 90-day priority. The design assumes that in 90 days it’s done or it’s dead. In a stale meeting a Rock rolls to the next quarter, then the next, with a new owner and a reworded title, and nobody at the table says the obvious thing: we have carried this priority for nine months, so it was never a priority.

When a Rock slips, the question you owe the room is a curious one: what was more important? Because something was. The team spent those 90 days doing something. If that something mattered more than the Rock, the Rock was wrong. If it didn’t, you have a buy-in problem or a clarity problem, and both of those are yours to fix.

Picture a downtown law firm that carries “document the intake process” for four straight quarters. It never gets done because the partner who owns it is also the firm’s top biller, and every quarter, billing wins. That’s a seat problem, and no amount of Rock-setting fixes a seat.

IDS identifies, discusses, and never solves

Sixty minutes for issues is the best part of the agenda and the easiest to hollow out. The failure looks like an issues list that gets longer every week, the same three items on top, and an hour spent discussing them from new angles.

The test is simple. At the end of IDS, how many issues did you cross off, and what was the decision on each? If your honest answer is “we made progress on the conversation,” you held a book club. Most teams stall in the D because solving means somebody has to own a to-do with a date on it, and it’s more comfortable to keep discussing.

The meeting became ninety minutes of reporting

This one you can measure with a stopwatch. Time how long your team spends telling each other what happened last week versus deciding what happens next. In a stale meeting, reporting takes the room and IDS gets squeezed to fifteen minutes at the end.

I wrote a while back that I can personally predict 99% of your meetings today are either unnecessary (who’s accountable?) or too long (act your wage). The 90 minutes isn’t sacred. If your team is prepared, they should need a few minutes to propose a decision from what they found. The thirty minutes narrating how they found it is the part you can cut.

Picture a North Park marketing agency with eight people at the table, where every account lead reads out their client list. That’s a status meeting with an EOS logo on it.

The owner runs it

If you facilitate your own leadership meeting, the meeting is a room of people reporting up to you. The issues that get solved are the ones you care about that week. The numbers that get discussed are the ones you ask about. And the two people who never speak are never going to, because there’s no reason to when the boss is holding the pen.

The quiet seats are the tell inside this one. A leadership team where one or two people never add anything is carrying passengers, and the passengers know it. So does everybody else.

How do you fix a Level 10 Meeting that’s lost its purpose?

You fix it by asking the uncomfortable questions in the meeting, in front of the team, instead of thinking them in the car afterward. Here’s the reset, matched to the five failures.

If the scorecard is all green, raise the bar or move the number down a level. Raise every target by 1% and see what stays green. Or admit the number is a departmental metric, delegate it, and stop reviewing it at the leadership table. A leadership scorecard is the five to fifteen numbers that decide whether the company wins the week. Everything else is noise you’re paying seven salaries to listen to.

If the scorecard is red, make it the discussion. Red is the reason the meeting exists. Take the number into IDS and ask the real question about the person who owns it: are they ready, willing, and able to hit it? If the answer is no, you have a training problem or a seat problem, and you’ll know which. Then check the target itself. As I put it once, it’s not that your KPIs suck, you know what’s important. It’s that we suck at two things: making them accountable, and following through on the performance part. Set the target just outside current performance, review it weekly, raise it once they hit it. Gunning for the top of the industry on the first try just sets everybody up to quit.

If Rocks are slipping, get curious, then get honest. What was more important? Did we have buy-in, or did people nod? Did the owner of the Rock have the hours? If a Rock has rolled twice, kill it or replace the owner. Rolling it a third time teaches the whole team that priorities are suggestions.

If IDS never solves, end every issue with a name and a date, or don’t end it. The rule I hold clients to: nothing leaves IDS without a to-do, an owner, and a due date, and the to-do gets read back next week. If the room can’t reach a decision, the decision is that two people take it away and bring a proposal. Discussion that doesn’t end in a to-do is entertainment.

If it’s ninety minutes of reporting, cut the meeting in half. I mean it literally. Run it at 45 minutes for a month and see what breaks. My standing rule for my own calendar: if you receive a 30m or 60m meeting, don’t decline it; propose a new time for half the length. Apply that to your leadership meeting and the reporting evaporates first, because reporting is the part nobody needed.

If the owner runs it, hand over the pen. Pick the facilitator who will hold the room to the agenda, including you. Then ask the question you’ve been scared of: “Why are you here? Do you need to be on this leadership team?” Ask it of the multitasker with the laptop open. Ask it of the seat that hasn’t spoken since March. You will not enjoy it. It’s still the fastest fix on this list.

And one question sits over all of it. Is the business growing financially at a pace that supports everyone at this table? If it isn’t, hit the big stop button, reset the priorities, and rebuild the scorecard around the two or three numbers that would change that answer. A Level 10 Meeting that scores a 10 every week while the company flatlines is grading itself on attendance.

If you’d rather see the whole system scored instead of just the meeting, the Operating System Scorecard takes about six minutes. It shows you whether the stale meeting is the problem or a symptom of a bigger gap, which is usually the case.

Is it the book, or is it you?

It’s you. It was me too.

I’ll say that carefully, because “it’s you” reads as a shot and it isn’t one. I installed this meeting for a living. I’ve also sat at the head of a leadership table as the operator and let my own version of it drift into exactly what I’ve just described: an hour of status, a scorecard everybody nodded at, two seats that never spoke, and on the weeks I was tired one of them was mine. Nobody at that table said the meeting had gone stale, and I didn’t ask. Structure decays into ritual unless somebody keeps asking whether it still produces anything, and that somebody sits at the head of the table.

So the book isn’t to blame. Wickman wrote a perfectly good agenda. Verne Harnish wrote a perfectly good one for Scaling Up. A weekly meeting is only as good as the questions that get asked inside it, and the agenda can’t ask them for you.

What do owners do instead of fixing the meeting?

Four things, and each one is a way to avoid the questions above.

• Switch systems. The EOS meeting went stale, so it’s time for Scaling Up, or OKRs, or a new consultant with a new template. You’ll get a year of momentum from the novelty, then the same five failures, because you brought the same team and the same habits. Switch systems when you’ve found a real gap the current one can’t cover, never to escape a stale meeting.
• Add time. The meeting isn’t solving anything, so it becomes two hours. Now it’s two hours of not solving anything.
• Grow the scorecard. More numbers feels like more accountability. It’s the opposite. A 40-line scorecard guarantees nobody tells the story behind any single line.
• Skip it when things get busy. This is the quiet one. A meeting that gets cancelled whenever a client fire flares up has already told the team what it’s worth.

What to do before next Tuesday

One takeaway, and it’s a question, because that’s the only tool that works on this. Bring it to your leadership team at the start of the next meeting, before the segue, and don’t let anyone answer with a nod: how do we make these meetings matter again, and is everyone at this table truly on board?

Then sit in the silence that follows. That silence is the meeting you’ve been having for the last year, finally saying something.

If you want the honest read on whether the meeting is the problem or the symptom, score your operating system across all 22 capabilities first. It’s free, it takes about six minutes, and it tells you which gap the stale meeting is hiding. If you’d then rather have somebody in the room who’ll ask the uncomfortable questions with you, that’s the work I do with San Diego owners. Take the first whack at it yourself, though. Your team is watching what you do when the meeting gets uncomfortable.