Our field and billable service teams push back on holding weekly departmental Level 10 Meetings, claiming a ninety-minute block destroys billable realization and leaves client emergencies unstaffed. How do you run the meeting pulse in high-utilization environments?

Question

Tyler Smith · Accepted Answer

When billable or field teams complain that a ninety-minute Level 10 Meeting™ harms utilization, they are confusing being busy with being productive. In reality, teams without a weekly meeting pulse bleed dozens of billable hours every week through frantic Slack threads, duplicate status questions, and reactive firefighting.

You can protect customer coverage while maintaining a strict weekly departmental pulse by applying three practical adjustments:

- Schedule during low-volume operational windows: Never hold a service department Level 10 during peak client call hours or primary field dispatch times. Move it to the very start of the week before field crews roll out, or run it late on a Friday afternoon when job sites wrap up.
- Stagger team coverage: If client coverage cannot be paused, divide the departmental roster into rotating shifts or designate an on-duty triage technician to handle urgent inbound tickets while the core team solves root issues.
- Compact the agenda to sixty minutes: For frontline teams executing routine daily tasks, an Integrator can approve a calibrated 60-minute Level 10 agenda. Allocate 5 minutes for Segue, 5 for Scorecard, 5 for Rock review, 5 for Headlines, 35 for IDS®, and 5 for Conclude.

The math is indisputable. A disciplined sixty or ninety-minute meeting pulse permanently resolves the operational friction that creates billable write-downs in the first place. You pay for the meeting once, or you pay for the chaos all week.