Strety’s Complete Guide to the Level 10 Meeting: Templates, Agendas & Best Practices

Put the 10 in your Level 10 Meeting with our complete guide. Includes free templates, agendas, and step-by-step instructions to run effective L10 meetings that solve issues and drive results.

90 minutes (or less) can transform your business week after week. Seriously. No more meandering discussions that lead nowhere. Stop leaving meetings wondering what you actually accomplished. Have focused, productive sessions that solve real problems and drive measurable results.

Welcome to the Level 10 Meeting — the backbone of the Entrepreneurial Operating System (EOS®) and the secret weapon of thousands of successful businesses worldwide.

This comprehensive guide will show you exactly how to run Level 10 meetings that your team will actually look forward to attending. You’ll get proven templates, step-by-step instructions, and real-world examples from businesses like yours that have transformed their operations by adding L10 meetings to their toolboxes.

Get ready to implement Level 10 meetings that consistently deliver results, solve issues permanently, and keep your team aligned on what matters.

Chapter 1: What is a Level 10 Meeting?

A Level 10 Meeting (often called an “L10”) is a structured, 90-minute weekly meeting format that’s part of the Entrepreneurial Operating System (EOS®). The name comes from the goal of every meeting: to be so effective and valuable that participants rate it a “10” on a scale of 1 to 10.

Created by Gino Wickman as part of the EOS® framework, the L10 meeting addresses the most common complaint about business meetings: they’re a waste of time. Instead of rambling discussions and unclear outcomes, L10 meetings follow a proven agenda designed to solve issues, maintain accountability, and keep everyone focused on priorities.

Why Traditional Meetings Fail

Most business meetings suffer from the same problems:

• Inconsistent timing/format/etiquette
• No clear agenda or structure
• Discussions that go off on tangents
• Issues raised but never resolved
• Unclear action items and ownership
• Too much talking, not enough solving

The Level 10 Meeting eliminates these issues through its disciplined structure and focus on problem-solving.

Core Purpose: Solving Issues and Maintaining Traction

At its heart, the L10 meeting serves two primary functions:

1. Issue Resolution: The majority of meeting time (60 out of 90 minutes) is dedicated to identifying, discussing, and solving the most important issues facing your team.
   
2. Accountability: Regular check-ins on key metrics, quarterly priorities (Rocks), and weekly commitments ensure nothing falls through the cracks.
   

Who Should Attend L10 Meetings?

L10 meetings work best with 3-7 participants who:

• Share common goals and objectives
• Have the authority to make decisions about issues discussed
• Are committed to the meeting cadence and format
• Can contribute meaningfully to issue resolution

This might be your leadership team, department heads, or any group that needs to stay aligned and solve problems together. At Strety, we have an L10 meeting for our leadership team, our product team, and our growth team, as well as running smaller meetings and 1:1s that loosely follow the L10 agenda. If you’re just getting started, try it with your leadership team, then cascade into more departments.

Chapter 2: The Level 10 Meeting Agenda Breakdown

The L10 meeting follows a precise 90-minute agenda with seven distinct components. Each section has a specific purpose and time allocation, creating a rhythm that becomes second nature with practice.

The 7 Components of a Level 10 Meeting

1. Segue (5 minutes)

Purpose: Transition everyone mentally into the meeting and create connection.

The segue isn’t just small talk — it’s an intentional way to help people shift from their previous activities into focused meeting mode. Good segue questions include:

• “What’s one thing you’re excited about this week?”
• “Share something good from your weekend”
• “What’s one word that describes how you’re feeling today?”

Keep it personal but professional, and ensure everyone participates briefly.

2. Scorecard (5 minutes)

Purpose: Review your most important weekly metrics to spot trends and identify issues.

Your scorecard should contain 5-15 key numbers that give you a pulse on your business. Each metric should have:

• The person accountable for that number
• The weekly goal or target
• The actual result
• A simple red/yellow/green status

During this section, simply report the numbers. If something is off track, add it to the issues list — don’t discuss it here.

3. Rock Review (5 minutes)

Purpose: Quick check-in on quarterly priorities to ensure they stay on track.

Rocks are your most important 90-day priorities. During this section:

• Each Rock owner gives a brief “on track” or “off track” status
• If a Rock is off track, add it to the issues list
• Keep updates to 30 seconds or less per Rock
• No discussion or problem-solving here

4. Headlines (5 minutes)

Purpose: Share important news, updates, and good news that everyone should know.

Headlines are for information sharing only — no discussion required. Good headlines include:

• Customer wins or feedback
• Employee achievements or milestones
• Important company updates
• Industry news that affects your business
• Personal news team members want to share

5. To-Do List (5 minutes)

Purpose: Review commitments from the previous week and ensure accountability.

Go through each To-Do from last week:

• Mark completed items as “done”
• Carry forward incomplete items (and discuss why in Issues if needed)
• Assign clear ownership for any new To-Dos
• Set specific due dates (typically by the next meeting)

This section reinforces accountability and prevents things from falling through the cracks.

6. IDS (Issues Solving Track) (60 minutes)

Purpose: The heart of the L10 — identify, discuss, and solve your most important issues.

This is where the real work happens. The IDS (Identify, Discuss, Solve) process includes:

• Identify: List all issues that need attention 
• Discuss: Talk through the most important issues to get to the root cause 
• Solve: Create specific action items that permanently resolve the issue

We’ll dive deeper into the IDS process in Chapter 6.

7. Conclude (5 minutes)

Purpose: Wrap up with clarity on next steps and meeting effectiveness.

The conclusion includes:

• Recap of new To-Dos assigned during the meeting
• Confirm next meeting date and time
• Rate the meeting on a 1-10 scale (goal is always Level 10)
• Quick feedback on what worked well or needs improvement

Time Management Tips

• Use a timer for each section
• Designate a timekeeper (rotate this role)
• When time is up, move to the next section
• Add any incomplete discussions to the issues list
• Trust the process — the structure works when you follow it

Chapter 3: Level 10 Meeting Templates & Downloads

To help you get started immediately, we’ve created comprehensive templates you can download and customize for your team.

Free Level 10 Meeting Agenda Template

A simple 2-page PDF with each item in the Level 10 Agenda, and spaces to print and fill in your team’s information.

Free Google Sheet Template: L10 Meeting, Scorecard, Rocks, Accountability Chart, V/TO

A comprehensive Google Sheet with the EOS® tools you need to get started: the Level 10 Meeting, Scorecard, Rocks, Accountability Chart, and V/TO. Simply go to the link, click “File” in the top left corner, and either select “Download” to get a copy on your local computer, or “Copy” to save a copy to your Google Drive.

Virtual Level 10 Meeting Setup Checklist

Want to make sure your Virtual Level 10 gets a 10? Run through this helpful checklist, created by remote work veterans.

Chapter 4: How to Run Your First Level 10 Meeting

Pre-Meeting Preparation (The Week Before)

1. Choose Your Team

Select 3-7 people who:

• Share common goals and responsibilities
• Have decision-making authority
• Can commit to weekly attendance
• Will engage constructively in problem-solving

2. Set the Rhythm

• Choose the same day and time each week
• Block 90 minutes (you may finish early as you improve — our team basically never goes more than an hour)
• Send recurring calendar invites
• Make attendance a top priority

3. Gather Your Data

Before your first meeting, collect:

• 5-15 key metrics for your scorecard
• 1-3 quarterly priorities (Rocks) per person
• Initial issues list from team input
• Any outstanding To-Dos from previous informal commitments

4. Prepare the Space

For in-person meetings:

• Quiet room with minimal distractions
• Whiteboard or flip chart for issues
• Timer (visible to all participants)
• Copies of the agenda template

For virtual meetings:

• Reliable video conferencing platform
• Screen sharing capability
• Digital agenda (Strety works beautifully for this ;))
• Good audio/video quality for all participants

During Your First Meeting

Start with Why

Before diving into the agenda, spend 10 minutes explaining:

• The purpose of L10 meetings
• How the format will benefit the team
• Why consistency and structure matter
• The commitment you’re making together

Follow the Format Strictly

Resist the urge to “customize” on your first few meetings:

• Use the timer religiously
• Move to the next section when time is up
• Don’t skip sections, even if they feel awkward initially
• Add items to the issues list rather than discussing them out of sequence

Practice the IDS Process

During your 60-minute Issues section:

1. Identify: Spend 10 minutes listing all issues
2. Prioritize: Order them by importance/urgency
3. Discuss: Talk through the top 2-3 issues only
4. Solve: Create specific To-Dos that resolve each issue

End with Honesty

Rate the meeting honestly (probably 6-8 for your first one) and discuss:

• What felt awkward or unnatural
• Where you saw value immediately
• What you’ll do differently next week
• Commitment to stick with the process

Post-Meeting Follow-Up

Within 24 Hours:

• Send meeting recap with all new To-Dos
• Update any tracking systems
• Schedule any follow-up conversations identified
• Begin preparing for next week’s scorecard

Throughout the Week:

• Check in on To-Do progress
• Add new issues to next week’s list as they arise
• Gather scorecard data
• Update Rock status

Chapter 5: Level 10 Meeting Best Practices

The Power of Consistency

The most successful L10 teams follow these non-negotiable practices:

Same Time, Same Channel

• Meet the same day and time every week
• Start and end on time, regardless of attendance
• Make L10 meetings the highest priority — they don’t get moved for other meetings
• Keep the same group of core attendees

Right People in the Room

Your L10 meeting should include people who:

• Share accountability for common results
• Have decision-making authority
• Can solve the issues that come up
• Are committed to the team’s success

If someone consistently can’t contribute to issue resolution or doesn’t share accountability for the results discussed, they probably don’t belong in this particular L10.

Making Meetings Engaging, Not Boring

Keep Energy High

• Start meetings with positive energy in the segue
• Celebrate wins in headlines
• Use humor appropriately (many teams love Strety’s customizable “tangent” alert)
• Keep discussions focused and productive

Encourage Participation

• Rotate who goes first in each section
• Ask for input from quieter team members
• Use the phrase “Is that true?” to check assumptions
• Create psychological safety for honest discussions

Handle Resistance Professionally

If team members resist the format:

• Acknowledge their concerns
• Explain the long-term benefits
• Ask for a 90-day trial commitment
• Lead by example with enthusiasm

Technology and Tools That Help

Essential Features for Virtual Teams

• High-quality video conferencing
• Screen sharing for agenda visibility
• Digital note-taking and task tracking
• Integration with existing productivity tools

How Strety Enhances L10 Meetings

Strety’s purpose-built L10 meeting tools include:

• Pre-built agenda templates that follow EOS® standards
• Real-time scorecard tracking with visual indicators
• Issues list that can be updated throughout the week, with threaded comments to have asynchronous discussion ahead of time
• To-Do assignment and tracking
• Ability to attach files, comments, and links to all items for fuller context
• Microsoft Teams integration for seamless workflow
• Meeting rating and improvement tracking

Common Mistakes to Avoid

Time Management Failures

• Don’t skip sections because you’re running late
• Don’t extend discussion time at the expense of issue-solving — move issues to long term or parking lot if it’s not urgent to solve them today
• Don’t let one person dominate conversation time
• Don’t start late or end early without covering everything

Process Violations

• Don’t solve issues during scorecard or Rock review
• Don’t turn headlines into discussions
• Don’t let To-Dos be vague or unassigned
• Don’t avoid difficult conversations

Cultural Missteps

• Don’t make meetings feel punitive or blame-focused
• Don’t allow personal attacks or unprofessional behavior
• Don’t ignore the meeting rating or feedback
• Don’t give up on the process after a few awkward sessions — practice makes for perfect 10s!

Chapter 6: The IDS Method Deep Dive

The Issues Solving Track (IDS) is the heart of the Level 10 Meeting and often the most transformative part for teams. Most business problems stem from issues that are identified but never properly resolved. IDS changes that pattern.

Understanding the Three Steps

Identify: Getting Everything on the Table

The goal isn’t to solve issues during identification — it’s to capture everything that needs attention. Good issues for the list include:

People Issues:

• Performance concerns
• Role clarity problems
• Communication breakdowns
• Skill gaps

Process Issues:

• Workflow inefficiencies
• Quality problems
• System failures
• Procedure gaps

Business Issues:

• Customer complaints
• Financial concerns
• Strategic challenges
• Market opportunities

Common Mistakes in Identification:

• Trying to solve issues as you list them
• Being too vague (“communication problems”)
• Avoiding difficult topics
• Not getting input from everyone

Discuss: Getting to the Root Cause

Once you’ve prioritized your issues, real discussion begins. The goal is to understand the true, root cause — not just the symptoms.

Effective Discussion Techniques:

• Ask “What’s really going on here?” multiple times
• Use “Is that true?” to check assumptions
• Encourage different perspectives
• Focus on facts, not opinions
• Dig deeper than the obvious answers

Example of Good vs. Poor Discussion:

Poor Discussion: “Sales are down this month. Let’s just work harder on prospecting.”

Good Discussion: “Sales are down this month. What’s different from last month when we hit our goals? Let’s look at lead sources, conversion rates, and sales activities. Is this a pipeline issue, a closing issue, or something else entirely?”

Solve: Creating Permanent Solutions

The solve step creates specific action items that address the root cause, not just the symptoms. Good solutions have these characteristics:

• Specific: Clear about what will be done
• Assignable: One person owns the action
• Achievable: Realistic given time and resources
• Measurable: You’ll know when it’s complete
• Time-bound: Has a clear deadline

Real-World IDS Examples

Example 1: Customer Retention Issue

Issue: “Three customers cancelled this month”

Poor IDS:

• Identify: “Customer cancellations”
• Discuss: “Customers are unhappy”
• Solve: “Try harder to make customers happy”

Good IDS:

• Identify: “Three customer cancellations in one month”
• Discuss: “What’s the pattern? All three cited slow response times. Our average response time increased from 2 hours to 8 hours over the past month. Why? We lost a customer service rep and haven’t replaced them.”
• Solve: “Post job opening by Friday (Sarah), interview candidates next week (Sarah), implement temporary escalation process for urgent requests (Mike by tomorrow)”

Example 2: Team Communication Problem

Issue: “Marketing and sales teams aren’t aligned”

Poor IDS:

• Identify: “Communication issues”
• Discuss: “People need to talk more”
• Solve: “Have more meetings”

Good IDS:

• Identify: “Marketing and sales teams creating conflicting customer expectations”
• Discuss: “Marketing promises 24-hour response, sales tells customers 48 hours. Marketing creates campaigns for Enterprise clients, sales focuses on SMB. No regular communication between teams about target customer profile or messaging.”
• Solve: “Weekly marketing/sales alignment meeting starting next Monday (Jennifer owns), update all customer-facing materials to consistent messaging (Tom by end of month), create shared customer profile document (both teams by Friday)”

Advanced IDS Techniques

The “Five Whys” Method

Keep asking “why” to get to root causes:

1. Issue: Customer complained about invoice errors
   1. Why? Invoice had wrong amounts
   2. Why? No reconciliation between billing and invoice
   3. Why? Data entry error in billing system 
   4. Why? New employee doesn’t know the system
   5. Why? No training process for billing system
2. Solution: Create billing system training checklist

Pattern Recognition

Look for themes across multiple issues:

• Are several issues related to the same process?
• Do multiple issues point to the same person or role?
• Are there systemic problems that create multiple symptoms?

Issue Cascading

Some issues need to be solved by other teams:

• Add them to departmental L10 agendas
• Track progress in your leadership meeting
• Set clear expectations for resolution timing

Chapter 7: Level 10 Meeting Troubleshooting

Even the best L10 meetings face challenges. Here are the most common problems and proven solutions.

Meetings Running Too Long

Symptoms:

• Consistently going over 90 minutes
• Rushing through final sections
• Not getting to all issues

Root Causes:

• Too much discussion in non-IDS sections
• Trying to solve too many issues
• Lack of timekeeper discipline
• Wrong people in the meeting

Solutions:

• Use a visible timer for each section
• Assign a rotating timekeeper role
• Add discussions to issues list instead of having them in other sections
• Focus on only 2-3 issues per meeting
• Evaluate if you have the right attendees
• Use a light-hearted but effective “tangent alert” like Strety’s custom GIFs

People Not Participating

Symptoms:

• Same 1-2 people dominate discussion
• Quiet team members don’t contribute
• Decisions made without full team input

Root Causes:

• Personality differences
• Fear of conflict or disagreement
• Unclear expectations about participation
• Power dynamics

Solutions:

• Rotate who speaks first in each section
• Directly ask quiet members for input: “Sarah, what’s your perspective?”
• Address dominating behavior privately: “I need you to help me get input from everyone”
• Create ground rules about equal participation

Same Issues Recurring

Symptoms:

• Similar problems come up week after week
• To-Dos don’t actually solve the underlying issue
• Team feels frustrated with lack of progress

Root Causes:

• Solving symptoms instead of root causes
• Vague or unassigned action items
• Lack of follow-through on commitments
• Wrong people assigned to solve issues

Solutions:

• Spend more time in the “Discuss” phase of IDS
• Ask “What would prevent this from happening again?”
• Make To-Dos more specific and measurable
• Assign issues to people with appropriate authority
• Track completion rates and adjust accountability

Technology Failures

Symptoms:

• Video/audio problems disrupting flow
• Inability to share screens or documents
• Lost meeting notes or action items

Root Causes:

• Inadequate technology setup
• Lack of backup plans
• No clear tech ownership

Solutions:

• Test technology
• Have backup communication methods
• Designate someone as “tech support” for the meeting
• Use platforms with good reliability (like Strety’s Microsoft Teams integration)
• Keep meeting notes in multiple locations

Personality Conflicts

Symptoms:

• Tension between specific team members
• Personal attacks or unprofessional behavior
• Avoidance of difficult but necessary conversations

Root Causes:

• Unresolved personal issues
• Conflicting work styles
• Poor conflict resolution skills
• Lack of ground rules

Solutions:

• Address behavior privately first, then in group if needed
• Establish meeting ground rules about professionalism
• Focus discussions on business impact, not personal preferences
• Use phrases like “Help me understand…” instead of “You’re wrong”
• Consider whether conflicting people need to be in the same L10
• Run a People Analyzer™ on conflict-prone people; the problem may be rooted in a core values issue

Chapter 8: Measuring Level 10 Meeting Success

The Meeting Rating System

Every L10 meeting ends with each participant rating the meeting on a 1-10 scale. This isn’t just a feel-good exercise — it’s a critical measurement tool.

What Makes a “Level 10” Meeting:

• Started and ended on time
• Followed the agenda structure
• Solved important issues permanently
• Everyone participated meaningfully
• Clear action items with ownership
• Team feels energized and aligned

Common Rating Ranges:

• 1-3: Major problems, consider stopping and addressing issues
• 4-6: Typical for new teams, some value but significant room for improvement
• 7-8: Good meetings with minor areas for improvement
• 9-10: Excellent meetings that teams look forward to attending

Using Ratings for Improvement:

• Track average ratings over time
• Discuss low ratings immediately: “What made this a 6 instead of an 8?”
• Celebrate when you consistently hit 8+ ratings
• Use rating trends to identify what’s working and what isn’t

Key Performance Indicators for Level 10 Meetings

Issue Resolution Rate

Track what percentage of issues identified actually get resolved permanently:

• Formula: (Issues resolved permanently ÷ Total issues identified) × 100
• Good target: 80%+ resolution rate
• Red flag: Same issues appearing multiple weeks

To-Do Completion Rate

Measure accountability and follow-through:

• Formula: (Completed To-Dos ÷ Total To-Dos assigned) × 100
• Good target: 90%+ completion rate
• Tracking: Note reasons for incomplete To-Dos

Meeting Efficiency Metrics

• Average meeting length: Should trend toward 90 minutes or less
• Issues solved per meeting: Typically 2-5 depending on complexity
• Attendance rate: Should be 95%+ for core team members

Long-Term Business Impact Metrics

The ultimate measure of L10 meeting success is business results:

Operational Improvements

• Faster problem resolution times
• Reduced recurring issues
• Improved cross-team communication
• Higher employee engagement scores

Financial Impact

• Revenue growth consistency
• Improved profitability
• Reduced operational costs
• Better cash flow management

Cultural Indicators

• Employee retention rates
• Internal promotion rates
• Customer satisfaction scores
• Speed of decision-making

Creating Your Measurement Dashboard

Consider tracking these metrics monthly or quarterly:

L10 MEETING SUCCESS DASHBOARD

Meeting Quality:

□ Average meeting rating: ___/10

□ Meetings held on schedule: ___%

□ Average meeting length: ___ minutes

Accountability:

□ To-Do completion rate: ___%

□ Issues resolved permanently: ___%

□ Rock completion rate: ___%

Engagement:

□ Attendance rate: ___%

□ Participation quality: ___/10

□ Team satisfaction: ___/10

Business Impact:

□ Revenue vs. goal: ___%

□ Customer satisfaction: ___/10

□ Employee engagement: ___/10

Chapter 9: Level 10 Meetings for Different Team Types

Leadership Team L10 Meetings

Participants: CEO/President, VPs, Department Heads 

Focus: Strategic issues, company-wide priorities, major decisions

Typical Scorecard Metrics:

• Revenue vs. goal
• Cash position
• Customer acquisition/retention
• Employee satisfaction
• Key operational metrics

Common Issues:

• Strategic planning and execution
• Cross-departmental conflicts
• Resource allocation
• Major customer or employee situations
• Market opportunities and threats

Best Practices:

• Keep highly strategic and avoid operational details
• Cascade important issues to departmental teams
• Focus on company-wide Rocks and priorities
• Model the behavior you want to see in other teams

Departmental L10 Meetings

Participants: Department manager plus 3-6 team members 

Focus: Departmental priorities, operational issues, team coordination

Sales Team Example:

Scorecard Metrics:

• New leads generated
• Conversion rates by stage
• Average deal size
• Pipeline value
• Customer retention

Common Issues:

• Lead quality and quantity
• Sales process improvements
• Customer objections and responses
• Territory or account management
• Product knowledge gaps

Operations Team Example:

Scorecard Metrics:

• Production efficiency
• Quality metrics
• Customer satisfaction
• On-time delivery
• Safety incidents

Common Issues:

• Process improvements
• Quality control
• Resource planning
• Customer service issues
• Equipment or system problems

Cross-Functional Team Level 10 Meetings

Participants: Representatives from multiple departments working on shared goals 

Focus: Project coordination, breaking down silos, shared accountability

Project Team Example:

Purpose: New product launch 

Participants: Product, Marketing, Sales, Operations 

Scorecard: Project milestones, budget, timeline 

Issues: Cross-team dependencies, resource conflicts, launch readiness

Customer Success Team Example:

Purpose: Improve customer experience 

Participants: Sales, Customer Service, Product, Finance 

Scorecard: Customer satisfaction, retention rates, support ticket resolution Issues: Customer feedback themes, process gaps, cross-team handoffs

Remote and Hybrid Team Considerations

Technology Requirements:

• High-quality video conferencing
• Screen sharing capability
• Digital agenda and note-taking
• Real-time collaboration tools

Engagement Strategies:

• Require cameras on for participation
• Use breakout rooms for smaller group discussions
• Rotate speaking order to ensure participation
• Send agenda and materials in advance

Time Zone Management:

• Find meeting times that work for all core participants
• Record meetings for those who can’t attend live
• Use asynchronous tools for status updates between meetings
• Consider regional team meetings that feed into global L10s

Large vs. Small Team Adaptations

Small Teams (3-4 people):

• May need shorter meetings (60 minutes)
• Can be more informal in tone
• Easier to reach consensus quickly
• May combine multiple types of issues

Large Teams (6-7 people):

• Stick strictly to 90-minute limit
• Need stronger facilitation
• May require more structured turn-taking
• Consider breaking into smaller groups if too unwieldy

Chapter 10: Technology and Tools for L10 Meetings

Essential Software Features

Core Requirements:

• Agenda Management: Pre-built templates that follow EOS® structure
• Scorecard Tracking: Easy input and visual status indicators
• Issues Management: Ability to add, prioritize, and track resolution
• To-Do Assignment: Clear ownership and due date tracking
• Meeting Notes: Comprehensive capture and distribution

Advanced Features:

• Integration with existing tools (Microsoft Teams, Slack, etc.)
• Mobile accessibility for busy leaders
• Rock tracking connected to quarterly planning
• Historical reporting on meeting effectiveness
• Automated reminders and notifications

How Strety Enhances L10 Meetings

Strety is purpose-built for EOS® implementation, with specific features designed to make L10 meetings more effective:

Seamless Microsoft Integration:

• Teams Integration: Run meetings directly within Microsoft Teams
• To-Do Sync: Automatically sync action items with Microsoft To-Do
• SSO: Single sign-on eliminates password friction
• Create Item (Issue, Headline, or To Do) directly from Microsoft Teams Chat or email in Outlook

Meeting-Specific Features:

• Timer: Built-in timing for each agenda section
• Tangent Alerts: Fun but effective way to keep discussions on track
• Real-time Collaboration: Multiple people can update agenda during meeting
• Instant Issue Capture: Add issues throughout the week, not just during meetings

Accountability Tools:

• Visual Scorecards: Red/green status makes trends obvious
• Rock Progress Tracking: Connect quarterly priorities to weekly progress as well as annual goals
• To-Do Follow-up: Automatic reminders and completion tracking
• Meeting Ratings: Track effectiveness over time
• To Do integrations: with your other favorite tools like Asana, Google Tasks, HubSpot, Monday.com, HaloPSA, ConnectWise, AutoTask, and Kaseya BMS

Reporting and Analytics:

• Issue Resolution Trends: See which types of issues recur
• Meeting Effectiveness: Track ratings and completion rates over time
• Team Engagement: Monitor participation and accountability metrics

Virtual Meeting Best Practices

Pre-Meeting Setup:

• Test technology 
• Send agenda and materials 24 hours in advance
• Ensure all participants have meeting link and materials
• Have backup communication method ready

During Virtual Meetings:

• Start with cameras on for better engagement
• Use screen sharing to display agenda
• Mute when not speaking to avoid background noise
• Take notes in shared document visible to all
• Use chat feature for questions or side notes

Platform-Specific Meeting Tips:

Microsoft Teams (especially with Strety integration):

• Use Strety app within Teams for seamless experience
• Leverage Teams chat for quick issues between meetings
• Record meetings for absent team members
• Use breakout rooms for smaller group discussions

Zoom:

• Use annotation features for collaborative note-taking
• Leverage polling for quick decisions
• Use waiting room to control meeting start
• Enable automatic recording for documentation

Google Meet:

• Share Google Docs for real-time collaboration
• Use Calendar invite to attach relevant docs
• Enable closed captions for better accessibility
• Use Meet’s new companion mode for hybrid meetings

Chapter 11: Advanced Level 10 Meeting Strategies

Cascading Issues Between Meetings

As your EOS® implementation matures, you’ll have L10 meetings at multiple levels of your organization. Managing the flow of information and issues between these meetings becomes critical. Proper use of cascading messages and issues helps keep communications documented and smooth, without sending a million follow-ups on various channels.

Upward Cascading:

Department → Leadership Team

• Major decisions that need executive approval
• Resource requests beyond department authority
• Cross-departmental conflicts
• Strategic implications of operational issues

Process for Upward Cascading:

1. Identify issues that need escalation during departmental L10
2. Add to leadership team issues list with context
3. Department head presents issue with recommended solution
4. Decision cascades back down to department team

Downward Cascading:

Leadership Team → Department Teams

• Strategic decisions that affect department operations
• Company-wide initiatives requiring coordination
• Policy changes or new procedures
• Resource allocation decisions

Process for Downward Cascading:

1. Leadership team makes strategic decision
2. Each leader adds implementation issues to their department’s L10
3. Department teams create specific action plans
4. Progress reports back up to leadership team

Horizontal Cascading:

Department → Department

• Cross-functional project coordination
• Shared customer or vendor issues
• Process handoffs between teams
• Resource sharing or scheduling conflicts

Cross-Team Issue Resolution

When Issues Span Multiple Teams:

1. Identify the Right Meeting: Where can this issue be solved most effectively?
2. Assign an owner: One person owns driving the solution across teams
3. Set Clear Timeline: When does this need to be resolved?
4. Create Accountability: How will progress be tracked and reported?

Example: Customer Onboarding Process Issue

• Identified in: Sales team L10 (customers confused about next steps)
• Involves: Sales, Customer Success, and Operations teams
• Solution Process:
  • Sales leader champions the issue
  • Cross-functional meeting scheduled within 48 hours
  • New process documented and implemented
  • Progress reported back to all three L10 meetings
  • Success measured in customer satisfaction scores

Quarterly Rock Planning Integration

Your L10 meetings should seamlessly connect to quarterly planning:

Week 13 (Last Week of Quarter):

• Review all Rocks for completion
• Identify lessons learned from the quarter
• Begin brainstorming priorities for next quarter
• Schedule quarterly planning session

Quarterly Planning Session:

• Review previous quarter’s results
• Set new Rocks based on annual priorities
• Ensure Rocks connect to weekly scorecards
• Update issues lists with Rock-related priorities

Week 1 (First Week of New Quarter):

• Review new Rocks in detail
• Break down Rocks into monthly milestones
• Identify potential obstacles and add to issues list
• Update scorecards to track Rock progress

Annual Planning Connections

Your weekly L10 meetings drive execution of your annual plan:

Vision/Traction Organizer (V/TO) Integration:

• 3-Year Picture: Discussed in leadership L10s quarterly
• 1-Year Plan: Drives quarterly Rock selection
• Quarterly Rocks: Tracked weekly in L10 meetings
• Issues: Many stem from obstacles to achieving the vision

Keeping the Big Picture Visible:

• Reference V/TO in quarterly planning sessions
• Connect weekly issues to annual priorities
• Celebrate progress toward long-term goals
• Adjust course when data shows you’re off track

Building L10 Culture Throughout Organization

Creating Consistency:

• Same Meeting Format: All teams use same basic L10 structure
• Common Language: Everyone understands terms like IDS, Rocks, Scorecard
• Shared Tools: Use same platform (like Strety 😉) across all teams
• Consistent Timing: All teams meet on same day when possible

Training New Leaders:

• L10 Facilitation Skills: How to run effective meetings
• IDS Mastery: Getting good at issue identification and resolution
• EOS® Understanding: How L10s fit into the bigger operating system
• Technology Training: How to use your chosen platform effectively

Measuring Cultural Adoption:

• Meeting Consistency: How many teams hold L10s regularly?
• Quality Ratings: Are teams achieving Level 10 meetings?
• Issue Resolution: Are problems getting solved permanently?
• Employee Engagement: Do people value their L10 meetings?

Chapter 12: Real-World Level 10 Meeting Success Stories

ServiceMaster of Salem – Transforming Meeting Culture

Background: Brian Greer runs four ServiceMaster Restore franchises across Oregon and was struggling with ineffective meetings before implementing EOS® and Strety.

The Challenge: “Our meetings sucked,” Brian admits candidly. “We were meeting to meet. And I hate that. I’m very passionate about it. If we don’t have anything to talk about, let’s not be here. It’s such a waste of time.”

The Transformation: After implementing L10 meetings with Strety, Brian’s experience completely changed:

“Our meetings sucked, and now they’re very good. They’re very structured; just about every meeting we have follows the L10 format, and it’s so nice to be able to customize each one. I also love the Tangent button in Strety, because we can get on tangents. And we always laugh when that tangent bird comes across the screen. It gets us back on track in a fun way.”

Specific Results:

• Meetings now consistently finish in 90 minutes or less
• Clear action items with ownership after every meeting
• Better visibility across four different franchise locations
• Improved accountability through scorecard tracking
• Team members actually look forward to meetings

Key Success Factors:

1. Consistency: Same day and time every week across all locations
2. Structure: Strict adherence to L10 format prevented rambling discussions
3. Technology: Strety’s integration made it easy for distributed team
4. Accountability: Clear metrics and follow-through on commitments

Valiant Technology – Driving Engagement Through Structure

Background: Georg Dauterman is president of an NYC-based MSP that transformed their culture by implementing EOS® and extending it company-wide through Strety.

The Challenge: Valiant was experiencing the common problem of passive meeting participation. Team members would sit through meetings without truly engaging or taking ownership.

The Solution in Action: Georg describes the transformation in meeting engagement:

“I think we’ve all had the experience, especially earlier in our careers, where you’re more of a passive observer in a meeting, sitting there thinking, ‘Man, I don’t know why we’re even having this meeting.’ Now we’re driving the engagement in Strety. And if there’s no need for the meeting, we end it early. Our goal is to try to finish, and if we don’t use the full meeting time, we’re like, ‘Cool, we get back 10 minutes’ — again, getting those small wins that add up. The idea is to be efficient and have enough structure to do it repeatedly.”

Measurable Outcomes:

• Moved from leadership-only EOS® to company-wide implementation
• Scorecard metrics visible to entire team created accountability
• 1:1 meetings became more structured and valuable
• Reviews and performance management integrated into regular rhythm
• Company culture shifted from “mystery meat” around performance to clear expectations

What Made It Work:

1. Visibility: Scorecards were made public, increasing accountability
2. Integration: Strety’s Microsoft Teams integration reduced friction
3. Comprehensive Implementation: Extended L10s beyond just leadership team
4. Cultural Shift: From passive observation to active engagement

Industry-Specific Adaptations

MSP/Technology Services Adaptations:

Valiant Technology, along with many other Strety customers, represent the MSP industry, which has specific L10 meeting needs:

Common Scorecard Metrics for MSPs:

• Ticket resolution times
• Customer satisfaction scores
• Monthly recurring revenue (MRR)
• New client acquisition
• Employee utilization rates

Typical Issues for MSP L10s:

• Client escalations and service delivery
• Technology stack changes and implementations
• Staffing and capacity planning
• Vendor relationships and negotiations
• Cybersecurity incidents and prevention

Technology Integration Benefits:

• PSA (Professional Services Automation) system integration
• Automated ticket-to-issue creation
• Real-time dashboard visibility
• Mobile access for field technicians
• Integration with Microsoft ecosystem

Professional Services Firm Example:

Scorecard Focus:

• Billable hour targets
• Project profitability margins
• Client retention rates
• Proposal win rates
• Staff utilization percentages

Common Issues:

• Project scope creep
• Resource allocation conflicts
• Client communication breakdowns
• Billing and collection challenges
• Staff development and retention

Manufacturing Company Example:

Scorecard Metrics:

• Production efficiency rates
• Quality defect percentages
• Safety incident tracking
• On-time delivery performance
• Inventory turnover rates

Typical Issues:

• Equipment maintenance and downtime
• Supply chain disruptions
• Quality control processes
• Workforce scheduling
• Continuous improvement initiatives

Before and After Scenarios

Scenario 1: The Chaos Meeting → The Level 10 Meeting

Before (Traditional Meeting):

• Started 10 minutes late waiting for stragglers
• No clear agenda, just “What’s on everyone’s mind?”
• 45-minute discussion about one customer complaint
• Multiple side conversations and tangents
• Ended with vague commitments: “Let’s keep an eye on this”
• No follow-up mechanism
• Meeting rating: 4/10

After (Level 10 Meeting):

• Started exactly on time with full attendance
• Clear agenda followed strictly with timekeeper
• Customer complaint identified, root cause discovered (process gap), specific solution implemented
• Three other issues also resolved with clear ownership
• Ended with recap of five specific To-Dos with deadlines
• Follow-up built into next week’s agenda
• Meeting rating: 9/10

Scenario 2: The Status Update → The Problem-Solving Session

Before:

• Most of meeting spent on status reports
• Problems mentioned but not solved
• Decision-making postponed indefinitely
• People left with same issues they brought
• Frustration with “meeting about meetings”

After:

• Status updates condensed to 5-minute scorecard review
• 60 minutes dedicated to solving actual problems
• Decisions made in real-time with right people present
• Action items created to prevent issues from recurring
• Team energized by progress and resolution

Frequently Asked Questions about Level 10 Meetings

How often should we have Level 10 meetings? 

Weekly, same day and time. This consistency is crucial for building momentum and maintaining accountability.

Who should facilitate the L10 meeting? 

The team leader initially, but facilitation can rotate among team members as they become comfortable with the format.

What if we don’t have issues to discuss? 

If you truly have no issues, the meeting can end early. However, most teams find that the structured format helps surface issues they weren’t previously addressing.

How do we handle confidential topics in L10s? 

Confidential personnel or financial issues can be handled in separate meetings. The L10 should focus on issues the entire team can help solve.

Can L10 meetings work for remote teams? 

Absolutely — it’s part of the reason our team at Strety is able to stay so connected even though we’re scattered all over the world. Many of our most successful customers are fully remote. The key is having the right technology and maintaining engagement through cameras and participation.

What’s the ideal L10 meeting size? 

3-7 people works best. Fewer than 3 lacks diverse perspectives; more than 7 becomes difficult to manage effectively.

How do we get buy-in from skeptical team members? 

Ask for a 90-day trial commitment. Most skeptics become believers once they experience consistent, productive meetings.

What if our meetings always run over time? 

Use a timer for each section and stick to it religiously. Add extra discussions to the issues list rather than extending sections.

Conclusion

The Level 10 Meeting isn’t just another meeting format — it’s a fundamental shift in how your team communicates, solves problems, and drives results. When implemented consistently with the right structure and tools, L10 meetings become the engine that powers your entire business operating system.

Key Takeaways

Structure Creates Freedom: The rigid 90-minute format with seven distinct sections actually creates more freedom by eliminating wasted time and unclear outcomes.

Issues Get Solved: Unlike traditional meetings where problems are discussed but not resolved, the IDS process ensures permanent solutions.

Accountability Becomes Natural: Weekly scorecard reviews and To-Do follow-ups create a culture where commitments are kept and results are measured.

Teams Get Aligned: Regular rhythm and shared language help everyone stay focused on what matters most.

It Gets Easier: The first few L10 meetings may feel awkward, but teams quickly develop a rhythm that makes meetings efficient and valuable.

Your Next Steps

1. Start This Week: Don’t wait for the perfect moment or perfect team. Begin with the templates provided and adjust as you learn.
   
2. Commit to Consistency: Same day, same time, same format for at least 90 days before making major changes.
   
3. Measure Progress: Track meeting ratings, issue resolution, and To-Do completion to see improvement over time.
   
4. Get the Right Tools: Whether you use spreadsheets, simple software, or a comprehensive platform like Strety, make sure your tools support the process rather than hindering it.
   
5. Be Patient with the Process: Great L10 meetings are built over time. Trust the structure even when it feels unnatural initially.
   

Continue Your EOS® Journey

Level 10 Meetings are just one component of the complete Entrepreneurial Operating System. To maximize their impact:

• Develop Clear Vision in your V/TO: Ensure your team knows where you’re going (blog on vision statements and mission statements here)
• Build Solid Accountability Charts: Get the right people in the right seats (guide and free accountability chart template here)
• Create Meaningful Scorecards: Track what matters most (scorecard overview here)
• Set Quarterly Rocks: Focus on 90-day priorities (how to set great goals here)
• Master the IDS Process: Solve issues permanently (IDS guide here)

Resources for Continued Learning

Essential Books:

• Traction by Gino Wickman (the foundational EOS® book)
• How to Be a Great Boss  by Gino Wickman and René Boer
• What the Heck is EOS? by Gino Wickman and Tom Bouwer

Strety’s EOS Implementation Wiki

Get Started with Strety: Ready to experience L10 meetings the way they’re meant to be run? Strety’s purpose-built EOS® platform makes Level 10 Meetings effortless and effective:

• Free 30-Day Trial: Test drive all L10 meeting features
• Microsoft Teams Integration: Meet where your team already works
• Expert Support: Get help from people who live and breathe EOS®
• Proven Results: Join thousands of teams already running successful L10s

Start Your Free Trial Today

Connect with EOS® Experts:

• Find certified EOS® Implementers in your area
• Access additional tools and resources at eosworldwide.com

Final Thoughts

The companies that consistently outperform their competitors aren’t necessarily the ones with the best products, the most funding, or the smartest people. They’re the ones that execute, communicate, and solve problems faster.

Level 10 Meetings give you the framework to become one of those companies. The structure is proven, the tools are available, and the only question remaining is: will you commit to making it happen?

Your next Level 10 Meeting could be the beginning of the most productive and aligned period in your company’s history. The question isn’t whether Level 10 Meetings work — thousands of companies have already proven they do. The question is whether you’re ready to stop having meetings that waste time and start having meetings that drive results.

Take the first step. Schedule your first Level 10 Meeting. Follow the format. Trust the process. Your team — and your business — will thank you for it.