Level 10 Meeting Agenda: The Weekly Meeting Structure That Keeps Leadership Teams Aligned
Your leadership team meets every week. And every week, the same thing happens: the meeting runs long, the loudest voice dominates, half the team checks out by minute thirty, and the issues that actually matter get pushed to “next week.” Again.
You are not alone. Research shows that 71% of weekly meetings are considered unproductive, costing U.S. companies an estimated $37 billion per year in lost productivity. For a company with 50 to 150 employees, that translates into hours of executive time burned every single week with nothing to show for it.
The problem is not that your team meets too often. The problem is that your meetings have no structure, no rhythm, and no mechanism for resolving the issues that are quietly strangling your growth.
What a Level 10 Meeting Actually Is
The Level 10 Meeting (often called the L10) is the weekly leadership team meeting format built into the Ninety.io platform and the broader Business Operating System framework. The name comes from a simple idea: every meeting should be rated on a scale of 1 to 10 by the team at the end, and the goal is to hit a 10 every single week.
That sounds ambitious. But once the structure is in place, teams consistently rate their meetings between 8 and 10 within a few weeks of adoption. The secret is not better facilitation skills or more charismatic leadership. It is a fixed agenda that accounts for every minute of a 90-minute block, with the majority of time dedicated to solving real problems instead of listening to status updates.
A Level 10 Meeting is not a status meeting, not a brainstorming session, and not a “let’s go around the room” exercise. It is a disciplined operating rhythm where the leadership team reviews data, checks progress on quarterly priorities, and resolves the issues that are blocking execution.
Why the Level 10 Meeting Matters More Than You Think
Most leadership teams I work with have some version of a weekly meeting. The problem is that these meetings have drifted over time into one of two failure modes.
Failure mode one: the update parade. Each department head gives a five to ten minute summary of what happened last week. By the time everyone has spoken, the meeting is over and nothing has been decided. The team walks out informed but unchanged.
Failure mode two: the fire drill. Whoever has the most urgent crisis hijacks the meeting. The team spends 90 minutes reacting to one issue while six other important problems go unaddressed. This creates a pattern where only emergencies get attention and systemic issues never get resolved.
Both failure modes produce the same outcome: your leadership team meets every week but the business does not actually get better. Strategic priorities drift. Accountability erodes. And the CEO ends up solving problems one by one in hallway conversations because the meeting did not do its job.
The Level 10 Meeting breaks both patterns by allocating time proportionally. Updates get five minutes. Issues get sixty. That ratio is not a suggestion; it is the architecture that makes the meeting work.
How the Level 10 Meeting Agenda Works
The Level 10 Meeting runs exactly 90 minutes. Same day, same time, same room, every week. The agenda never changes. Here is each segment and what happens in it.
Segue (5 Minutes)
Every person at the table shares one piece of good news, personal or professional. This is not small talk. It is a deliberate transition that gets people out of their inbox and into the meeting mentally. Teams that skip this step spend the first 15 minutes warming up. Teams that do it are locked in by minute six.
Scorecard Review (5 Minutes)
The team reviews five to fifteen key metrics (the Scorecard) that represent the health of the business. Each number is owned by one person. The only discussion here is whether a number is on track or off track. If it is off track, the owner drops that issue onto the Issues List. No fixing, no explaining, no debating. Just flagging.
This is where Ninety.io earns its place: the Scorecard is visible in real time, numbers are updated before the meeting, and the team can see trends over weeks and quarters without anyone building a slide deck.
Rock Review (5 Minutes)
Rocks are the company’s 90-day priorities. Each Rock is owned by one person. The review is binary: on track or off track. Again, no discussion. If a Rock is off track, it drops to the Issues List. This five-minute check replaces the 30-minute “project update” that kills most meetings.
Customer and Employee Headlines (5 Minutes)
Anyone at the table can surface a headline about a customer situation or an employee situation that the team needs to be aware of. These are not problems to solve in this moment. They are awareness items. If a headline needs action, it goes to the Issues List.
To-Do Review (5 Minutes)
The team reviews the to-do list from last week. Every to-do is a seven-day action item owned by one person. The review is binary: done or not done. A healthy team completes 90% or more of its to-dos every week. If the completion rate drops below that, something is broken in accountability or prioritization, and that itself becomes an issue.
IDS: Identify, Discuss, Solve (60 Minutes)
This is the heart of the meeting. The team looks at the Issues List (which has been building throughout the Scorecard, Rock, Headline, and To-Do segments) and prioritizes the top three issues. Then they work through each one using the IDS framework:
Identify the real issue. Not the symptom. The root cause. This is often the hardest step because most teams want to start solving before they have named the actual problem.
Discuss it openly. Everyone with relevant information speaks. The facilitator keeps the discussion focused and prevents circular conversation. No side conversations, no tangents, no “well, actually” loops.
Solve it with a decision. Every issue ends with either a to-do (a seven-day action item assigned to one person), a change to a process, or a decision that closes the issue permanently. Nothing leaves the IDS segment without a resolution.
The 60-minute allocation is what separates the Level 10 from every other meeting format. Most meetings spend 80% of their time on updates and 20% on decisions. The Level 10 inverts that ratio. Your leadership team spends the vast majority of its time doing the thing that only the leadership team can do: making decisions and solving cross-functional problems.
Conclude (5 Minutes)
The team reviews the to-dos created during the meeting, confirms who owns what, and identifies any messages that need to cascade to their teams. Then everyone rates the meeting on a scale of 1 to 10. If the rating is below 8, the facilitator asks what would have made it better. Over time, this feedback loop tightens the meeting until it consistently hits 9 or 10.
Real-World Application: What Changes When the Level 10 Takes Hold
I worked with a professional services firm, about 80 employees, $12M in revenue, where the CEO was running a two-hour Monday meeting that the leadership team openly dreaded. The agenda was informal: whoever had the biggest problem that week got the floor. The COO called it “crisis roulette.”
We replaced that meeting with a Level 10 in week one. The first three weeks were rough. The team was not accustomed to the discipline. They wanted to discuss Scorecard numbers instead of just flagging them. They wanted to solve Headline items on the spot. The facilitator, a woman named Keiko who ran operations, had to redirect constantly.
By week four, something shifted. The Scorecard review was taking three minutes. The Rock review was taking two. The team was dropping issues onto the list efficiently because they trusted that the IDS segment would get to them. And the IDS segment was producing real decisions: a pricing change that had been debated for months got resolved in twelve minutes. A hiring conflict between two departments got settled with a clear to-do and a deadline.
By week eight, the CEO told me the Level 10 was the single highest-value hour of his week. Not because the meeting was fun, but because it was the one place where the leadership team actually solved problems together instead of just talking about them.
I have seen similar patterns in a 40-person manufacturing company where the owner, a man named Dmitri, was attending every department meeting because he did not trust the leadership team to make decisions without him. Once the Level 10 was running, he dropped three of those meetings within a month. The issues that used to require his involvement were being resolved by the team in IDS. He got six hours a week back.
Signs Your Team Needs the Level 10 Meeting Structure
You probably need to adopt the Level 10 if any of these sound familiar:
- Your weekly meeting regularly runs over the scheduled time, and people still leave feeling like nothing was accomplished.
- The same issues come up week after week because they never get fully resolved.
- One or two people dominate every meeting while the rest of the team disengages.
- Your meeting is mostly status updates that could have been sent in an email.
- You, as the CEO, are the de facto facilitator, which means you cannot participate fully as a team member.
- Decisions made in meetings do not stick because there is no follow-up mechanism.
- Your team avoids raising difficult issues because there is no structured way to discuss them.
If three or more of those are true, your meeting is not broken because of bad attitudes or lack of effort. It is broken because it has no architecture. The Level 10 provides that architecture.
How to Get Started
Start by committing to one change: a fixed 90-minute meeting, same day and time every week, with the Level 10 agenda printed on the table. Assign a facilitator who is not the CEO (this is critical; the CEO needs to participate, not run the meeting). Assign a scribe to capture to-dos and issues. Run the meeting exactly as outlined above for six consecutive weeks before evaluating.
The first two weeks will feel awkward. The team will resist the time constraints. Let them. The discipline is the point. By week three, the rhythm starts to click. By week six, your team will wonder how they ever operated without it.
If you want a platform that automates the Scorecard, Rock tracking, Issues List, and To-Do management so the meeting runs itself, Ninety.io is built specifically for this. It is the tool I recommend to every leadership team I work with because it turns the Level 10 from a paper exercise into a living operating system.
Frequently Asked Questions
What is a Level 10 meeting? A Level 10 meeting is a structured 90-minute weekly leadership team meeting designed within the EOS and Business Operating System frameworks. It follows a fixed agenda that dedicates 60 of the 90 minutes to identifying, discussing, and solving the most important issues facing the business. The name refers to the goal of rating every meeting a 10 out of 10 for effectiveness.
How long should a Level 10 meeting last? Exactly 90 minutes. The meeting starts on time and ends on time, every week. The fixed time constraint is part of the design: it forces the team to prioritize ruthlessly and prevents discussions from expanding to fill available time. Teams that extend the meeting “just this once” lose the discipline that makes the format work.
Who should facilitate a Level 10 meeting? Ideally, the Integrator, COO, or a designated operations leader facilitates the Level 10. It should not be the CEO or Visionary. The facilitator’s job is to keep the agenda on track, redirect tangents, and ensure every issue reaches a resolution. When the CEO facilitates, they cannot fully participate as a team member, and the meeting tends to drift toward whatever the CEO cares about that week.
Can we modify the Level 10 agenda for our team? The short answer is: not in the first 90 days. Run the meeting exactly as designed for at least one full quarter before making any adjustments. Most teams that modify the agenda early end up reverting to their old meeting habits. After a quarter of consistent use, minor adjustments (like extending IDS by five minutes and shortening Headlines) can work, but the core structure should remain intact.
What is the difference between a Level 10 meeting and a regular weekly meeting? A regular weekly meeting typically has a loose or rotating agenda, focuses heavily on status updates, and often ends without clear decisions or action items. The Level 10 inverts this: updates are compressed into 25 minutes, and the remaining 65 minutes are spent solving problems and making decisions. The fixed structure, weekly Scorecard review, and IDS framework create accountability that informal meetings cannot replicate.
