Hard Decisions Are Where a Strategy Becomes Real
The organization learns the actual strategy from hard decisions, and closing the gap between an event and its explanation is an operating function of the executive team.
Most companies hold two kinds of all-hands meetings. The first kind announces the strategy. The deck is polished, the priorities are named, the future state is compelling, and the room is full. Ask people what was said a quarter later and most will remember the theme and little else. The second kind announces a hard decision: a significant workforce reduction, a restructuring, the exit from a business the company had described as core. People remember that meeting for years. They remember who delivered the news, how long the explanation lasted, whether questions were taken, and what the leaders moved on to next.
Leadership teams tend to weight these two meetings backwards. Months of preparation go into the strategy announcement, because it is understood to be the moment the strategy is communicated. The hard-decision meeting is treated as an event to be managed through: legal reviews the language, a careful statement is prepared, the session is kept short, and the goal is to steady the organization and return to normal operations. The organization weights them the other way around. The announcement tells people what leadership intends. The hard decision tells them what those intentions are worth under pressure. Whatever the deck says, the organization learns the actual strategy at the second meeting.
Across the enterprise operating-model work I have led and been close to, this pattern has held with uncomfortable consistency. My position is that consequential decisions are where a strategy becomes real to the organization, that employees measure the gap between the size of an event and the interpretive effort leadership spends on it, and that closing this gap is an operating function of the executive team, with definable parts and non-delegable ownership, rather than a communications task.
The gap employees measure
When something consequential happens, the people affected perform a simple assessment. They weigh how much the event changed their world against how much effort leadership spent helping them understand it. A reduction that removes a meaningful share of their colleagues, a reorganization that changes who they work for and what they own, the loss of a customer that anchored their business unit: these register as large. If leadership treats the event as large, explains it, connects it to the direction, and returns to it as consequences unfold, the assessment concludes that leadership understands what is happening. If leadership acknowledges the event briefly and moves on, the distance between the event’s magnitude and its treatment becomes information in its own right. It supports only two readings: leadership does not grasp the size of what just happened, or leadership grasps it and would rather not explain it. The first reads as incomprehension, the second as evasion, and both withdraw credibility from every statement about direction leadership has made.
The most common form of this failure has a recognizable shape. After difficult news, leadership pivots to the positive material: recent wins, growth ahead, the opportunity the company is positioned to capture. The motives are usually sincere. Leaders want to restore confidence, protect morale, and keep fear from compounding, and they believe dwelling on the event will do the opposite. But confidence is an inference people draw from evidence, and an organization that has just absorbed a hard event is looking for one specific kind of evidence: that leadership understands the event and has a considered response to it. Celebratory material offered in place of that evidence is experienced as avoidance, however it was intended. This is narrative substitution, positive corporate messaging doing the job that interpretation was supposed to do, and it leaves the organization with communication but without meaning.
The vacuum does not stay empty. People assemble their own explanation from what they can observe: which work is still funded, which roles were removed, what leaders inspect and what they have stopped asking about, which contradictions are tolerated, and how leadership behaved the last time something like this happened. The informal narrative built from those observations tends to defeat the official one for a structural reason. It explains more of what people can see. An official account that skips past the reduction explains less than a rumor that accounts for it, so the rumor spreads because it does more explanatory work, and it is usually less charitable than the truth leadership declined to tell.
A strategy that cannot explain the decision
There is a useful test buried in all of this. A strategy that is real can explain any hard decision the company makes, and it can do so specifically: which businesses or capabilities are being exited, which are being protected, what the resulting shape of the company is supposed to enable, and why this decision moves toward that shape rather than away from it. Nothing about passing the test requires confidential detail; it only requires that the decision was actually derived from the strategy, because a derivation that exists can be described.
When leadership cannot make that connection, employees are left with two possibilities. Either the strategy is a narrative maintained for external audiences while decisions are made on other grounds, or the decision was a cost action taken under pressure and dressed in strategic language afterward. Both happen, and organizations are good at working out which one they are watching. The damage extends well past the event itself. Once one major decision proves unconnected to the stated direction, every subsequent statement of direction is discounted, because the organization has learned that the strategy does not constrain what leadership actually does.
A related failure compounds this one: structural and cost actions consistently move faster than operating clarity. New reporting lines, consolidated functions, and reduced teams arrive months before the answers that would make them usable, about how decisions will now be made, which capabilities the company intends to keep, what work should stop, and who owns which outcomes. The organization experiences the consequences of the strategy before it can use the strategy for anything. The behavior that follows is predictable. People hold information, defer decisions, preserve optionality, optimize for visibility, and in some cases quietly leave. Leadership tends to read this as resistance or disengagement, and occasionally it is. Far more often it is a rational response to unexplained consequence. People cannot align to a direction they can only infer, and they will not take risks against a direction that might change again without explanation.
Sense-making is an operating function
What an organization needs after a consequential event has a definable shape, which is what makes it an operating function rather than a matter of communication talent. Leadership needs to state what happened at the scale the audience experienced it, rather than the scale that is comfortable to present. It needs to share the reasoning that can be shared: the facts that drove the decision, the alternatives that were considered, the trade-offs that were accepted. It needs to say what changes and, just as deliberately, what does not. It needs to name the uncertainty that remains instead of smoothing it over, because people can see the uncertainty anyway and watching leadership pretend otherwise is corrosive. And it needs to say how leadership will judge whether the decision worked, which is the part that makes everything else accountable rather than rhetorical. None of this requires unusual rhetorical skill. The hard part is the willingness to stand in front of the organization and do it.
The best-known public demonstration is Airbnb’s reduction in May 2020, when the company cut roughly 1,900 of 7,500 roles, about a quarter of its workforce. The chief executive published a long letter that stated the business reality plainly, revenue forecast at less than half the prior year, committed to the principle that every reduction map to a narrowed future strategy, explained which activities the company would scale back, and described how affected people were chosen and what the company would do for them. It was written under as much legal exposure and genuine uncertainty as any comparable announcement, and it is remembered as an act of leadership rather than damage control. What made it work was structural rather than stylistic: the reasoning was visible, the decision traced to the strategy, and people could tell what the company would look like afterward.
The standing objection to all of this is confidentiality, and the constraint is real but almost never binding. Walk through the components above and notice that none of them requires disclosure a legal review would strike. The facts that drive a hard decision are usually already visible in outline, in the revenue trajectory, the lost clients, the cost structure. Trade-offs can be described without exposing negotiations. Uncertainty can be named without publishing forecasts. When sense-making does not happen, the binding constraint is usually discomfort rather than legal exposure: the work is unpleasant to stand up and do, and leadership has categorized the explanation as a communications deliverable, which makes it feel safe to delegate.
That categorization fails because half the signal is who does the explaining. A well-crafted statement from the communications function carries different information than the people who made the decision spending their own time and attention explaining it, taking the questions, and returning to the subject in the weeks that follow. The organization reads the allocation of executive attention as instruction, a point I have argued elsewhere in this body of work, and nowhere is that reading more concentrated than in the days after a hard decision. Sense-making that has been delegated is sense-making the organization can see was declined.
The account the organization keeps
A practical way to hold all of this is that the organization keeps an account of the strategy’s credibility, and every hard decision either deposits into it or withdraws from it. A deposit is a decision explained in the strategy’s own terms, where the explanation survives contact with what people can observe afterward. A withdrawal is a decision left unexplained, or explained in terms the next quarter’s behavior contradicts. The balance shows up in a specific capability: whether employees can predict leadership’s decisions from the stated direction. Prediction is the real test of an operational strategy. When people can anticipate what leadership will choose, they can make trade-offs without escalating them, stop work without waiting for permission, and interpret the next surprise inside a coherent frame. A hard decision is the largest single data point they will ever be given, which is why mishandling one costs more credibility than a year of ordinary communication can rebuild.
The practical implication for a leadership team is that the explanation of a hard decision is part of the decision, entitled to the same rigor, the same senior ownership, and a deliberate budget of executive attention proportioned to the event’s consequence for the people absorbing it. Treating the explanation as an afterthought makes the decision strictly more expensive, because the organization pays the full price in severance, lost capability, and disruption, and receives none of the clarity that was available for the asking. The costs of a hard decision are paid either way. Explaining it is how the organization gets something back for the price.