The Promise Ledger

Why change fails in the accounting, not the communication Every few years, most organisations run the same experiment without realising it’s an experiment.

They announce a significant change: a restructure, a merger, a new operating model, a transformation with a capital T. They invest heavily in the announcement: the narrative, the town hall, the cascade pack, the FAQ that anticipates forty-one questions. And then, over the following months, they watch trust, engagement and discretionary effort behave in ways the comms plan never predicted, and they diagnose the problem as resistance to change.

The diagnosis produces the standard prescription: more communication. Another town hall.

A refreshed narrative. Change champions. And when that doesn’t work either, the final diagnosis arrives, the one that ends every failed transformation review: “we underestimated the culture.”

I want to offer a different account of what happened, because I’ve watched this experiment run across banks, agencies and care organisations for 25 years, and I no longer believe the problem is resistance, or culture, or communication volume.

The problem is accounting.

Change is a promise-generating machine Start with what a change announcement actually is, stripped of its production values.

It’s a batch of promises. A large batch, issued all at once, to an audience of professional listeners.

Some of the promises are explicit, and leaders know they’re making them: “There are no planned redundancies.” “Nothing changes for your clients.” “Decisions will be made by March.” “You’ll hear it from us first.”

Some are implicit, and leaders often don’t know they’re making them, which doesn’t reduce their status as promises by one degree: “We’ll be consulting before decisions are made”

contains the promise that consultation can alter the outcome. “We value your feedback on this” promises the feedback goes somewhere. “This is about setting us up for growth”

promises that the pain has a purpose that will eventually be visible. Even the tone is a promise: a leader who says “I’ll be straight with you” has just issued a commitment that every subsequent sentence will be audited against.

And here’s the part the comms plan never models: everyone listening writes it all down. Not literally, though sometimes literally. People keep a ledger, and the ledger has two columns, kept and broken, and every promise from the announcement eventually lands in one of them.

“You’ll hear it from us first.” And they did, before the media, before the rumour mill. Entry:

kept.

“No planned redundancies.” Fourteen weeks later, there were. The word “planned” was doing more work than anyone admitted. Entry: broken, with an asterisk that makes it worse, because everyone can see the lawyering.

“We’ll genuinely consult.” The consultation ran for three weeks, the feedback was themed into a deck, and the final structure was identical to the leaked draft from before the consultation began. Entry: broken, and this one carries a compounding penalty, because a fake consultation doesn’t just break its own promise. It teaches people that the next invitation to participate is theatre, which quietly poisons every future ask.

Change succeeds or fails on the closing balance of that ledger. Not on the quality of the narrative. Not on the number of town halls. On whether, when people total the columns at the end, the organisation said true things and did what it said.

The three properties of the ledger If the ledger were simple, managing it would be simple. It has three properties that make it far more demanding than any comms plan accounts for, and each one connects to something this series has already established.

The ledger is cumulative. No change program starts at zero. This restructure inherits the closing balance of the last one, and the one before that, going back as far as institutional memory reaches, which is much further than leaders assume. An organisation whose previous transformation broke its central promises begins the new one in deficit: the same words, from the same podium, are now discounted before they’re finished being said. This is why identical change programs, run with identical skill, land completely differently in different organisations. They’re not being received on their merits. They’re being received against a balance. Leaders who’ve recently arrived make this mistake constantly: they inherit the deficit without knowing it exists, spend their credibility budget on promises priced at face value, and are baffled when the room doesn’t buy.

The ledger is collective. This is the moments-become-stories mechanism from earlier in this series, running at its highest velocity. An individual broken promise never stays individual.

The person who was told “your role is safe” three weeks before it wasn’t doesn’t just update their own ledger. Their story travels, at dinner tables, in corridor conversations, in the group chat that leadership doesn’t know exists, and every hearer posts the entry to their own ledger as if it happened to them. In change, there are no private promise-breaks. Each one is a broadcast, and, per the asymmetry we established early on, broken-promise stories travel faster and further than kept ones, because warning colleagues is a favour.

The ledger runs through the manager. People don’t audit change against the CEO’s town hall. They audit it against what their manager could tell them the next morning. The single most common point of failure in change, the exact line where the ledger starts haemorrhaging entries, is the moment the announced promise meets a manager who wasn’t briefed. The all-staff email promises clarity and support; the team turns to its manager and asks “what does this mean for us?”; and the manager, who learned about the change from the same email, shrugs. That shrug posts an entry to every ledger in the room, and the entry doesn’t say “our manager was out of the loop.” It says “the promise of being informed was false.” The medium essay was about this in general. Change is where it costs the most, fastest.

The survivors are the audience One more connection, and it’s the one change programs most consistently ignore.

Most significant changes involve people leaving: redundancies, spill-and-fill, roles “not going forward.” The departure essay established that every exit has an audience, the people who stay, and that the manner of the leaving teaches the stayers what they’re worth. In a restructure, this effect runs at scale and in high definition. The survivors, the exact people the transformation depends on for its promised benefits, watch precisely how their colleagues are treated on the way out. Whether the process is dignified or brutal. Whether years of service are honoured or processed. Whether the “support” promised in the announcement materialises as real help or a PDF about resilience.

The change’s biggest promise is always implicitly about the future: this will be a good place to be, on the other side. The treatment of the leavers is the first evidence about whether that promise is true, delivered to the survivors while their own ledgers are open and their attention is total. Organisations that economise on the leaving experience during change are defaulting on the transformation’s central promise in front of its entire intended audience, and then wondering why the survivors’ engagement scores fall through the floor of the dashboard we discussed in week three.

The counterargument: you can’t promise certainty Now the objection every honest change leader will raise, and it’s the strongest one in this series so far, because it’s not a dodge. It’s a real bind.

“Genuine change involves genuine uncertainty. I don’t know the final structure. I don’t know if there will be redundancies; it depends on decisions not yet made, numbers not yet in. If every statement becomes a ledger entry, the rational move is to say nothing, and saying nothing is its own catastrophe. You’ve made honesty unaffordable.”

The bind is real, but look carefully at what the ledger actually audits. It doesn’t audit certainty.

It audits accuracy. And there’s a form of promise that’s fully available in deep uncertainty:

promise the process, not the outcome.

“We don’t know yet whether roles will be affected. Here’s the date you’ll know. Here’s what we can control and what we can’t. Here’s what we’ll never do: you won’t read it in the media first, and no decision about a person will be communicated by email.” Every clause of that is auditable, and every clause of it can be kept, regardless of how the uncertainty resolves.

That’s a balancing ledger under conditions of total unknowns.

What breaks ledgers isn’t uncertainty. It’s false reassurance: the “no planned redundancies”

said to soothe a room, priced at the moment’s comfort and paid for, with interest, when reality arrives. False reassurance is a loan against a future the speaker doesn’t control. The ledger always collects.

So the answer to the bind is not silence, and it’s not bravado. It’s a discipline: in change, promise only what you control, be precise about what you don’t, and treat every soothing sentence as the debt instrument it is.

What to do with this on Monday

Write the promise inventory before the announcement goes out. Take the draft comms and underline every commitment, explicit and implicit, exactly as we did with the careers page seven essays ago. For each one, a single question: do we control this? Everything that fails the test gets rewritten as a process promise or removed. This one hour of accounting prevents most of the deficit.

Brief managers before the all-staff, every time, no exceptions. The manager’s ability to answer “what does this mean for us?” the next morning is the first kept or broken promise of the entire program. Build the cascade backwards from that conversation, not forwards from the town hall.

Close the consultation loop in three parts. What we heard. What changed because of it.

What we heard and didn’t change, and why. The third part is the one that gets skipped and the one that proves the consultation was real. A consultation without a published “what didn’t change and why” is indistinguishable from theatre, and will be filed as theatre.

Design the leaving before you design the announcement. If the change involves departures, the departure experience is the transformation’s most-watched promise. Resource it first, not last.

Open the ledger you inherited. If past changes broke promises, say so, specifically, before making new ones. “Last time, we said X and did Y. Here’s what we’re doing differently.”

Acknowledging the deficit is the only known way to stop paying interest on it. Pretending the balance is zero guarantees you’ll be charged as if it’s worse than it is.

The sentence to keep

Change doesn’t fail because people resist it. It fails when the ledger stops balancing.

People are not, in my experience, resistant to change. They’re resistant to being lied to, and they have long memories, shared memories, and a manager-shaped audit point for everything you announce. Run change as a promise portfolio, account for every entry, and the resistance that every methodology warns about mostly fails to materialise, because it was never resistance. It was accounting.

Next week, the quietest broadcast system in your organisation, and the one that teaches your values more clearly than the values do: who gets recognised, for what, in front of whom.

If you’ve sat in the all-team briefing and felt yourself opening the ledger, and you remember the exact sentence that made you start counting, reply or comment. Those sentences are a genre, and I’m collecting them.

Shehzad Bhanji writes The Promise Gap, a weekly perspective on the relationship between organisational promises and lived experiences. Across a 25-year international career spanning marketing, customer experience, employer brand, HR technology and people experience, he has worked across Australia, Asia, Europe, the Middle East and Africa.