Our department heads keep trying to elevate their localized operational metrics to the leadership team Scorecard, arguing that we need visibility. How do we draw a hard line between what belongs on the leadership team Scorecard versus what stays on departmental scorecards?

Question

Tyler Smith · Accepted Answer

To protect the sanity of your leadership team, you must enforce a strict gatekeeping process for the leadership Scorecard. The leadership team Scorecard is not a compilation of everything happening in the business. It is a high-level instrument panel designed to show if the entire enterprise is on track. If a department head argues that their metric needs visibility on the leadership Scorecard, apply a simple rule. A metric only makes it to the leadership level if a drop in that number forces a pivot from the entire leadership team, not just one department.

If a metric can be resolved entirely within the department, it must remain on that departmental scorecard. For example, individual team member task completion or specialized software uptime belongs on the operations scorecard. The leadership Scorecard should only track the macro-level indicators that directly impact the company's overall health, such as total weekly billable hours or overall customer satisfaction scores.

The Integrator must act as the ultimate gatekeeper here. During your weekly Level 10 Meeting™, reject any attempts to elevate localized operational details. Remind the team that the leadership Scorecard is limited to five to fifteen vital numbers for a reason. Keeping it lean ensures that you do not lose sight of the forest for the trees. If a department head needs to track their internal metrics, they can manage those within their own departmental Level 10 Meeting™. Keep the leadership team focused on steering the ship.