A program reports ninety percent of milestones complete, every workstream green, and the budget on plan. Three months later, the capability it was funded to deliver is still not in use. Nothing in the reports was false. They were measuring the wrong thing.
Activity measures what the organization did: tasks closed, deliverables submitted, hours spent. Progress measures what changed as a result. The two move together often enough that it is easy to treat one as the other, and they diverge often enough that doing so is expensive.
Why activity takes over
Activity is available. Every project tool counts tasks, and every team can report what it finished this week. Outcomes are harder. They lag, they depend on more than one team, and they require someone to define in advance what change would count as success. Under schedule pressure, reports drift toward what can be counted, and reviews drift toward the reports.
Three questions that tell them apart
- What changed, and for whom? If the answer describes only work completed, the report is showing activity.
- Which measure moved? Progress should appear in a measure tied to an objective, not only in a project plan.
- What would we stop if this went badly? If nothing would change, the item is being tracked, not managed.
A program can close every task in its plan and still miss the outcome it was funded for.
What to change in the report
Keep the activity measures. Teams need them to run their work. Move them down a level and put two things above them in the leadership view: the outcome measure each initiative is meant to move, and the decisions currently waiting on leadership. A status meeting built on those two items tends to be shorter, and it tends to end with something decided.
For a fuller treatment of how initiatives connect to measures and outcomes, see From strategy to owned work.