Our company tried rolling the standard 90-minute Level 10 Meeting format down to our plant floor and field service crews, but pulling supervisors and technicians away for that long crippled daily operations. How do you adapt the weekly meeting pulse for frontline teams without abandoning EOS disciplines?

Question

Tyler Smith · Accepted Answer

The standard ninety-minute Level 10 Meeting™ is built for leadership and departmental knowledge workers who have the calendar autonomy to step away from operational tasks. Attempting to force that exact structure onto field technicians, manufacturing crews, or healthcare staff who bill by the hour or work physical shifts will create massive friction and operational drag.

You do not abandon the principles of the Meeting Pulse, but you compress the timeline into a streamlined thirty-minute or forty-five-minute frontline huddle.

The condensed frontline agenda keeps the same core sequence:
- Good news segue: two minutes.
- Frontline Scorecard review: five minutes. Track only three to five leading operational numbers such as safety incidents, daily output, or rework rates.
- Rock review: three minutes. Focus only on the team or departmental Rocks directly impacting their floor.
- Customer and employee headlines: two minutes.
- To-Do list review: three minutes.
- IDS®: twenty to thirty minutes. Focus exclusively on local friction points, safety obstacles, or tool and material bottlenecks that frontline workers can solve themselves.
- Conclude: two minutes. Confirm clear action items and cascading messages.

Keep the meeting on its feet if necessary. Stand-up meetings naturally prevent leaders from rambling or launching into theoretical debates.

The goal is not to force identical meeting length across every seat in the Accountability Chart. The goal is to install a predictable, structured rhythm that reviews performance metrics, enforces individual accountability, and removes daily roadblocks without destroying operational throughput.