The five fundamental human needs during change

On the night of February 13th, 2013, in Phuket, a Korean Air gate agent taught me most of what I know about resistance to change.

My wife and I were exhausted. We'd spent a week vacationing with our two babies, sharing a bed with them, managing nap schedules, doing all the things that make travel with babies both wonderful and completely horrific. Ahead of us was a red-eye flight home. We had one saving grace: we'd reserved a bassinet so our baby could sleep.

Then we heard the words every parent dreads. "I'm so sorry, but we don't have a bassinet available. It was given to another passenger."

I explained our situation. I told her we'd chosen this flight because of that bassinet, that our baby desperately needed to sleep. I wasn't angry. I was tired and honestly a little desperate.

She didn't give me the standard "there's nothing I can do." She didn't offer a voucher. She stopped, listened, and asked herself a different question: what is this family's real problem?

The bassinet was never the problem. It was the tool we needed to solve the actual problem, which was a baby who needed to sleep. She understood the distinction, and she moved us to seats that reclined all the way back.

She didn't solve the problem I presented. She solved the problem I actually had.

Here's why that story belongs in an article about change. When a leader tells me their team is resisting, they are almost always describing the problem the team presented. Resistance is the bassinet. Underneath it sits a need the change has put at risk — and the person proposing the change usually cannot see it, for the simple reason that it isn't threatening them.

That asymmetry is the whole problem in miniature. The person announcing a restructure has had six weeks to absorb it, helped shape it, and knows exactly where they land in it, while the person hearing about it has had ninety seconds and knows none of those things. Treating their reaction as an information deficit — as something that a bit more explaining will fix — is the single most common mistake I see in change communication, and it is why the second town hall so rarely goes better than the first.

The five needs

1. Security

Will I still have a job, an income, a predictable shape to my week? This is the loudest of the five and the one leaders most often try to reassure away using language they cannot actually guarantee. If you are not in a position to promise safety, then don't. Promise honesty and a timeline for information instead, because people can plan around uncertainty far more effectively than they can plan around a reassurance that later turns out to be false.

The specific failure worth avoiding here is the unbounded promise. "No one is losing their job" buys you an enormous amount of goodwill if it holds, and costs you every future statement you make if it doesn't. Compare that with "no decisions have been made about roles, and I will tell you in the first week of March whether that has changed." Less comforting on the day. Worth far more by March.

2. Belonging

Am I still part of this? Reorganizations dissolve teams that people had genuine attachment to, and mergers ask two cultures to become one, which one of them almost always experiences as being absorbed rather than joined. The signal worth watching for is people referring to the organization as "they" when they used to say "we."

Belonging is also the need most often damaged by accident, through sequencing rather than through substance. People find out who was in the room before they were, and they draw conclusions about their own standing from it. So when a group hears significant news secondhand, the content of that news is frequently less damaging than the discovery that they were not important enough to hear it first.

The sequence is the message.

3. Significance

Do I still matter here? This is the most under-acknowledged of the five, largely because raising it out loud sounds like ego, which it isn't. When a change renders someone's hard-won competence obsolete — a new system, a new process, a new structure — what you have actually done is ask an expert to become a novice in public. That is genuinely costly, and it needs to be named rather than dismissed.

It is also the need most likely to be misread as something else entirely. A senior person picking holes in your implementation plan may well be raising real risks, and may simultaneously be demonstrating that they still know things worth knowing, and both of those can be true at once. Treating the objection purely as obstruction means missing the request underneath it, which is usually not that the change should stop but that their expertise should be visibly wanted in it.

4. Autonomy

Do I have any say in this? The difference between change that is done with people and change that is done to them comes down almost entirely to where the decision points sat. Nobody expects you to democratize every decision, but you can be explicit about which decisions are genuinely open, which are constrained, and which have already been made — and people respond remarkably well to that honesty even when the answer is that it's already been decided.

What corrodes trust is the false consultation, by which I mean inviting input on a decision that is already settled. People work out the difference quickly, and the cost is never confined to that one decision. Every subsequent invitation to contribute now gets read as theater, including the genuine ones.

5. Justice

Is this fair? People do not assess a change in isolation. They assess it against what happened to everyone else — who absorbed the cuts, who was consulted first, who kept their team intact, and who was asked to do more for the same. A change that is entirely defensible in aggregate can still read as unjust to whichever group carried more of its cost, and that reading does not resolve on its own. Where the inequity is real, name it and say what you intend to do about it. Where it only appears that way, show the reasoning — people will accept a great deal once they can see how a decision was actually made.

Justice also has the longest memory of the five. Security fears resolve themselves once the outcome arrives. A perceived injustice does not expire, and it tends to get retold. It is the need most sensitive to whatever leaders exempt themselves from, so an efficiency program that visibly does not apply to the people who designed it will be read as a statement about who the rules are for, whatever the accompanying message happens to say.

How to use this

So let me try to get specific. Before your next change conversation, work through two passes.

First, for each affected group, identify which one or two needs the change actually threatens. It is rarely all five, and it is rarely the same ones for different groups, since the engineering team and the customer support team are usually worried about quite different things. A single message addressed to the average of their concerns will land with neither of them.

Second, decide what you can honestly offer against that specific need. Not reassurance in general, but a concrete response to the particular threat. If significance is the issue, that might mean visible acknowledgment of someone's expertise along with real time to become competent again. If autonomy is the issue, it might mean genuine input on the parts that remain open.

Most failed change communication is a well-crafted answer to a question nobody asked.

Reading the need from the objection

In practice people rarely name the need directly. What they do instead is raise a practical objection with the need sitting underneath it, so here is a rough translation guide:

• "What's the timeline?" — asked repeatedly, this is usually security, because the question is really about the shape of their next few months rather than about project management.
• "Who decided this?" — usually autonomy or justice depending on the tone, and it is a question about the legitimacy of the process, so answering it with the rationale for the decision rather than the manner of it will not land.
• "How will this work in practice?" — often significance, particularly coming from experienced people, and underneath it sits the question of whether what they know still counts.
• "Why now?" — frequently belonging, and it tends to surface when people suspect the change reflects some judgment about them that nobody has been willing to say out loud.
• Silence from someone who is normally vocal — the most reliable signal on this list, and the one most often written down as agreement.

Treat these as starting hypotheses rather than diagnoses. The whole point of the translation is to prompt you to ask a second question instead of answering the first one.

The first 48 hours

The window immediately following an announcement does a disproportionate amount of damage or good, because it is when people are deciding what kind of change this is going to be. Three things are worth protecting in it.

Be present and unhurried. A leader who announces a restructure and then disappears into back-to-back meetings has communicated something considerably louder than the announcement itself. Visible availability across those first two days costs you a morning and buys months of credibility, and its absence gets read as avoidance whether or not that is what it is.

Answer the unaskable question first. In every change there is one thing that everybody is thinking and nobody will say in a group setting, and naming it yourself — including saying plainly that you cannot answer it yet — removes the single largest source of corridor speculation. If you don't name it, it does not go away. It simply circulates in a version you have no influence over.

Let the first objection go well. Whoever raises the first serious challenge is doing so on behalf of a room that is watching closely to see what happens to them, which means your response sets the price of honesty for the remainder of the change. This is the cheapest trust you will ever buy and by some distance the most expensive to lose.

Why this is a leadership skill, not a comms exercise

This work cannot be delegated to a communications function, because it requires being close enough to people to know what they are actually afraid of, and that closeness gets built long before the change is ever announced. It is why the leaders who navigate transformation well are almost always the ones who were already paying attention.

It also cannot be done at scale by any one person, which is the practical constraint that most transformation plans miss entirely. The conversations that matter are happening between a manager and the five or six people who trust them, which means the real capability question is not whether your executive team understands the five needs. It is whether the forty managers actually carrying the change have been prepared to have those conversations at all — and they are typically the least resourced people in the entire program.

The pay-off for getting this right goes beyond avoiding damage. Change handled this way leaves trust higher than it found it, because people have now seen how you behave when things are genuinely hard, and that is worth far more than the change itself.

If you're staring down a transformation, this is the ground our change leadership programs cover, and our leadership workshops run this material with intact teams rather than individuals — because the conversations it produces are ones a team needs to have together.

Before any of that, though, I'd sit with two questions.

Which of the five needs is your change actually threatening, for each group — and how would you know if you were wrong?

And the harder one. When your team raised their last objection, did you answer the problem they presented, or the problem they actually had?