We run multiple shifts in our warehouse and field operations, and managers argue that pulling supervisors for a full 90-minute Level 10 Meeting stalls daily production. How do we adapt the weekly pulse for frontline departmental teams without destroying the EOS discipline?

Question

Tyler Smith · Accepted Answer

Keep the architecture sacred, but tighten the scope. A departmental Level 10 Meeting for frontline or plant operations still requires the same agenda sequence: Segue, Scorecard, Rocks, Headlines, To-Do List, IDS, and Conclude. If pulling supervisors for ninety minutes genuinely halts work, you can run a crisp 60-minute departmental pulse, provided you do not cut the ratio of problem-solving.

In a 60-minute format, allocate three minutes for Segue, five for Scorecard, five for Rocks, five for Headlines, five for To-Dos, thirty for IDS, and seven for Conclude. Frontline scorecards should track leading daily indicators like safety incidents, scrap rates, and units completed, not high-level financial metrics. The issues must be purely local: tool bottlenecks, maintenance snags, and schedule conflicts.

Do not cancel the pulse to save time. Skipping weekly alignment creates operational friction that wastes far more labor hours across the week than a single structured meeting. Train your departmental managers to hold the room to strict reporting. The frontline pulse succeeds when supervisors realize the meeting removes their daily frustrations rather than adding administrative red tape.