Level 10 Meeting Agenda for a Small Company

The seven-part Level 10 agenda, what each part is for, where small leadership teams slip, and a lighter weekly version that keeps decisions and review dates.

This is for owner-led companies of about 5 to 100 people who run, or want to run, a weekly leadership meeting.

The Level 10 meeting comes from EOS, the Entrepreneurial Operating System. EOS Worldwide describes it as a weekly leadership meeting with a fixed seven-part agenda, held on the same day at the same time, and meant to run 90 minutes. If you are looking for a level 10 meeting agenda, that is the shape. Below: what each part is for, where small leadership teams tend to slip, and a lighter version for an owner and a few leads.

We are not against EOS. The agenda is a good one. The fixed order is the point: nobody has to decide what the meeting is about this week.

The seven parts

  1. Segue. Each person shares good news from the week, personal or professional.
  2. Scorecard. The team reviews a short list of weekly numbers. Each number has an owner, and each is on track or off track. Off-track numbers become issues.
  3. Rock review. Rocks are the quarterly priorities. Each is on track or off track.
  4. Headlines. Customer and employee news, good or bad, in a sentence each.
  5. To-do list. Did last week's to-dos get done? Done or not done, with no discussion.
  6. IDS. Identify, discuss, solve. This is most of the meeting.
  7. Conclude. Recap the new to-dos, agree on what to tell the rest of the company, and rate the meeting from 1 to 10. The name comes from that rating.

What each part is for

Segue gets people into the room. It is short on purpose.

Scorecard is a smoke alarm. It does not explain anything. It tells you which numbers need a conversation, and the conversation happens later.

Rocks keep the quarter's priorities in front of the team every week, so urgent work does not quietly replace important work.

Headlines are for news that needs no discussion. If it does need discussion, it becomes an issue.

To-dos are the follow-through check. Yes or no, no storytelling.

IDS is where decisions get made. Everything before it exists to clear the way for it.

Conclude closes the loop: what was decided, who does what, and whether the meeting was worth the time.

Where small teams slip

A team of an owner and a few leads does not fail at the agenda. It fails at the edges of it.

The scorecard turns into a debate. Someone sees a red number and explains it. Ten minutes later the team is in the middle of an issue, and the rest of the scorecard has not been read. The fix is the rule in the agenda itself: say on track or off track, and move any off-track number to the issues list.

Issues end without an owner or a date. The team talks well, agrees, and leaves. A week later nobody remembers who was going to do what. An issue is not solved until it has one name and one date next to it.

The numbers are stale. If the scorecard is typed in ten minutes before the meeting, or during it, people stop trusting it. Every number should have a source and a date.

Nobody runs the clock. In a big company someone is paid to facilitate. In a small one it falls to the owner, who also has opinions about every issue. That is a hard job to do well.

The part most templates leave out

The agenda checks whether last week's to-dos got done. It does not check whether last month's decisions worked.

That gap matters. A team can complete every to-do and still make the same poor call twice, because nobody went back to ask whether the call was right.

A decision record fixes this with four fields beyond the decision itself:

  • who owns it
  • who disagreed, and why
  • what would prove it wrong
  • a review date

On the review date, the team asks one question: did it work, partly work, or fail? Write the answer down. After a few months you can see which kinds of calls your team gets right.

A lighter version for an owner and a few leads

If 90 minutes is more than your team will sit through, keep the rhythm and trim the parts. This is a version to try, not a rule:

  1. Scorecard. Five to ten numbers, each on track or off track. No explanations yet.
  2. Last week's decisions and to-dos. Done or not done. For decisions whose review date has arrived, did it work?
  3. Issues. Pick the top few off-track items. For each, decide, then write the owner, the date, and the review date.
  4. Close. Read the new decisions back aloud.

Headlines can go in a shared note before the meeting. The segue is optional. The scorecard, the issues with owners, and the review are the parts that carry the weight.

Who enters the numbers and runs the clock

Someone has to pull the numbers before the meeting, keep time during it, write down each decision, and chase the follow-ups afterward. If that person is the owner, the owner is doing the work of running the meeting on top of leading it. If it is a lead, it is a chore that slides first when things get busy.

The simple fix is to rotate the role weekly so it is not one person's burden. The other is to hand the routine parts to software that works inside rules you set.

How Cabinet runs the same rhythm

Cabinet is our attempt at the second option. Each week it prepares the scorecard, with each number's source and date, and runs the meeting in Slack, Google Chat, or the web. It writes the decision record with owners, dissent, confidence, and a review date. It chases the follow-ups, and on the review date it asks how the decision turned out and grades it worked, mixed, or failed. A fixed policy checks every action against rules the owner sets, and the owner approves what matters. The people in the meeting still make the decisions.

We run agntwrk on it. It is in an invite-only beta, so new workspaces join a short waitlist. Plans are on the pricing page; the trial is $0 with $10 of usage.

If your team already runs a Level 10 meeting by hand, keep what works. If the meeting keeps slipping because nobody wants the job of running it, try it for a few weeks.

Start free