tyler-smith.com · Questions & Answers

Several of our department heads prefer tracking percentages on our weekly Scorecard, such as our project completion rate or customer satisfaction percentage. Why does EOS warn against percentage-based metrics, and what should we track instead?

Percentages hide operational reality and destroy weekly accountability. A percentage is an abstraction that masks volume swings. If your customer support team reports a ninety percent customer satisfaction rate for the week, that sounds healthy. But if that percentage represents nine happy clients out of ten total tickets because inbound volume collapsed, or if it represents nine hundred happy clients out of one thousand tickets with one hundred furious clients blowing up your phone, the underlying reality is completely different.

The same problem infects project completion rates. Ninety percent of tasks completed does not tell you if you completed nine trivial administrative tasks while missing the single critical milestone that triggers client billing. Percentages also make it easy for team members to rationalize away missed targets by blaming statistical variance.

Track absolute whole numbers and raw counts on your weekly Scorecard. Track the exact number of support tickets resolved, the raw count of client escalations received, the total billable hours logged, and the specific number of project milestones achieved on schedule.

Whole numbers force absolute clarity. When your Scorecard says you had four project deadlines missed this week against a goal of zero, there is nowhere to hide. You drop the four misses to your Issues List, identify the root causes during IDS, and fix the operational breakdown. Use percentages for long-term strategic reviews, but run your weekly operational rhythm on hard, unvarnished integers.

Category: Scorecards & Data

← All questions