Why I Published the Bad News Before I Had the Full Story

Once the safety deviation was confirmed as real, the second crisis began — and it was internal.

In the book, four objections arrive in quick succession.

Legal urges restraint. Releasing information prematurely could create liability exposure.

Finance recommends a sequenced information strategy.

A senior commercial executive frames it as a fix-first, communicate-later issue.

And a board member calls to suggest they evaluate the market impact before escalating unnecessarily.

I want to sit with that vocabulary for a moment, because it is the most honest thing in the scene.

Nobody says cover it up.

Nobody in my experience ever does.

“Sequenced information strategy” is corporate code for delay, and everyone in the room knows it. But it is also a phrase you can say out loud in a meeting, write in minutes, and defend to a regulator.

That is what makes it dangerous.

The Case for Waiting Is Always Well-Argued

Here is what I have learned about these rooms: the argument for waiting is never stupid.

It is usually made by intelligent people with genuine responsibility for something real. Legal is right that premature disclosure creates exposure. Finance is right that markets react to incomplete information. The commercial lead is right that a fix is more useful than an announcement.

Each objection, taken alone, is defensible.

And taken together they produce a decision nobody would defend if it were stated plainly: we will tell people once it is safe for us to tell them.

The reason this happens is not weak character. It is that the costs are asymmetric and only one of them is visible.

The cost of disclosing early is immediate, quantifiable and lands on identifiable people. Share price. Client calls. A difficult board meeting. Somebody's quarter.

The cost of disclosing late is deferred, diffuse and lands on the institution — usually on people who were not in the room.

So the meeting reliably optimises for the visible cost.

Not because anyone is corrupt.

Because that is what meetings do when nobody interrupts them.

What He Actually Published

David calls an emergency meeting — not just Legal and Operations, but everyone. Safety. Engineering. Compliance. Finance. PR. Regional leads.

“We're not choosing the comfortable path. We're choosing the right one. Full transparency. Immediate action. Zero delay.”

Then he opens a post on the company's internal transparency system — public to every employee, timestamped, traceable — and writes:

“Safety deviation detected. Investigations underway. No final risk known yet. All employees are encouraged to contribute data, context, insights, and prior patterns. Transparency will guide our response.”

Read the third sentence again.

No final risk known yet.

That is the part I would underline for anyone who wants to understand what this actually costs.

He did not wait until he had a conclusion and then communicate it well. He published while he still didn't know — and said so, in writing, with his name on it.

Most transparency I see in organisations is retrospective. We investigate privately, reach a position, then disclose with the answer already in hand. That is not transparency. It is a well-managed announcement.

Publishing uncertainty is a different act, and a much harder one, because you are surrendering control of a story you cannot yet finish.

The Research Nobody in That Room Had Read

There is a body of crisis communication research on exactly this decision, and its conclusion runs directly against the instinct in most boardrooms.

It goes by the name stealing thunder — an organisation breaking the news about its own crisis before the crisis is discovered by the media or anyone else.

Laura Arpan and David Roskos-Ewoldsen tested it experimentally and published the results in Public Relations Review in 2005. Organisations that disclosed their own bad news first were rated more credible than organisations whose crises were revealed by someone else. The effect carried through to behaviour, not just opinion — consumer purchase intention was higher too.

Arpan's earlier work with Pompper found the same pattern among journalists, who rated communicators who stole thunder as more credible.

There is a further finding that seems counter-intuitive until you have lived it: proactive disclosure of unfavourable information tends to reduce the perceived severity of the problem.

Disclosing early doesn't make the thing look worse. It makes it look handled.

Now, two honest caveats, because this research is not a licence.

The first is that stealing thunder without follow-through is read, correctly, as a stunt. Later work is explicit that the effect depends on what you do next; disclosure as a substitute for remediation is worse than silence, because you have now put your name on it.

The second matters particularly here. Much of this work was conducted in Western contexts, and researchers have questioned how well it travels — in several Asian business cultures, restraint and reserve are read as competence rather than evasion.

I lead in India and have worked across Southeast Asia, and I think that caveat is real. But I would put it differently.

The cultural variable is the tone of disclosure, not the timing of it. How much you say, how loudly, and to whom — those are legitimately different across markets. Whether the people carrying the risk get to know while they can still act is not a cultural question. It is a safety question.

Why It Steadied Instead of Panicking

The board member calls back in a fury. “Do you understand the market panic this could cause? You've exposed us without having a final conclusion.”

The reply is the sentence the whole chapter turns on:

“I've exposed the truth. And truth, when handled correctly, stabilizes systems faster than silence.”

What happened next is the part I find most instructive, and it is not the reputational outcome.

Within minutes of the post, hundreds of people joined the thread. Engineers uploaded logs in real time. Compliance added context. Former engineers in other regions contributed history nobody had asked them for. Interns spotted pattern mismatches. Finance mapped the cost of remediation against the cost of concealment.

Within six hours the anomaly was isolated. Real, but containable.

Six hours.

A private investigation by a small trusted group would not have done that in six hours. It could not have. The information required was distributed across hundreds of people, most of whom nobody would have thought to ask.

This is the argument for disclosure that I think gets missed entirely, because we frame the whole debate around trust and reputation.

Concealment does not merely risk your reputation later. It cuts you off, right now, from every person who holds a piece of the answer and doesn't know you're looking.

You are choosing to solve a distributed problem with a small team, in order to protect a narrative.

The Test

Nobody struggles with this in principle.

The difficulty is that you never get to make this decision after you know. If you knew, it wouldn't be a decision.

You make it at 7:12 in the morning, with a clean-looking vendor email, an unconfirmed anomaly, four intelligent colleagues advising restraint for four defensible reasons, and no idea yet whether this is nothing or the end of the company.

That is the only moment the choice exists.

And what you publish while you still don't know is the truest thing anyone will ever learn about how you lead.