Why green project reports hide red transformations
A project can hit every milestone and still miss the transformation. The two are not measured with the same instrument.
A project status is a statement about delivery. A transformation status is a statement about the business outcome. Most steering committees see only the first — and treat it as if it were the second.
The gap is structural. Delivery milestones are defined by the delivering party, are binary and refer to the system. Business outcomes are defined by the organisation adopting the system, are gradual and refer to the process. A program can close every milestone on time and still deliver a process the business cannot run on Monday morning.
Three questions expose the gap. First: which milestone in the plan measures whether the business can operate the new process? If the answer is “user acceptance test”, check whether the UAT refers to the system or to the process — in most plans it is the former.
Second: what is the definition of done for a country in the rollout? If it is “system available”, the rollout is reported as complete while the adoption work has not yet started. If it is “first month-end close in the new system without manual workarounds”, the report matches reality.
Third: who signs off the milestone? If the integrator signs, it is a delivery statement. If the process owner signs, it is a business statement. Both are legitimate; confusing them is not.
What to change. Keep the delivery report — it is necessary. Add a second, separate report with a few business-outcome indicators owned by the business: touchless-posting rate, number of manual workarounds, close duration, training status on the final configuration, key-user availability.
Report both side by side and resist the urge to merge them into one traffic light. The moment you average a delivery green with a readiness amber, you have recreated the problem.