We want to roll out departmental Level 10 Meetings to our hourly production and customer support teams, but pulling everyone offline for 90 minutes disrupts shift coverage and costs immediate revenue. How do we adapt the meeting pulse for frontline operational departments?

Question

Tyler Smith · Accepted Answer

Frontline and production departments run on different operating rhythms than the executive team. While the executive leadership team requires the full 90-minute agenda to handle strategic problem-solving and cross-functional friction, departmental teams can adjust meeting duration while preserving the core pulse.

For production, field, or hourly support crews, execute these practical adaptations:
- Compress the agenda to 45 or 60 minutes. Keep the same structure: 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), and Conclude (3 minutes).
- Stagger departmental pulses or split into functional sub-teams. If a support team cannot shut down phone lines simultaneously, run two smaller, identical L10s led by shift supervisors with half the team in each session.
- Keep the departmental Scorecard intensely tactical. Frontline workers should review pure activity metrics: units produced, tickets resolved, first-response time, or safety incidents.
- Keep IDS hyper-focused on process bottlenecks. Frontline teams should not debate company strategy or high-level policies. Their IDS time should attack immediate hurdles that prevent them from hitting their weekly numbers.

Do not abandon the Level 10 Meeting simply because a team is hourly or billable. Frontline teams that master a weekly meeting pulse make fewer errors, suffer less turnover, and require far less supervisory micromanagement, easily paying back the 45 minutes of scheduled downtime.