Our project managers consistently report their weekly project milestones as on track, but client projects routinely finish late and blow past budgets. How are our managers gaming milestone measurables, and how do we fix it on our Scorecard?

Question

Tyler Smith · Accepted Answer

Project managers game milestone metrics by moving milestone target dates internally or narrowing the scope of what complete means without formal client change orders. They report on track because they met an artificially adjusted date. Fix this by replacing subjective milestone status with objective, hard-coded weekly leading indicators. Track three specific paired numbers: Client Change Orders Signed, Cumulative Variance Against Baseline Budget, and Milestones Completed Against Original Target Date. Original baseline dates never move on the leadership Scorecard without Integrator approval. If a milestone shifts, it is marked off track immediately, and the issue drops to the Issues List for IDS in the Level 10 Meeting. Pair completion with budget pacing: percent of project budget consumed divided by percent of deliverable verified by quality inspection. When PMs know original dates are frozen and budget burn is visible weekly, gaming stops. Accountability requires external truth, not self-reported comfort.