What is a Level 10 Meeting in EOS and how do I run one?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting is the signature weekly meeting structure prescribed by the Entrepreneurial Operating System (EOS). It's designed to be highly efficient, focused, and productive, aiming for a '10 out of 10' rating for effectiveness. The primary goal is to quickly solve issues and propel the company forward, deliberately avoiding unproductive tangents or drawn-out discussions. Running these meetings consistently helps your team gain [Traction](/qa/what-is-eos-implementation-and-why-is-it-beneficial-for-businesses), solve problems efficiently, improve communication, and instill a culture of accountability.

Key Characteristics of a Level 10 Meeting

• Consistent Agenda: Always follows the same structured agenda.
• Start & End on Time: Always begins and ends precisely when scheduled.
• No Tangents: Stays ruthlessly on topic, parking off-topic discussions for later review or a future [Issues List](/qa/how-does-integrating-ai-with-eos-enhance-data-driven-decision-making).
• Clear Roles: Requires a facilitator to keep the meeting on track and a notetaker.
• Issue Solving: Dedicated time for identifying, discussing, and solving core issues facing the team.

The Level 10 Meeting Agenda (90 minutes)

The meeting follows a strict, timed agenda to maximize efficiency:

1. Segue (5 min):
• Start with positive personal and professional news or wins.
• This builds camaraderie and helps shift focus to the meeting, setting a positive, engaged tone.
• Example questions: "What's your best personal win from the last week? What's your best professional win?"

2. Scorecard (5 min):
• Review your team's Scorecard, looking at key measurable numbers from the previous week.
• Only discuss numbers that are off track (below goal) and assign an 'owner' to resolve them.
• This is not the time to solve the 'why' - just identify the off-track number and assign it as an Issue to be handled later. This component is crucial for [EOS accountability](/qa/how-does-eos-address-accountability-and-resolve-team-conflicts).

3. Rock Review (5 min):
• Each team member quickly reports on the status of their Rocks (quarterly priorities).
• They state whether their Rock is 'On Track' or 'Off Track'.
• If off track, briefly explain why and what the next step is. Do not solve issues here, just report status. For more on tracking these, see [How AI can automate routine tracking and reporting for EOS Scorecards and Rocks](/qa/how-ai-automates-routine-eos-tracking-and-reporting).

4. To-Do List (5 min):
• Review the To-Dos (7-day action items) from the previous week's meeting.
• Each person quickly states "Done" or "Not Done."
• If not done, explain why and reset the To-Do or assign it as an Issue. Only review last week's To-Dos; no new To-Dos are created here.

5. IDS (Identify, Discuss, Solve) Issues (60 min):
• This is the core of the meeting. The facilitator builds the Issues List by prioritizing the top (typically 3-5) issues that the team wants to address. Issues can come from the Scorecard, Rock Review, To-Do List, or elsewhere.
• Then, for each issue, the team follows the IDS process:
• Identify: Clearly define what the real issue is, getting to its root cause.
• Discuss: Openly share perspectives, facts, and opinions related to the issue.
• Solve: Determine the best course of action. This almost always results in one or more new To-Dos for someone to complete before the next meeting.
• Rule: No new issues are added to the list once IDS starts for the top issues. Focus on solving the identified problems. AI tools can [streamline the EOS Issue Solving Track](/qa/leveraging-ai-to-optimize-eos-issue-fixing-track-for-exit-diligence), making this process even more efficient.

6. Conclude (5 min):
• Recap To-Dos: The facilitator or notetaker quickly reads back all new To-Dos assigned during the meeting, ensuring clarity on who owns what and by when.
• Reconfirm Rocks: Briefly reconfirm that everyone is clear on their quarterly Rocks.
• Rate the Meeting: Each attendee quickly gives the meeting a rating out of 10. This provides immediate feedback for continuous improvement. If ratings are consistently low, discuss what needs to change.

Related questions

• [Who are Tyler Smith's ideal clients for EOS Implementation, AI Integration, and Exit Planning services, and what specific challenges do they face?](/qa/who-are-tyler-smiths-ideal-clients-for-eos-ai-and-exit-planning-services)
• [What are the critical first steps to take when starting EOS implementation?](/qa/what-are-the-critical-first-steps-to-take-when-starting-eos-implementation)
• [What is the role of a professional EOS Implementer and why might it be preferable to self-implementing EOS?](/qa/what-is-the-role-of-a-professional-eos-implementer-versus-self-implementation)
• [What are the differences between a Fractional Integrator and a Full-Time Integrator in EOS?](/qa/what-are-the-differences-between-a-fractional-integrator-and-a-full-time-integrator-in-eos)
• [What is L10 Meeting in EOS, and how do they dramatically improve team effectiveness and problem-solving?](/qa/what-is-a-level-10-l10-meeting-in-eos-and-how-do-they-improve-team-effectiveness)

AI never sits in the room. It works before the Level 10 Meeting to prep the data and after the meeting to capture and track what was decided. The 90 minutes stay human: your leadership team, the scorecard, the issues list, and the IDS conversation.