The Level 10 Meeting
The Level 10 (L10) Meeting is the weekly heartbeat of any organization running on EOS. It is a 90-minute, structured meeting designed to keep the leadership team aligned, accountable, and focused on solving the most important issues.
The name "Level 10" comes from the goal: every meeting should be rated a 10 out of 10 by participants. In practice, consistently scoring 8 or above indicates a healthy meeting culture.
Why It Works
Most meetings fail because they lack structure. They start late, wander off topic, rehash the same issues, and end without clear action items. The L10 Meeting solves these problems by:
- Following a fixed agenda -- The seven segments never change. Everyone knows what to expect.
- Keeping time -- Each segment has a strict time allocation. The facilitator enforces it.
- Focusing on solving -- 60 of the 90 minutes are devoted to IDS (Identify, Discuss, Solve).
- Creating accountability -- To-Dos are reviewed every week. Scorecard numbers are checked. Rock status is reported.
- Starting and ending on time -- No exceptions. If someone is late, the meeting starts without them.
The Seven Segments
1. Segue (5 minutes)
Each participant shares one piece of personal or professional good news. This is not optional or trivial -- it humanizes the team, builds connection, and sets a positive tone.
2. Scorecard Review (5 minutes)
The team reviews the weekly Scorecard. Each measurable is quickly checked: on track or off track? No discussion -- just status. If a number is off track, it can be dropped to the Issues list for later discussion in the IDS segment.
3. Rock Review (5 minutes)
Each Rock owner reports whether their Rock is "On Track" or "Off Track." Again, no discussion. Rocks that are off track are candidates for the Issues list.
4. Headlines (5 minutes)
Team members share important news -- customer wins, employee updates, industry developments. Headlines are informational. If any headline needs discussion, it becomes an issue.
5. To-Do Review (5 minutes)
Each person reports on their To-Dos from the previous week: "Done" or "Not Done." The goal is a 90%+ completion rate. Not-done items are either carried forward or escalated to the Issues list.
6. IDS -- Identify, Discuss, Solve (60 minutes)
This is the core of the meeting and the segment that makes L10 Meetings so effective. The team works through the Issues list using the IDS process:
- Identify -- The team prioritizes the top 3 issues.
- Discuss -- Each issue is discussed until the root cause is clear.
- Solve -- The team agrees on a solution, which typically becomes a To-Do.
Then move to the next issue. Repeat until the 60 minutes are up.
WARNING
The IDS segment is the most valuable part of the meeting. Protect this time. If earlier segments are running over, the facilitator must cut them short to preserve IDS time.
7. Conclude (5 minutes)
Wrap up with three steps:
- Recap To-Dos -- Read back all new To-Dos created during the meeting.
- Cascading messages -- Determine what information needs to be shared with the rest of the organization.
- Rate the meeting -- Each participant rates the meeting from 1 to 10.
Best Practices
Same Day, Same Time, Same Agenda
The L10 Meeting happens on the same day and time every week. Do not move it around. Do not skip it. Consistency is what makes it work.
Start on Time, End on Time
If the meeting is scheduled for 9:00 AM, it starts at 9:00 AM -- even if half the team is still getting coffee. This trains punctuality quickly.
No Tangents
If a discussion arises outside the IDS segment, the facilitator drops it to the Issues list. "That's a great point -- let's add it to the Issues list and discuss it during IDS."
Be Honest
The meeting only works if people are candid. Off-track Rocks should be called off-track. Missed To-Dos should be reported as not done. Meeting ratings should reflect reality.
Rotate the Facilitator (or Don't)
Some teams designate a permanent facilitator (often the Integrator). Others rotate. What matters is that someone owns the flow and enforces time limits.
Rate Every Meeting
The 1-10 rating is a feedback mechanism. If the average rating drops below 8, the team should discuss what's not working. Common causes: starting late, not enough IDS time, unresolved issues carried from week to week.
Common Mistakes
| Mistake | Fix |
|---|---|
| Spending too long on Scorecard/Rocks | Strict time limits -- status only, no discussion |
| Solving during Identify | Train the team to separate identifying from discussing |
| Skipping the meeting when "nothing is happening" | There is always something -- the meeting is the discipline |
| Not dropping items to Issues | If it needs more than 30 seconds, it's an issue |
| Low meeting ratings with no action | Discuss the meeting quality itself as an issue |
How EOS Hub Helps
EOS Hub's L10 Meeting feature digitizes the entire L10 flow:
- Guides the team through all 7 segments
- Pulls in Scorecard data automatically
- Shows Rock status for review
- Displays the To-Do list with completion tracking
- Manages the Issues list with IDS workflow
- Records meeting ratings and tracks trends on the Dashboard
Related Pages
- L10 Meetings Feature -- Using the L10 Meeting in EOS Hub
- IDS Process -- Deep dive into the Identify, Discuss, Solve process
- Scorecard -- Weekly measurables reviewed in segment 2
- Rocks -- Quarterly goals reviewed in segment 3