Our professional services firm has three distinct service lines with completely different delivery models. We are trying to keep our leadership scorecard under fifteen numbers, but each division leader is fighting to have their specific operational metrics on the main sheet. How do we structure our scorecard data so the leadership team stays focused on the enterprise level while department heads maintain local visibility?

Question

Tyler Smith · Accepted Answer

Trying to squeeze every operational metric from three distinct service lines onto your leadership team scorecard will result in data fatigue and useless ninety-minute meetings. Your leadership team scorecard must remain focused on the high-level health of the entire enterprise. To maintain this boundary, you must use the EOS® scorecard structure of a parent scorecard and departmental sub-scorecards. Your leadership scorecard should only contain five to fifteen macro-level metrics that represent the aggregate performance of the business. For the three division leaders, create separate departmental scorecards. Each division leader will track their specific, micro-level operational metrics on their own departmental sheets during their respective Level 10 Meetings™. On the leadership scorecard, you only track the roll-up numbers. For example, instead of tracking project delivery milestones for every single division on the main sheet, track a single metric: total company project milestones met on time. If that aggregate number is green, the leadership team moves on. If it turns red, the operations leader, who owns that metric on the Accountability Chart, must look at the departmental scorecards to identify which division is lagging. The operations leader then brings that specific division's issue to the leadership Level 10 Meeting™ for resolution. This keeps the leadership team out of the weeds while ensuring complete operational visibility across all service lines.