top of page

EOS L10 Meeting: The Complete Guide to Running Level 10 Meetings That Drive Execution

  • Writer: Daniel Madhan
    Daniel Madhan
  • May 14
  • 8 min read

Updated: 2 days ago

The Level 10 meeting forms the heartbeat of any successful company each week. Companies operating under EOS spend 90 minutes making sure everyone is on the right track, discussing any issues that arise from week to week and ensuring the whole team remains aligned. Studies show that leadership spends almost half of all their meeting time on matters that have nothing to do with what's important to their company but the costs are high, frustration accumulates, and revenue growth stops.


If you continue spending 90 minutes in a meeting where everyone nods in approval and claps at the end, but absolutely nothing changes, your company is slowly going backwards. When your Level 10 meetings are more than just an event that you and others attend, you can start turning around those losses one step at a time. How do you turn a typical EOS Level 10 meeting into a real weapon for productivity?


WHY THIS MATTERS

Studies show that leadership spends almost half of all their meeting time on matters that have nothing to do with what's important to their company costs are high, frustration accumulates, and revenue growth stops.


The 2-Week Death Zone That Kills Every OKR Tool


The 90-minute structure isn't flexible, and that's the whole point. You kick things off with a five-minute section where everyone shares a personal and professional win a simple way to mentally shift gears before getting down to business. From there, you spend five minutes going over the scorecard, which gives you an honest, number-based snapshot of how the week actually went. Then, 5 minutes check-in on your quarterly Rocks to see whether you're on track or falling behind.


After that, 5 minutes are set aside for customer and employee headlines. Another 5 minutes goes toward reviewing last week's to-do list and whether those tasks got done.

The real heart of the meeting is the 60-minute IDS block, where your team works through the issues that actually matter. You close out with a five-minute wrap-up, including a quick rating of how well the meeting went. The moment you let one section bleed into another, you lose the healthy pressure that keeps leaders focused and genuinely accountable.


The 90-Minute L10 Meeting Agenda Breakdown


Time

Section

Purpose

5 min

Personal & Professional

Win

A simple way to mentally shift gears before getting down to business

5 min

Scorecard

An honest, number-based snapshot of how the week actually went

5 min

Rocks Check-in

See whether you're on track or falling behind on your quarterly Rocks

5 min

Customer & Employee

Headlines

Quick share-out on customer and employee news from the week

5 min

To-Do Review

Reviewing last weeK's to-do list and whether those tasks got done

60 min

IDS Block

The real heart of the meeting your team works through the issues that actually matter

5 min

Wrap-up

A quick rating of how well the meeting went


The IDS Process: Identify, Discuss, Solve How It Actually Works


IDS (Identify, Discuss, Solve) is the moment that determines whether a business progresses or remains stagnant. The objective should not be merely to glance over a list of problems and label it a meeting. The essence of a meeting is to trace the root cause of a problem, discuss it openly as a team, and then agree on a solution that effectively works.


One of the biggest mistakes leadership teams make is treating symptoms as though they were the problems. For instance, your sales figures decrease for a week. In this case, it is not a sales-related issue that affects the results; it is something deeper, such as poor lead distribution between marketing and sales departments.


When you get to the IDS phase, train yourself to slow down. Allocate about 80% of your time to simply understanding what is really wrong before anyone suggests a solution. This feels uncomfortable at first, but it saves you from having the same conversation again next week.


After you have accurately identified the underlying problem, the answer generally comes to you on its own. The solution has never been the difficult part. The difficult part is pinpointing the correct problem to solve.


The 90-Minute L10 Meeting Agenda Breakdown


Step

Purpose

Identify

Trace the root cause of a problem not the symptom. Allocate about 80% of your time here.

Discuss

Discuss it openly as a team

Solve

Agree on a solution that effectively works once the problem is correctly identified, the answer generally comes on its own


The solution has never been the difficult part. The difficult part is pinpointing

the correct problem to solve.


The Rocks Review Problem: 30 Seconds Per Rock Isn't Enough


During a strict Level 10 meeting, you quickly say whether a Rock is "on track" or "off track" But when you only spend about 30 seconds on each Rock, it's easy to hide deeper issues. For example, an executive might say a major 90-day goal is "on track" when what they really mean is they'll start working on it next week. That's not good enough. You need to train your team to focus on what's actually been finished so far not just what people plan to do.


If a Rock is falling behind, don't stop to argue about it during this part of the meeting. Just move it to the IDS (Issues, Discussion, Solutions) list right away. By quickly shifting problems to the bottom of the agenda, you keep the meeting moving. At the same time, you make sure that your most important quarterly goals get the serious, problem-solving attention they really need. This way, nothing gets ignored, and the meeting doesn't get stuck either.


Rocks Review: What Hides the Truth vs What Reveals It


What hides the truth

What reveals it

30 seconds on each Rock easy to hide deeper issues

Train your team to focus on what's actually been finished so far not just what people plan to do

"On track" really means "I'll start working on it next week"

If a Rock is falling behind, move it to the IDS list

right away don't argue about it during this

part of the meeting


Why Your L10 Feels Like a Status Update Instead of a Problem-Solving Session


The moment your team starts reading from spreadsheets or trying to justify what they did last week, the meeting has already gone off the rails. There is a big difference between merely reviewing what has been done and making plans to tackle what is not working. That distance gets bigger whenever leaders arrive at the meeting room without having studied their figures beforehand.


This is what usually happens: somebody has a red metric and rather than highlighting it as an issue, they spend the next ten minutes giving a back-story. They had heavy traffic, the vendor was late, and the quarter was difficult. At the same time, all others are just waiting. The problem remains unsolved - it just gets narrated.


If you allow that to go, you're subtly telling your staff that a good excuse is worth as much as a good solution. When someone goes from "here's the issue" to "here's why it's not my fault" you need to intervene. Redirect them. Put the issue on the list and proceed.


Remember that your L10 is not a courtroom, it's a repair shop. No one goes to a mechanic's shop just to know what caused their car to break down they go to the mechanic's shop to get their car fixed. Your meeting room should be a repair shop. The past is useful only as a reference point. The important thing is what your team decides to do next, and whether they leave the room with a clear plan to do what should be done.


Your L10 is not a courtroom, it's a repair shop.


Status Update Mode vs Problem-Solving Mode


Status Update Mode (off the rails)

Problem-Solving Mode (on the rails)

Team reads from spreadsheets or tries to justify what they did last week

Making plans to tackle what is not working

Someone with a red metric spends ten minutes giving a back-story heavy traffic, vendor was late, quarter was difficult

The problem gets highlighted as an issue and put

on the list not narrated

"Here's why it's not my fault"

"Here's the issue" then redirected to action


What the Best L10 Meetings Do Differently: Enforcement Before the Meeting Starts


The best leadership teams never show up to a meeting and assume it will work out. They arrive ready and ensure that everyone else is ready as well. Long before anyone sits down, the scorecard is already filled in, each Rock has a clear status marked against it, and the issues list is ready to go.


The truth is that if people are still doing mental math when the meeting is supposed to be going on, you can't have a meaningful conversation. It's like going to a job interview without knowing anything about the company you intend to work with. It's too late.


That's why dedicated software tools are more important than people realize. A good execution platform compels the preparation to take place in advance. It eliminates the classic "I thought you had the spreadsheet" moment that quietly kills momentum. If the data is fixed before the clock begins, the team can use their time to discuss problems, rather than trying to locate the numbers.


When the meeting starts, and your team are still compiling figures, it's already off track. The first few minutes of the meeting set the tone for the rest of the meeting. Great L10 meetings aren't great because of what happens in the room. They're good because of the discipline that took place before anyone walked into the room. Each and every one needs to be adequately prepared before the meeting starts.


Pre-Meeting Checklist: What Disciplined Teams Have Ready Before They Sit Down


✓ The scorecard is already filled in

✓ Each Rock has a clear status marked against it

✓ The issues list is ready to go

✓ Data is fixed before the clock begins

✓ No more "I thought you had the spreadsheet" moments


Great L10 meetings aren't great because of what happens in the room. They're good because of the discipline that took place before anyone walked into the room.


How to Determine if Your L10 Is Truly Driving Business Forward


Take a close look at your to-do list when the 90 minutes are up. Are the action items clear, owned by one person, and due in exactly 7 days? If your to-dos are unclear, then the meeting failed. Real progress results in real, practical action.


Also, watch the ratings at the end by everyone. If your team scores a 10 out of 10 every time, it's a red flag. It likely indicates that people are not having difficult conversations. Sometimes a healthy, useful meeting should be given an 8 because the meeting was difficult, draining, or uncomfortable. A little bit of friction is needed to move the business forward. If you don't feel a little drained or uncomfortable at the end of the meeting, it means you're not getting the real opportunities to improve.


Ultimately, you'll know if your L10 meeting is driving your business forward if it helps improve execution. Key indicators that show that your L10 is truly driving your business forward include Rocks getting completed consistently, issues getting solved permanently, teams are getting more accountable, employees are getting more productive, and your revenue and scorecard numbers are improving


L10 Health Check: How to Tell if Your Meetings Are Actually Working


Indicator

What to look for

To-do clarity

Action items clear, owned by one person, and due in exactly 7 days

Meeting rating

If your team scores a 10 out of 10 every time, it's a red flag likely indicates people are not having difficult conversations. An 8 after a hard, draining meeting is healthier

Rock completion

Rocks getting completed consistently

Issue resolution

Issues getting solved permanently

Team accountability

Teams are getting more accountable

Productivity

Employees are getting more productive

Business numbers

Your revenue and scorecard numbers are improving


THE BOTTOM LINE

A little bit of friction is needed to move the business forward. If you don't feel a little drained or uncomfortable at the end of the meeting, it means you're not getting the real opportunities to improve.


 
 
 

Comments


bottom of page
Request Pilot Program