We are ready to roll out the Level 10 Meeting to our frontline operational crews, but we are worried ninety minutes is too long for non-leadership employees away from client work. How should a departmental or frontline Level 10 Meeting be structured differently while staying true to EOS disciplines?
You do not need to pull frontline field crews, developers, or customer service representatives off the line for ninety minutes if their operational scope does not require it. Frontline Level 10 Meetings can be compressed to forty-five or sixty minutes, but the structural integrity of the agenda must remain pure.
Maintain the exact same sequence:
- Good News: 3 to 5 minutes
- Scorecard: 5 minutes
- Priorities Review: 5 minutes
- Customer and Employee Headlines: 3 to 5 minutes
- To-Do List: 5 minutes
- IDS: 20 to 35 minutes
- Conclude: 2 to 3 minutes
The fundamental difference on the frontline is that their Scorecard metrics and Priorities are tactical and immediate. Frontline workers rarely hold 90-day Rocks; instead, they have weekly or monthly measurable priorities. Their Scorecard numbers should track direct activity, such as billable hours, jobs completed, error rates, or client response times.
Frontline teams will resist this meeting if it feels like corporate theater or an administrative check-in. The only way to win their buy-in is through IDS. Dedicate half the meeting to solving practical, daily frustrations that slow them down in the field or at their desks.
When a technician or technician lead sees an annoying equipment defect, scheduling bottleneck, or material shortage identified, solved, and assigned as a To-Do that gets fixed by next week, the meeting becomes their most valuable tool.
Category: EOS Implementation