Most status reports do not lie. They omit. They round. They smooth. By the time leadership realizes the report no longer matches the operational truth, the corrective options have narrowed — sometimes drastically. Learning to read between the lines is among the highest-leverage governance skills a senior executive can develop.
2026-05-09
The first place narrative drift becomes detectable is in the structure of the data itself — what the report counts, how it summarizes, and what those summaries quietly leave out.
When the same risks and unresolved actions appear cycle after cycle without being materially advanced, the register has shifted from being a corrective mechanism to being an archival one. Each entry continues to be reviewed, owners continue to be assigned, mitigations continue to be discussed — and the underlying condition continues to persist. The longer a risk remains on the register without resolution, the lower the probability that the existing governance arrangements will resolve it. This is not a function of the risk itself; it is a function of whether the governance mechanism is structurally capable of acting on it.
The diagnostic question: is not “what is on the register” but “what has come off the register, and how.” A healthy register has a steady throughput: risks added, risks worked, risks closed with evidence. A drifting register accumulates without discharging.
A red, amber, or green dashboard is a useful summary device for executives who do not have time to read forty pages of narrative. It is a destructive device when it begins to substitute for that narrative. The color is a compression of judgment. If the underlying judgment is being progressively softened — if “amber” begins to absorb conditions that would previously have prompted a red — the dashboard remains colored but no longer conveys the same meaning. The color layer has drifted from the data layer.
The next place narrative drift becomes detectable is in the structural integrity of the report itself — its dependency map, its milestone discipline, its cross-stream coherence.
Status reports are workstream-shaped. Each delivery team or stream produces its slice. The composite picture is assembled centrally. What is frequently missing is the dependency map that links those slices together: when stream A reports “on track”, what is that dependent on from stream B; when stream B reports “amber on a known risk”, how does that risk propagate to stream A’s confidence rating. The absence of a maintained dependency map is the single most common structural defect in steering-committee reporting, and it produces a specific failure mode — composite green at the program level, composite red at the delivery level, with no formal mechanism to reconcile the two.
A milestone date appears in three consecutive reports without being re-validated against the latest plan, the latest dependency position, or the latest resource availability. The team is still working towards it. The date itself, however, has become an artefact — present in the report not because it has been re-confirmed but because it has not been formally re-baselined. Unchallenged milestones accumulate. By the time the steering committee asks the question “is this date still real”, the answer is frequently no — and has been no for several reporting cycles.
1. McKinsey & Company (2023). Delivering large-scale IT projects on time, on budget, and on value. mckinsey.com
2. KPMG (2023). Driving business performance through digital transformation. KPMG Global.
3. Flyvbjerg, B. & Budzier, A. (2022). Cost overruns and benefits shortfalls of IT projects. Saïd Business School, University of Oxford.
