Announce the Why, Not Just the What

Every leader eventually delivers a decision people will not like. The schedule changes. The request is denied. The program everyone assumed was permanent ends. This is not a failure of leadership, it is the job, and no amount of listening makes it disappear, because organizations run on tradeoffs and every tradeoff has a losing side.

What is optional, entirely within your control, is whether the decision arrives with its reasoning attached. And that choice, more than the decision itself, is what your people will use to decide what kind of place they work in.

An unexplained decision is a fill-in-the-blank

Here is the mechanism. When a decision lands without a why, nobody experiences it as reasonless. People are meaning-making machines. They will supply a reason within the hour, assembled from whatever materials are lying around: old grievances, cafeteria theories, the assumption that budget or politics or favoritism decided everything. The organization abdicated the explanation, so the rumor economy wrote one, and the rumor economy is not a generous author.

This is why announcing the why is not a courtesy add-on. It is a competition for narrative, and the real reason only wins if it shows up. Decades of procedural justice research back this with unusual consistency: people's acceptance of outcomes, including unfavorable ones, depends heavily on whether the process appears reasoned, consistent, and honest about itself (Lind & Tyler, 1988). People can absorb no. What they cannot absorb is because I said so, delivered by silence.

What a why actually contains

A real why is not a slogan about strategic priorities. It is the tradeoff, shown. What was weighed against what. Which constraint was binding, the one the audience probably cannot see from where they stand. What was protected at the cost of what was surrendered. And when input was part of the process, where that input went: what was raised, what moved because of it, what did not and why.

For example, when a decision I make in response to a staff request turns out to generalize, I say so in the announcement and convert it to policy on the spot: we have agreed that going forward, project leads in this situation get two covered hours, therefore here is the rule. The therefore does real work. It tells people the decision came from reasoning that will apply tomorrow, to them, evenly, not from a mood that visited me on a Tuesday. Reasons that generalize are the difference between governance and weather.

Correct yourself the same way

The discipline gets tested hardest when the decision that needs explaining is your own mistake. Here I hold a rule I borrowed from my own weekly staff memos: corrections are visible, never silent. When a date I published was wrong, the correction shows the old date struck through and the new one bold, in front of everyone. Nobody has to wonder whether they misremembered, and nobody catches the organization quietly rewriting its record.

The same applies to reversed decisions. If new information changed my mind, the announcement says what the information was and when it arrived. This feels expensive in the moment, it is an admission, every time, and it is the cheapest trust an organization can buy. An institution that shows its corrections is an institution whose uncorrected statements can be believed. That is the entire mathematics of credibility, and silent edits spend it invisibly.

The compounding effect

None of this slows decisions down, which is the standing objection. The reasoning already exists, you did the weighing, that is what deciding was. Announcing the why is just refusing to discard the most valuable byproduct of the work you already did.

And it compounds in a specific direction. People who see reasons learn how the organization thinks. Over time they start anticipating the constraints, aiming their proposals at the real tradeoffs, and raising objections that engage the actual reasoning rather than the imagined politics. You are, decision by decision, teaching your people your decision function, and the return is input good enough to change it. An organization that hides its whys stays surrounded by guesses. An organization that shows them ends up surrounded by colleagues.