Our sales and customer service managers claim that the standard 90-minute Level 10 Meeting agenda is too rigid for their fast-paced daily operational workflows. How do we adapt the cadence for transactional frontline teams without bastardizing the EOS model?

Question

Tyler Smith · Accepted Answer

Department managers often confuse operational velocity with real productivity. When frontline sales and customer service teams resist the Level 10 Meeting, it is usually because their current communication consists of noisy Slack messages, ad-hoc interruptions, and firefighting. They assume a 90-minute weekly meeting will slow them down.

You must not let departments invent custom meeting formats that abandon the core principles of EOS. However, frontline departmental meetings can be adjusted in length while keeping the structural framework completely intact.

For high-volume frontline teams like customer support or inside sales, running a 60-minute Level 10 Meeting is entirely acceptable. You maintain the exact same sequence:
- Good News: two minutes.
- Scorecard: five minutes, reviewing daily or weekly metrics like call volume, ticket resolution, or conversion rates.
- Rock Review: five minutes, checking departmental milestone completion.
- Customer and Employee Headlines: five minutes.
- To-Do List: five minutes, ensuring previous week accountability.
- IDS: thirty to thirty-five minutes, tackling the top two operational bottlenecks impacting the team that week.
- Conclude: three minutes, recap and rating.

What you must never compromise on is the discipline. The Scorecard review is reporting numbers, not telling stories. The IDS session is identifying root causes, not venting about difficult customers. When frontline managers master this structured cadence, they quickly realize that 60 focused minutes once a week eliminates dozens of disruptive interruptions throughout the business day.