You Can Measure Trust With a Stopwatch

An executive I audited answered the question with a number and nothing else. The question: how long does it take for bad news to reach you once something breaks. Her whole answer: two days. No story, no complaint. The tone of someone reporting the weather, and the tone is the finding. A two-day delay on the information she most needs fresh had become a fact of her company, filed somewhere near the payroll date.

A few questions later, the same intake asks what her team doesn't tell her. Her answer: that they disagree with leadership's decisions, and that they don't feel supported.

Read those together. She knows the silence exists. She can name its shape. What she can't do is make it move faster. We dug into everything she'd tried. Always two days.

I now ask every company for this number, because it behaves consistently: bad news travels at roughly two days per level. One layer of management between the problem and the decision-maker, two days. Two layers, four. The exact figure varies; the compounding doesn't. Good news arrives the same afternoon. It carries itself, because people volunteer whatever makes them look good.

The extreme case shows the mechanism. A small restaurant team had their card system die mid-shift. The server told nobody. He took cash where he could, waved a few tables through, got the evening done. The owner found out at close, counting a drawer that made no sense. "The card system is down" was worth everything at seven and almost nothing at midnight.

Colin Powell: bad news isn't wine, it doesn't improve with age. The kitchen version is blunter. Problems age like milk.

So why two days per level? Bad news pays a toll at every level it climbs, and the toll has three booths.

Verification first. Nobody wants to raise a false alarm, so whoever saw the problem checks it again, asks a colleague, waits to see whether it happens twice. A day gone.

Softening second. The message gets translated into safer words on the way up. "The client is furious" becomes "some concerns on the client side." "This will slip three weeks" becomes "the timeline is tight." Each translation buys the messenger comfort and costs the listener meaning. By the time the words are safe enough to say, they're too vague to act on.

Timing third. The carrier waits for the right moment, or tries to fix the thing quietly and report a solved problem instead of an open one. Solved reads as competence; open feels like exposure. Sometimes the quiet fix works and you never learn how close it came. Sometimes it fails, and the problem arrives late and grown.

Notice what the booths are made of. Verifying is diligence. Softening is tact. Fixing before reporting is ownership. The delay is built out of virtues, which is why there's no villain to find, and why announcing "I want to hear problems earlier" changes nothing. You'd be asking people to stop being careful, considerate, and self-reliant. They won't, and they shouldn't have to.

Here's the reframe that earns its keep. We treat trust as a feeling and measure it, when we measure it at all, with a survey. Treat it as a speed instead. Trust is the transmission speed of true information, and the bad-news lag is its gauge: when did the thing break, and when did the person who could act on it hear? That gap is your number. You can measure trust with a stopwatch.

Ron Westrum built a whole typology of organizations on this axis: what a culture does with inconvenient information, and above all what it does to the people who carry it. Which is why "my door is always open" doesn't move the number. An open door only helps the person already standing in it.

What moves it is a rule about messengers. Report first, fix second, for anything touching delivery or a client. Raw wording is welcome; stale is the only failure. Then the half most companies skip: every messenger gets thanked, visibly, with the message judged separately from the messenger's performance. One punished carrier closes the road for everyone who watched it happen.

Leadership complies first. Norms are set by what leadership visibly does. The founder who opens Monday with her own freshest bad news, the deal she misread, the deadline she blew, does more for transmission speed than any anonymous survey. She's demonstrating, at her own expense, what happens to people who say true things: nothing. They get heard.

One condition, and it's load-bearing. This assumes your last messenger walked away whole. If the most recent person who carried bad news upward got a lecture about attitude, the channel is dead before it opens, and you owe a debt before you can ask for anything new: credit, publicly and by name, someone who brought you a hard message. Pay the old toll before announcing the road is free.

You'll know within a few weeks: at least one piece of bad news reaches you less than a day old, worded plainly enough to sting. If everything arriving is still stale and pre-cushioned, the booths are still collecting, whatever you announced.

The lag never goes to zero, and it doesn't need to. A team that checks before escalating is a team worth having. Know your number, then watch it the way you watch cash. Two days can become one. One can become an hour. Every hour you recover, the problem you hear about is younger, smaller, still an afternoon's work instead of a client call.

Unlike the survey, the stopwatch can't flatter you.