How to Run an Effective L10 Meeting: Agenda, Rocks, Scorecards, and Team Accountability

Written by

in

Running an effective L10 meeting requires more than following a calendar invite and reviewing a few updates. In the Entrepreneurial Operating System, the Level 10 meeting is designed to help leadership teams stay focused, solve real issues, and maintain accountability week after week. When done well, it becomes a disciplined operating rhythm that turns strategy into measurable execution.

TLDR: A strong L10 meeting follows a consistent 90-minute agenda, uses Rocks to track quarterly priorities, reviews scorecard metrics, and ends with clear accountability. For example, a 25-person operations team might reduce overdue tasks by 35% in one quarter by using a weekly Issues List and assigning every action item to one owner. The meeting works best when updates are brief, problems are prioritized, and decisions are clearly documented.

What Is an L10 Meeting?

An L10 meeting is a weekly leadership meeting structured to achieve a “level 10” rating from participants. The goal is not simply to talk through business activity, but to identify the most important problems and solve them with discipline. A typical L10 meeting lasts 90 minutes and follows the same agenda every week.

The power of the meeting comes from consistency. Rather than reinventing the discussion each time, the team uses a proven structure to review priorities, inspect performance, and address obstacles. This keeps the conversation from drifting into status reporting or vague debate.

The Standard L10 Meeting Agenda

A reliable agenda helps protect the meeting from becoming unfocused. While companies may adjust details to fit their culture, the classic L10 structure includes the following sections:

  • Segue: Each person briefly shares a personal and professional win.
  • Scorecard Review: The team reviews key weekly metrics and flags anything off track.
  • Rock Review: Quarterly priorities are checked for progress and ownership.
  • Customer and Employee Headlines: Important feedback, concerns, or wins are surfaced.
  • To Do Review: Previous action items are reviewed for completion.
  • IDS: The team identifies, discusses, and solves the most important issues.
  • Conclude: New to dos are confirmed, key messages are cascaded, and the meeting is rated.

The meeting should be timed carefully. Many effective teams spend only a few minutes on updates, reserving the majority of the session for IDS, which stands for Identify, Discuss, Solve. This is where the real value of the L10 meeting is created.

Using Rocks to Keep Quarterly Priorities Visible

Rocks are the company’s most important priorities for the quarter. They are not everyday tasks or general goals. A good Rock is specific, measurable, and assigned to a single owner. For example, “Improve onboarding” is too vague, while “Launch a new onboarding checklist for all customer success hires by March 31” is much stronger.

During the L10 meeting, Rocks should be reviewed quickly and honestly. Each owner reports whether the Rock is on track or off track. If a Rock is off track, the team should avoid long explanations during the review section. Instead, the issue should be added to the Issues List and addressed during IDS if it is one of the highest priorities.

This approach protects the meeting from becoming a lengthy progress report. More importantly, it creates transparency. Everyone can see which priorities are moving forward and which need support, adjustment, or urgent attention.

Scorecards: Measuring What Matters

The scorecard is one of the most important tools in an L10 meeting. It provides a weekly view of the numbers that indicate whether the business is healthy. These metrics should be practical, timely, and connected to business outcomes.

Examples of scorecard metrics include:

  • Sales: new qualified leads, proposals sent, close rate, weekly revenue.
  • Operations: on time delivery, production backlog, error rate, capacity utilization.
  • Finance: cash balance, accounts receivable, gross margin, overdue invoices.
  • Customer Success: churn risk accounts, support response time, customer satisfaction score.
  • People: open roles, employee turnover, training completion, absenteeism.

A useful scorecard does not need dozens of numbers. In fact, too many metrics can reduce clarity. Most teams benefit from tracking 5 to 15 meaningful numbers that can be reviewed weekly. Each metric should have an owner, a target, and an agreed definition so there is no confusion about what is being measured.

When a number is off track, the team should not immediately dive into discussion. The facilitator should ask whether it belongs on the Issues List. This keeps the scorecard review efficient while still ensuring that important performance gaps are not ignored.

Building a Strong Issues List

The Issues List is where concerns, obstacles, decisions, and opportunities are captured. It should be treated as a working inventory of what may be holding the organization back. A weak L10 meeting avoids difficult issues; a strong L10 meeting brings them into the open and addresses them objectively.

Common issues include missed targets, unclear responsibilities, process breakdowns, customer complaints, staffing constraints, and strategic disagreements. The key is to write issues clearly. Instead of listing “Marketing problem,” write “Inbound lead volume has dropped below target for three consecutive weeks.” Clear wording leads to clearer solutions.

Once issues are listed, the team should prioritize them. Not every issue deserves discussion in that meeting. The facilitator should guide the group toward the most important items, especially those that affect revenue, customer experience, team capacity, or quarterly Rocks.

IDS: Identify, Discuss, Solve

The IDS process is the core problem-solving method used in an L10 meeting. It prevents teams from circling around symptoms without reaching decisions.

  1. Identify: Clarify the real issue. Ask whether the stated problem is the root cause or only a symptom.
  2. Discuss: Allow relevant input, but keep the conversation focused. Avoid repetition, side topics, and defensiveness.
  3. Solve: Agree on the decision or action needed. Assign a clear owner and deadline when follow-up is required.

Effective IDS requires discipline. The goal is not to let everyone speak at length; the goal is to solve the issue. A strong facilitator will respectfully interrupt repetition, redirect vague comments, and ask, “What is the next action?”

Team Accountability and To Dos

Accountability is one of the main reasons L10 meetings work. Every to do created during the meeting should be assigned to one person, not a department or group. It should also be specific enough that completion is easy to verify the following week.

For example, “Follow up with finance” is weak. A better to do is: “Maria will send the revised cash flow forecast to the leadership team by Friday at 3 p.m.” This removes ambiguity and makes accountability objective.

During the next L10 meeting, to dos are reviewed as either done or not done. There should be no long explanations in this section. If a missed to do creates a larger concern, it can be added to the Issues List. This reinforces a culture where commitments matter.

The Role of the Facilitator

A well-run L10 meeting depends heavily on facilitation. The facilitator does not need to be the CEO, but they must be comfortable managing time, enforcing the agenda, and keeping the team focused. Their responsibility is to protect the process.

Important facilitator behaviors include:

  • Start and end on time.
  • Keep updates brief and factual.
  • Move off-track items to the Issues List.
  • Push for clear decisions and owners.
  • Prevent blame-oriented conversations.
  • Ask the team to rate the meeting honestly.

The final meeting rating is more than a formality. If participants rate the meeting below an 8, the facilitator should ask what would make it better. Over time, this feedback helps improve the quality and discipline of the meeting.

Common Mistakes to Avoid

Many L10 meetings lose effectiveness because teams drift away from the structure. The most common mistakes include spending too much time on status updates, reviewing too many scorecard numbers, tolerating vague Rocks, and failing to assign clear to dos. Another frequent issue is allowing the loudest voices to dominate IDS while quieter team members hold back important insights.

Leaders should also avoid using the L10 meeting as a place for punishment or public embarrassment. Accountability is essential, but it must be professional and fact-based. The meeting should create clarity and progress, not fear.

How to Know Your L10 Meeting Is Working

An effective L10 meeting produces visible results. Rocks move forward, scorecard problems are addressed earlier, issues get solved instead of recycled, and team members follow through on commitments. Over several weeks, the organization should experience fewer surprises because problems are surfaced consistently.

A practical benchmark is to track completion rates for weekly to dos. If the team consistently completes at least 85% to 90% of action items, accountability is likely improving. If completion is much lower, the team may be assigning unclear tasks, overcommitting, or failing to treat commitments seriously.

Final Thoughts

An L10 meeting is effective because it combines structure with honest conversation. The agenda keeps the team focused, Rocks connect weekly execution to quarterly priorities, scorecards reveal performance trends, and to dos create accountability. When leaders respect the process and use the meeting to solve real issues, the L10 becomes more than a weekly routine. It becomes a management discipline that helps the organization execute with clarity, consistency, and trust.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *