Our project managers are consistently marking their weekly milestones green on the Scorecard, but we later discover they are pushing back deadlines informally to make their numbers look good. How do we design metrics to prevent this specific type of schedule manipulation?

Question

Tyler Smith · Accepted Answer

This type of schedule manipulation is a classic example of gaming the Scorecard. When project managers feel pressured to keep their numbers green, they will often renegotiate deadlines with clients or team members without reflecting that slippage in their weekly reporting. To stop this behavior, you must change how you define and measure project progress. Instead of tracking a subjective progress percentage or a self-reported status, put a metric on your weekly Scorecard called milestone variance. This number tracks the exact number of days a project milestone has slipped from its original baseline schedule. By measuring the variance against the baseline, any deadline movement is immediately visible as a red number. This objective data forces your team to bring schedule issues to the Level 10 Meeting for a healthy IDS session rather than hiding them. Pair this metric with a weekly customer satisfaction score to ensure that speed is not sacrificed for quality. Keeping your data transparent is crucial for maintaining the operational integrity of your business.