Guide

How to run an EOS Level 10 (L10) meeting

L10 works because it’s boring, timed, and consistent. Your “second brain” makes it stick: decisions, owners, due dates — with receipts.

Open L10 pack builder Use the L10 generator See Exec tools
TL;DR
  • L10 wins through cadence: same agenda, same timeboxes, every week.
  • Most teams fail at IDS and follow-through. Minutes must include owners + due dates.
  • Don’t let “great conversation” turn into “no action.” Ship the recap within 30 minutes.

The L10 agenda (classic timeboxes)

  • Segue (5m): quick wins / good news.
  • Scorecard (5m): numbers only; on/off track.
  • Rock review (5m): on/off track; no stories.
  • Headlines (5m): customer/employee headlines.
  • To‑dos (5m): last week’s commitments, done/not done.
  • IDS (60m): identify → discuss → solve.
  • Conclude (5m): recap new to‑dos + rate meeting 1–10.
Generate an L10 pack Ship a recap

IDS: the part most teams get wrong

IDS fails when you let it become “status updates.” Keep it ruthless:

  1. Identify: capture issues as short, neutral statements.
  2. Discuss: one issue at a time; clarify root cause.
  3. Solve: decide an action, owner, due date. Then move on.
Don’t solve with “we should.” Solve with “Owner X will do Y by Z.”

The minutes format that actually sticks

Your minutes should read like a contract with your future self. Three sections:

TL;DR
3 bullets maximum. What changed?
Decisions
What is now true? Who decided?
Action items
Owner · Task · Due date · Status
Minutes generator • L10 pack generator • Recap generator

Where tools betray you (what to validate)

L10s are full of numbers and names: scorecards, metrics, rocks, customers, owners. Validate those failure modes before you trust the notes.

Numbers stress test
Scorecard metrics and commitments drift quietly.
Names stress test
Owners and customers must be captured correctly.
Want the cheapest exec-safe tool?
Filter by Exec, then validate numbers and names.
Take Tool Finder See pricing table See lab receipts