EOS Hub

English

Slovenčina

English

Slovenčina

Appearance

L10 Meetings ​

The L10 (Level 10) Meeting is the heartbeat of EOS. EOS Hub provides a structured digital environment for running these weekly meetings with your team, guiding you through all seven segments.

INFO

New to the L10 Meeting format? Read the EOS Methodology: Level 10 Meeting page first for background on why this meeting structure works.

Creating a Meeting ​

To start a new L10 Meeting:

  1. Navigate to Meetings in the sidebar.
  2. Click New Meeting.
  3. Select the meeting date (defaults to today).
  4. The meeting is created and you are taken to the meeting view.

TIP

Only users with OWNER or ADMIN roles can create meetings. MEMBER users can participate but not initiate.

The Seven Segments ​

Each L10 Meeting follows a structured flow of seven segments. EOS Hub displays each segment as a step, guiding your team through the process.

1. Segue (5 minutes) ​

Start the meeting with good news. Each participant shares one piece of personal or professional good news. This sets a positive tone and helps the team connect.

In EOS Hub, participants can type their segue or share verbally while the facilitator advances the meeting.

2. Scorecard Review (5 minutes) ​

Review the team's weekly Scorecard. The meeting view displays all measurables with this week's values compared to goals.

  • Numbers that hit their goal are highlighted in green.
  • Numbers that missed their goal are highlighted in red.
  • Missing entries are flagged for follow-up.

TIP

Any measurables that are off track can be dropped to the Issues list directly from this segment.

3. Rock Review (5 minutes) ​

Review the status of each Rock for the current quarter. Rock owners report whether their Rock is On Track or Off Track.

  • On Track Rocks are displayed in green.
  • Off Track Rocks are displayed in red.

Rocks that are consistently off track should be dropped to the Issues list for discussion.

4. Headlines (5 minutes) ​

Share customer and employee headlines -- important news that the team should be aware of. Headlines are brief, informational updates. If any headline needs discussion, drop it to the Issues list.

In EOS Hub, team members can add headlines during the meeting. Each headline can be flagged as needing IDS with a single click.

5. To-Do Review (5 minutes) ​

Review To-Dos from the previous week. Each To-Do owner reports whether their item is Done or Not Done.

  • Done To-Dos are checked off and archived.
  • Not Done To-Dos can be carried forward to next week or dropped to the Issues list.

The goal is a 90%+ completion rate each week.

6. IDS -- Identify, Discuss, Solve (60 minutes) ​

This is the core of the meeting. The team works through the Issues list using the IDS process:

  1. Identify -- Prioritize the top three issues from the list.
  2. Discuss -- Dig into the root cause (not symptoms).
  3. Solve -- Agree on a solution, which usually becomes a To-Do.

In EOS Hub, the IDS segment displays the full issues list. The team can:

  • Reorder issues by priority
  • Move an issue to "Solving" status to indicate active discussion
  • Create To-Dos directly from the issue resolution
  • Mark issues as "Solved" when complete

WARNING

Resist the urge to skip straight to solving. The "Discuss" phase is critical for finding root causes rather than treating symptoms.

7. Conclude (5 minutes) ​

Wrap up the meeting:

  • Recap To-Dos -- Review all new To-Dos created during the meeting.
  • Cascading Messages -- Identify any information that needs to be communicated to the rest of the company.
  • Rate the Meeting -- Each participant rates the meeting from 1 to 10.

Meeting ratings are stored and displayed on the Dashboard for trend tracking.

Meeting Countdown Timer ​

When a meeting is in progress, a real-time countdown timer appears in the application header. This helps the team stay on track with time management.

How It Works ​

  • Countdown display -- A large, bold countdown showing the remaining time.
  • Elapsed time -- A smaller clock showing how long the meeting has been running.
  • Progress bar -- A full-width bar at the bottom of the header that shrinks as time passes.

Color Indicators ​

  • Green -- Normal meeting time remaining.
  • Red -- Less time remaining than the configured warning threshold.
  • Pulsing red (full bar) -- Meeting has exceeded its allocated time. The timer switches to show overtime (+MM:SS).

The meeting continues running until the facilitator manually ends it -- the timer does not auto-end the meeting.

Configuring Duration & Warning ​

Meeting duration and warning threshold are configurable per team in the Admin Panel:

  1. Go to Admin > Teams.
  2. Find the team and adjust Meeting Duration (default: 90 minutes) and Warning Threshold (default: 80 minutes).

TIP

The countdown timer survives page refreshes -- it uses the meeting's start time from the database, not browser state.

Meeting Duration Tracking ​

When a meeting is completed, the actual duration is calculated and stored. This duration is:

  • Displayed in the meeting history list (with a clock icon).
  • Visualized in the Dashboard as a Meeting Duration chart.

Meeting History ​

All past meetings are listed on the Meetings page. You can:

  • View the full record of any past meeting, including all segments.
  • See who participated and how they rated the meeting.
  • Review To-Dos and Issues that were created during the meeting.
  • See the actual meeting duration alongside the average rating.

Meeting Participants ​

All team members can view the meeting. Participation is tracked -- the meeting records who was present and who rated the meeting.

Best Practices ​

  • Start on time, end on time. The L10 Meeting is designed to last exactly 90 minutes (configurable per team). Use the countdown timer to stay on track.
  • Follow the segments in order. Do not skip or rearrange.
  • Keep Segue, Scorecard, Rock Review, Headlines, and To-Do Review brief. The bulk of the time (60 minutes) should be spent on IDS.
  • Rate honestly. The meeting rating is a tool for improvement, not a formality.
  • Create To-Dos, not discussions. When the team solves an issue, capture a specific, actionable To-Do.

AI-Enhanced Inputs ​

During meetings, many text inputs include an "Enhance with AI" button. This helps participants write clearer issue titles, more actionable to-dos, and better cascading messages. See AI Integration for details.

Built with VitePress

© 2026 EOS Hub. All rights reserved.