The Hidden Cost of Narrative Management

Narrative management is not dishonesty. It is something subtler and, in many ways, more dangerous. It is the progressive alignment of formal reporting toward what governance bodies want to hear, rather than what they need to know.

How it starts

It rarely begins as a deliberate choice. A program team faces a difficult reporting period. There are genuine problems. A technical issue that hasn’t resolved, a dependency that isn’t tracking, a risk that has materialised in ways that weren’t anticipated. The team knows this. The program manager knows this.

But the governance forum is next week. And the question that dominates the pre-forum preparation is not “how do we accurately describe the program’s condition?” It is “how do we present this in a way that doesn’t create more noise than we can manage?”

That is a reasonable human response to a difficult situation. Governance forums are not always environments where bad news is welcomed. Careers have been affected by programs that attracted too much executive attention. The incentives, often unspoken, often unconscious, point toward smoothing the narrative.

So the report is written. The problems are noted, but framed as being under management. The risks are listed, but their interactions and implications are not fully described. The dashboard stays amber rather than red, because red would require explanations that the team isn’t ready to give.

Nothing written is false. But the picture presented is not the picture that exists.

The compounding effect

The first instance of narrative management is almost costless. The governance forum accepts the report. The questions are manageable. The program continues.

But something has shifted. The baseline for what gets reported has moved. The next difficult period, the team returns to the same approach, because it worked last time. Gradually, the gap between reported condition and actual condition widens.

This is the mechanism that Diane Vaughan described in her landmark study of the Challenger disaster. She called it the normalisation of deviance, the progressive acceptance of conditions that would once have triggered concern, through repeated exposure to those conditions without immediate consequence.

In program governance terms, narrative management is normalisation of deviance applied to reporting. Each cycle of smoothed reporting makes the next cycle easier to justify. The threshold for what requires frank disclosure rises. The governance forum, receiving reports that consistently describe a manageable situation, loses the sensitivity to detect the conditions developing beneath the surface.

The cost that doesn’t appear in any report

Here is what makes narrative management so insidious. Its costs are almost entirely invisible until they are catastrophic.

The program that has been managing its narrative for twelve months does not look like a program in trouble. Its dashboard is amber, not red. Its governance forums are functioning. Its milestone reports show completion percentages. Its risk register is populated and maintained.

And yet, beneath that surface, conditions are accumulating. Technical decisions that should have been escalated have been deferred. Dependencies that were flagged as risks have not been resolved. The actual volume of rework required is substantially larger than what appears in any report.

When those conditions eventually surface, through an integration failure, an independent assurance review, an audit, the scale of the problem appears suddenly and without warning to governance bodies who believed they had adequate visibility. The Australian National Audit Office’s Major Projects Reports document this pattern repeatedly: programs that maintained acceptable formal performance indicators while accumulating the conditions for large, late-stage cost and schedule escalation.

The cost of narrative management is not visible in any single report. It accumulates in the gap between what is known and what is said.

The governance response that makes it worse

There is a cruel irony in how governance bodies typically respond when the gap finally becomes visible. The response is almost always to increase reporting intensity. More frequent updates, more detailed dashboards, more governance forums.

This response addresses the symptom, insufficient information, without addressing the cause, which is the organisational dynamic that filtered the information in the first place. An organisation that has been managing its narrative for twelve months does not suddenly report more candidly because the reporting cadence has doubled.

More reporting does not produce more honesty. It produces more narrative management, at a higher frequency.

What governance actually requires

The antidote to narrative management is not more reporting. It is governance environments that genuinely reward the surfacing of problems. Where bringing a red to a governance forum is treated as responsible management rather than program failure, where the absence of problems over an extended period is treated as a signal worth investigating rather than celebrated.

It also requires governance mechanisms that do not depend entirely on self-reported program data. Independent assessment, leading indicators of systemic health, direct engagement with the workforce provide the cross-reference that allows governance bodies to test whether the narrative they are receiving reflects the program’s actual condition.

Programs that successfully avoid the narrative management trap are distinguished not by better reporting systems but by governance cultures that make honesty safer than management.

That culture is harder to build than a dashboard. But it is the only thing that actually works.