What the Level 10 Meeting is and why it matters
The Level 10 Meeting™ is the weekly leadership meeting at the heart of EOS®, the Entrepreneurial Operating System®. It is the place where a leadership team checks its numbers, confirms that quarterly priorities are on track, clears last week's commitments, and then spends most of its time solving real problems. The name comes from the goal itself: a meeting good enough that everyone in the room would rate it a 10.
Most leadership meetings drift because they have no fixed shape. Updates expand to fill the time, the hardest topics get pushed to the end, and decisions are made without anyone writing down who owns the follow-up. The Level 10 agenda fixes this by doing two things. It compresses reporting into short, predictable segments, and it reserves the majority of the meeting for solving issues. Reporting tells you where you are. Solving is what moves the business.
Because it happens every week, at the same time, with the same agenda, the meeting also becomes the heartbeat for every other EOS tool. Your Scorecard gets reviewed here, your Rocks get checked here, and your short-term issues get resolved here.
The agenda, segment by segment
The standard Level 10 agenda runs 90 minutes. Each segment has a clear purpose and a time box.
| Segment | Time | What happens |
|---|---|---|
| Segue | 5 min | Each person shares one personal and one professional piece of good news |
| Scorecard | 5 min | Review the weekly measurables; each owner says "on track" or "off track" |
| Rock review | 5 min | Each Rock owner reports "on track" or "off track" for their quarterly priorities |
| Customer and Employee Headlines | 5 min | One-sentence updates about customers and people |
| To-Do List | 5 min | Review last week's To-Dos; each one is either done or not done |
| IDS | 60 min | Identify, Discuss, and Solve the most important issues |
| Conclude | 5 min | Recap new To-Dos, agree on any messages to cascade, rate the meeting 1 to 10 |
The discipline is in what you leave out of the first 30 minutes. Reporting segments are for status only. Anything that is off track, surprising, or needs a conversation gets dropped onto the issues list for IDS rather than discussed on the spot. That single habit is what protects the 60 minutes of problem-solving.
Running IDS well
IDS stands for Identify, Discuss, Solve. Start by scanning the issues list and choosing the top three issues, not the first three. Work them one at a time, in priority order.
- Identify. The person who raised the issue states it in a sentence or two. The team then asks questions until the real cause is clear. The stated problem is often a symptom of something underneath it.
- Discuss. Everyone says what they need to say, once. The goal is to surface perspectives, not to argue in circles. When people start repeating themselves, the discussion is over.
- Solve. Agree on the solution and capture it, usually as a To-Do with one owner and a due date within about a week. Some issues are solved simply by sharing information; that counts too.
When you finish the top three, pick the next three. Do not worry if the list is not empty at the end of the meeting. Solving the most important issues completely is better than touching every issue lightly.
Concluding and rating
The last five minutes close the loop. Read back each new To-Do and its owner so nothing is ambiguous. Decide whether anything discussed needs to be communicated to the rest of the company, and who will do it. Then each person rates the meeting from 1 to 10. If someone gives a score below 8, ask them briefly why. Over time, those short explanations are one of the best sources of improvement for the meeting itself.
How to start running Level 10 Meetings
If your team is new to the format, use this checklist to set it up.
- Pick a fixed day and time. Same day, same start, every week. Treat it like a standing appointment that only moves for true emergencies.
- Assign a facilitator and a scribe. The facilitator, often the Integrator, keeps the agenda moving and the time boxes honest. The scribe captures To-Dos, issues, and cascading messages.
- Prepare the inputs in advance. Scorecard numbers should be updated before the meeting starts, and Rock owners should know their status. Prep time spent outside the room saves far more time inside it.
- Start and end on time. Starting late teaches people that the start time is optional. Ending late teaches them the time boxes are optional.
- Keep the issues list visible throughout. Anyone can add an issue at any point in the meeting.
- Commit to several weeks before judging it. The first few meetings usually feel mechanical. The rhythm improves once people trust that issues will actually get solved.
For more detail on setup, see the Level 10 Meetings guide in the help center, and the companion article on running Level 10 Meetings that actually work.
Common mistakes and how to fix them
Reporting turns into discussion. Someone shares a Scorecard number and the room starts debating it. Fix: the facilitator says "Let's drop that to the issues list" and moves on. Agree as a team that this is expected, not rude.
IDS is spent on easy issues. Teams sometimes clear small, comfortable issues to feel productive. Fix: always choose the top three by importance before you start solving anything.
Issues are discussed but never solved. A long conversation ends with "let's think about it." Fix: before moving to the next issue, ask what the solution is and who owns the To-Do. If the issue truly cannot be solved yet, name what information is missing and make getting it the To-Do.
To-Dos linger. The same items appear week after week. Fix: keep To-Dos to roughly seven-day commitments and track completion. If something needs weeks of sustained work, it may belong as a Rock or a longer-term project instead.
Low ratings with no follow-up. The team rates meetings a 6 or 7 but nobody asks why. Fix: treat any rating under 8 as a prompt for a short explanation, then raise recurring complaints as an issue.
Skipping the segue. It can feel like small talk, but it gets everyone mentally present and gives the team a window into what is happening in each other's lives. Keep it short rather than cutting it.
How the Level 10 connects to the other EOS tools
The weekly meeting is where most of the EOS toolbox gets used in practice.
- The Scorecard feeds the meeting with the 5 to 15 weekly numbers that tell you whether the business is healthy. Off-track numbers become issues.
- Rocks are reviewed weekly so that a quarterly priority slipping in week three is caught in week three, not at the end of the quarter.
- The Issues List for the meeting holds short-term issues that can be solved within the next week or so. Longer-term issues live on the company Issues List and are typically worked during quarterly sessions.
- The Accountability Chart clarifies who owns each issue and To-Do, which keeps "whose problem is this?" debates out of IDS.
- Quarterly sessions set the Rocks and clean up the long-term Issues List, and the weekly meeting then executes against them for the next 13 weeks.
As you roll EOS out beyond the leadership team, departments typically run their own Level 10 Meetings with their own Scorecards and issues lists, following the same agenda. Issues that a department cannot solve on its own can be moved up to the leadership team, and vice versa.
Working with your EOS Implementer
If you work with an EOS Implementer, the Level 10 Meeting is usually introduced early in your journey. Your Implementer facilitates the full-day session days, such as Focus Days, Vision Building, and quarterly sessions, and teaches the team how the meeting should run. Between those sessions, your team runs the Level 10 on its own every week.
That split works best when your Implementer can see how the weekly meetings are going. Meeting ratings, completed To-Dos, and the issues your team has solved give them a clear picture before the next session day, so session time can go to the issues that matter most. Teams that are self-implementing can follow the same agenda and the same principles; the weekly rhythm is what matters.
How GoalCadence supports the Level 10 Meeting
GoalCadence is built for teams running on EOS. For the weekly meeting, it gives you a timer with pre-configured segments for each part of the agenda, which you can adjust if your team needs a different split. You can start from Level 10, Quarterly Planning, or Annual Planning meeting templates.
To-Dos created in IDS carry one owner and one due date, flow out of the meeting with their context, and are tracked as pending, in progress, completed, or overdue. Each meeting is rated 1 to 10 so you can watch the trend over time, and a searchable archive keeps your IDS history and documented decisions in one place. Your EOS Implementer can join your account at no cost on every plan, and higher plans add departmental Level 10s and AI meeting summaries. See pricing for plan details.