Ask a chief executive where assurance sits on the balance sheet and expect a smile. Ask where it sits in the operating model and expect silence. That silence has a cost: company after company, I have watched trust treated as weather — commented on, never maintained — until the structure buckles.
The research beneath this essay followed fourteen organisations through punishing episodes: restructures, botched launches, regulatory hits. In each, the speed of recovery turned on a single factor above all others — not cash, not staff, but the assurance banked inside the senior team before the blow fell.
Treat it as weight-bearing kit and the maintenance log writes itself. Bridges get inspected whether or not faults are reported. Assurance merits the same: not an annual engagement survey everyone games, but light, regular checks of the joints under load.
Three joints take most of the load. First, promise-tracking: the share of pledges honoured, shown where everyone can see. Teams that mark themselves keep their word. Second, dissent habits: whether challenge appears inside the meeting or seeps into hallways later. Hallway challenge is rust — silent, spreading, structural. Third, mending pace: how fast a broken promise is admitted, owned and renewed. Rapid mending builds more assurance than spotless performance ever does.
None of this is soft-hearted. Across the fourteen cases, teams solid on all three joints resolved disputed matters 40 percent faster, and — more revealingly — their rulings stuck. Brittle teams re-fought the same questions quarter after quarter, funding it in executive hours.
Servicing the infrastructure
- Mark promise-keeping the way you mark cash — publicly, weekly.
- Haul dissent out of the hallway into the meeting, on purpose.
- Fix broken promises quickly; mending speed beats flawlessness.
- Check assurance before the shock, not after the damage.
The keynote version of this essay ends with a dare worth echoing: name one weight-bearing promise your team owes another, and set a date to examine it. Kit fails the moment maintenance lapses. Assurance behaves identically — except its breakdown posts no warning notices, only a meeting that goes quiet at exactly the wrong second.