We are ready to roll out departmental Level 10 Meetings to our sales and operations teams, but we want to avoid them turning into bloated status updates. How do we structure departmental weekly pulses differently from leadership meetings?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings should follow the exact same structural flow as your leadership meeting, but the content must be highly tactical. The biggest mistake companies make is allowing departmental meetings to become lengthy, descriptive status updates where people simply list what they did last week.

To prevent this, focus heavily on the departmental Scorecard and Rocks. The metrics on a departmental Scorecard must be leading indicators of performance, such as calls made, invoices processed, or tickets closed.

When cascading this meeting pulse, ensure the facilitator keeps the reporting sections incredibly tight. If a metric is off-track, or if a departmental Rock is in jeopardy, it must go straight to the departmental Issues List.

The IDS portion of a departmental Level 10 Meeting should focus on solving immediate operational bottlenecks that prevent team members from hitting their weekly numbers. These issues should be solved at the lowest possible level of the Accountability Chart.

Only when a departmental team cannot resolve an issue themselves should it be rolled up to the leadership team's short-term Issues List. By keeping departmental meetings fast, focused, and action-oriented, you empower your managers to run their operations autonomously, making the business far more attractive to future buyers.