Organizations Cannot Change Until They Grieve What Is Ending

A leadership team learns that the future it planned for is not going to arrive.

The market moved. The merger did not create the expected value. A technology changed the economics of the business. Customers stopped behaving the way the strategy assumed they would. The product that once organized the company’s identity is becoming less important every year.

So the leaders schedule a strategy session.

They bring in new data, debate scenarios, revise the forecast, rename a few priorities, and leave with a transformation plan. Yet the plan still depends on the future they were supposed to have abandoned. The same products must remain central. The same people must retain authority. The same capabilities must be protected. The same story about why the organization matters must survive.

The strategy is new. The future underneath it is not.

In her episode of The Unfolding Thought Podcast, futurist and death doula Juli Rush brings an unusual idea into the work of foresight: sometimes a future has to be treated as something that is dying.

That language may sound too intimate for a strategy meeting. I think that is precisely why it is useful.

Organizations are usually comfortable discussing change as an analytical problem. They are much less comfortable discussing it as a loss. But a future can disappear before a company, community, or person has emotionally and structurally stopped living inside it. When that happens, more evidence does not necessarily create movement. The organization may understand what has changed and still be unable to act as though it understands.

A plan is never just a plan

We like to imagine that a strategic plan is a neutral description of choices, resources, and expected results. It is also a collection of promises.

It promises a salesperson that a market will continue to value the relationships she spent twenty years building. It promises a product leader that the expertise which made him important will remain important. It promises an executive that the organization he knows how to lead will still exist. It promises employees that the sacrifices they made were part of a story that leads somewhere.

Those promises are rarely written in the plan. They are still real.

This is one reason organizations can acknowledge a change intellectually while rejecting its consequences operationally. They accept that the market is different, then preserve the budget built for the old market. They say the business must become more customer-centered, then leave decision rights with the functions furthest from the customer. They describe a legacy product as declining, then require every new investment to protect its revenue, status, and internal constituency.

Research on organizational identity helps explain why this is so difficult. In one study of employees going through a corporate takeover, people adjusted better when they could experience either continuity with a valued identity or the gain of a credible new one. When neither path was available, strong identification with the old organization could deepen the loss.

The implication is not that leaders should preserve everything people value. That would make meaningful change impossible. It means that ending a plan can also disturb status, competence, community, memory, and identity. If leaders discuss only the business case, they leave the rest of the transition to happen underground.

Facts cannot end a future people are still living inside

When change stalls, leaders often assume the missing ingredient is information.

They commission another market study. Add detail to the transformation roadmap. Ask finance for a more precise forecast. Build a larger dashboard. Bring in a consultant to repeat what people inside the organization have already been saying.

Sometimes better evidence is exactly what is needed. Sometimes the evidence has already done its job.

The problem is that evidence can tell us a choice is no longer working without dissolving our attachment to it. In Barry Staw’s classic research on escalation of commitment, people became more willing to invest in a failing course of action when they felt personally responsible for having chosen it. More information did not automatically produce better correction. Responsibility could become a reason to defend the past.

Organizations make this effect collective. A strategy acquires sponsors, specialists, reporting lines, incentives, rituals, and language. Entire careers grow around making it appear sensible. By the time the evidence turns, the organization is not reconsidering an isolated decision. It is reconsidering part of itself.

This is why a declining initiative can survive years of disappointing results. Each round of investment is described as the final adjustment needed to prove the original idea. Each delay protects the people involved from having to decide what the ending means.

There is an important difference between uncertainty and ambiguity. Uncertainty means we do not yet know which outcome will occur. Ambiguity can mean we do not even agree on what is ending, what remains, or what the loss should be called.

Psychologist Pauline Boss developed the idea of ambiguous loss to describe losses that resist clean resolution. The organizational version is obviously not equivalent to the disappearance or psychological absence of a loved one. The concept is still useful. A company can announce a transformation while leaving the former system half-alive. People lose familiar roles but continue to be measured against their old responsibilities. A strategy is declared over, but no one can say which commitments are actually released.

Nothing has clearly died, so nothing can be fully grieved or replaced.

Resistance is often grief with an operational vocabulary

In business, grief rarely announces itself as grief.

It sounds like a request for more proof. A concern about timing. A debate over scope. A warning that customers are not ready. An insistence that the old process needs one more quarter. A proposal to run the new model without taking resources from the old one.

Any of those objections might be valid. Treating every disagreement as an emotional reaction is a convenient way for leaders to avoid criticism. But treating every objection as an analytical judgment is equally convenient. It allows the organization to negotiate indefinitely with a future that has already left.

The popular habit of assigning organizational change to a neat sequence of grief stages is not especially helpful. Grief is not a predictable staircase, and employees are not patients to be managed through denial on the way to acceptance. People can support a strategic decision and still mourn what it removes. They can be excited by a new role and miss the competence they felt in the old one. They can disagree with the decision for sound reasons while also feeling threatened by it.

The useful move is not diagnosing people. It is making the losses discussable.

What will employees no longer be proud of? Which relationships will become less central? What expertise will carry less authority? Which customer, community, or tradition will feel abandoned? What story about the organization will no longer be true?

If leaders cannot answer those questions, they probably do not yet understand the change they are asking other people to make.

Hospice: stop treating the incurable as a turnaround

Rush has since formalized her work as a framework of Hospice, Vigil, and Compost. Those three words describe work that conventional strategy often skips.

Hospice begins with a difficult distinction: what needs more effort, and what needs an ending?

Leaders are rewarded for fixing, growing, and sustaining things. Ending something can feel like admitting that the prior investment was mistaken. That makes it tempting to label every failing system a turnaround opportunity.

But purpose and mechanism are not the same. A university can remain committed to learning while ending a program. A company can remain committed to customers while retiring the product through which it once served them. A nonprofit can remain committed to a need while admitting that its intervention no longer produces the intended result.

Hospicing a future does not mean declaring the work worthless. It means stopping the attempt to make one mechanism immortal.

Practically, I would ask leaders to make the ending specific:

• Which assumption no longer deserves to organize the strategy?
• Which product, process, role, or investment will stop?
• What evidence made that decision necessary?
• What would cause the organization to reconsider?
• Who has the authority to prevent the ending, and for how long?

Without that specificity, “letting go” becomes another slogan sitting on top of unchanged budgets and power.

Vigil: stay with the loss long enough to learn

Organizations are often impatient with the space between an ending and a replacement.

A product is discontinued on Monday and the new growth narrative is presented on Tuesday. A reorganization is announced with a slide explaining why everyone should be excited. A founder leaves, and the company immediately declares that the culture will not change.

That speed is meant to create confidence. It can also communicate that what people invested in the old future is inconvenient.

A vigil does not require months of therapeutic meetings or ceremonial language that feels false to the organization. It requires enough attention to distinguish what should end from what should be honored.

What did the old strategy make possible? Which capabilities did it create? What did people learn while making it work? Which relationships and values should survive its end? What harm did it cause that should not be romanticized?

This matters because organizations frequently make one of two mistakes. They preserve the old system so completely that the new future cannot emerge, or they denounce the old system so completely that people who built it hear the change as an indictment of their contribution.

Neither produces honest learning.

The vigil is where a company can say, “This served us, and it cannot take us where we need to go.” Both halves of that sentence matter.

Compost: carry forward what can still feed the system

Compost is not preservation. The original form does not survive.

What survives are elements that can become useful in a different system.

A legacy product may contain customer knowledge the new team needs. A discontinued program may have built a community that should not disappear with its budget. A failed strategy may reveal a capability the organization undervalued because it was attached to the wrong outcome. A departing leader may carry relationships and tacit knowledge that cannot be transferred through a folder of documents.

Composting asks a harder question than, “What lessons did we learn?” Organizations answer that question too easily. They produce a list, thank the team, and return to work.

The better question is, “Where will the lesson live?”

Will a decision rule change? Will a metric disappear? Will authority move? Will a capability receive funding? Will a hiring profile change? Will a customer promise be rewritten? If the old strategy taught something but nothing in the operating system changes, the organization did not compost the experience. It buried it.

This cannot become change-management theater

There is an obvious danger in bringing the language of grief into organizational life. Leaders can use it to make a decision feel humane without making the decision itself more honest.

A ritual cannot compensate for a deceptive explanation. Listening sessions do not create dignity if the outcome was predetermined and leaders pretend otherwise. Honoring the past is not meaningful if employees absorb every cost while executives protect their own roles. Asking people to grieve can become insulting when the organization refuses to name who chose the change and who benefits from it.

The work of ending a future does not replace strategy. It makes strategy testable.

A responsible ending should show up in the allocation of money, attention, people, and decision rights. It should release someone from an obsolete expectation. It should create room for a new experiment that the old strategy would have crowded out. It should make clear which part of the organization’s identity is a purpose worth carrying and which part was only one temporary expression of that purpose.

The most strategic question may be: what has ended?

Most strategy processes begin with some version of, “What future do we want?”

It is a necessary question. It may not be the first one.

Before an organization can choose a future, it may need to identify the future it is still trying to recover. The market position that is not coming back. The growth curve that depended on temporary conditions. The career ladder built for work that no longer exists. The cultural story that stopped matching employees’ experience. The strategy that succeeded once and became an identity long after it stopped being an advantage.

Rush’s insight is not that organizations should become preoccupied with endings. It is that beginnings become more credible when endings receive real attention.

The future is not built on an empty site. It is built amid structures, promises, loyalties, and expectations that already occupy the ground. Some deserve to be restored. Some deserve to be repurposed. Some deserve a careful ending.

The strategic discipline is knowing which is which, and having the courage to make the distinction operational.

Sometimes the most responsible beginning looks a little like a funeral.

Listen and read further

• Juli Rush on The Unfolding Thought Podcast
• When the Future Dies
• “When the Future Dies: Hospice, Vigil, Compost,” World Futures Review
• The Social Identity Model of Organizational Change
• Barry Staw’s study of escalating commitment
• Pauline Boss and the theory of ambiguous loss