We want to run departmental Level 10 Meetings for our field technicians and customer support reps, but pulling them off the floor for a full ninety minutes halts operations and kills client response times. How do we adapt the weekly pulse for frontline shift workers without compromising the EOS discipline?

Question

Tyler Smith · Accepted Answer

Frontline operational teams do not always need ninety minutes, but they do need the exact same structural discipline. You can compress the time, but you never alter the agenda flow or abandon the weekly pulse.

For shift workers, field technicians, or call center teams, run a compressed 45-minute or 60-minute departmental Level 10 Meeting. The time allocations scale down proportionally:

- Segue: 3 minutes
- Scorecard: 5 minutes
- Rock Review: 3 minutes
- Customer and Employee Headlines: 3 minutes
- To-Do List: 3 minutes
- IDS: 25 to 40 minutes
- Conclude: 3 minutes

Frontline meetings move faster because these teams are not debating company strategy or long-term financial modeling. Their metrics are binary, tactical, and immediate. Their issues are ground-level bottlenecks, such as a broken dispatch workflow, a missing field tool, or a recurring client onboarding defect.

To prevent operational disruption, stagger the meetings across shifts or run two identical sub-team meetings led by designated supervisors. What you must never do is cancel the meeting because the team is busy. When operational fires cancel your meeting pulse, you guarantee those same fires will burn all year. Give frontline teams a crisp, sixty-minute block to kill recurring friction, and watch your daily operational downtime drop.