Getting a team through a change they did not ask for

By the time someone books a change management session, the change has usually already been announced. The structure is decided, the reporting lines are drawn, and the room has spent three weeks talking about it in corridors. What is being asked for is not information. It is a way to move a group that has already made up its mind.

This is the point at which most sessions fail, and they fail in a specific and predictable way: they explain the change. A model of the change curve goes up on a slide, someone describes the four stages, and the room nods politely because agreeing is easier than arguing. Nothing transfers, because nothing happened.

Why explaining resistance does not reduce it

People do not resist change because they lack a framework for it. They resist because of something concrete: they will lose autonomy, or status, or a working relationship, or the one part of the job they liked. Those are rational objections, and being shown a diagram of the emotional stages of change does not address a single one of them.

There is also a credibility problem. The person delivering the session is usually not the person who decided the change, and the room knows it. Anything that sounds like advocacy gets discounted immediately.

What does work is indirect. Put the group inside a situation with its own pressures, let them make decisions, and then draw the line themselves between what they just did and what they do at work. Nobody discounts their own behaviour as biased.

What a session has to produce to be worth running

A moment the room cannot deny. Something happened, everyone saw it, and it is not a matter of opinion. That is the asset an experiential format produces and a presentation cannot.

Language people take away. After a good session a team has a shorthand — a reference to something that happened in the room that they can use in a meeting three months later without explaining it. This is quietly the most durable outcome and almost nobody designs for it.

A named, observable behaviour. Not "we will be more open to change" but something a third party could confirm happened. "Cross-team requests get a yes or no within two working days." Without one of these, there is nothing to measure and nothing will be measured.

Somewhere for the objections to go. The real ones surface during the debrief, not the session. If the sponsor is not prepared to hear them, the session makes things worse — the room has now said the quiet part out loud and watched nothing happen.

The four traps, and why one approach does not clear them

People stay put for different reasons, and the reasons need different levers.

Comfort. The current situation is survivable and the new one is unknown. This person is not afraid; they are unconvinced that the trade is worth making, and they need to see the cost of staying rather than the benefit of moving.

Fear. A specific, often accurate assessment that they will be worse off. Reassurance is the wrong tool. Precision is the right one — exactly what changes, exactly what does not.

Habit. No objection at all, and no change either. The behaviour is automatic and the intention never reaches it. What moves this is a changed cue, not a changed mind.

Over-analysis. Genuine engagement that never resolves. More information makes it worse. What helps is a deadline and a reversible first step.

A session that applies one approach to all four will clear some of the room and lose the rest, and the people it loses will be the ones the change most depends on. This is the design Shift is built on: four characters held by four different things, a fixed budget of time, and not enough of it to try everything on everyone.

When a session is the wrong purchase

Three situations where an experiential session will not help, and saying so early saves everyone a bad day.

The decision is still reversible and people know it. If the room believes lobbying might still change the outcome, they will use the session to lobby. Run it after the decision is genuinely final, or accept that you are running a consultation and call it that.

The objection is about trust, not change. If the real issue is that people do not believe what leadership tells them, a simulation will surface that in the debrief and then leave it on the table. That is a leadership conversation, and it has to happen first or the session becomes evidence for the prosecution.

Nobody senior will be in the room. Sessions where the leadership team sends everyone else produce a group that is now articulate about a change nobody with authority heard them discuss. The cynicism afterwards is worse than the cynicism before.

Who should be in the room

The default booking is "the affected team", and it is usually wrong on both edges.

Include the people who have to make the change work day to day, and include their manager. A team that reaches a shared conclusion without the person who signs off on it has to relitigate the whole thing on Monday.

Mix the teams where the change is cross-functional. Two groups that each believe the other is the obstacle will not discover otherwise in separate rooms.

Keep it under about thirty for a session where a single plenary debrief matters. Above that, the conversation narrows to whoever is most comfortable speaking, which on a change topic is rarely the people you most need to hear.

Measuring it, which decides whether you get a second session

Most change sessions are evaluated with a form at the end asking how useful it was. The score comes back around 4.4, as it always does, and tells the sponsor nothing.

The useful version is set up before the room, not after it, and takes about forty minutes with the sponsor: what will people do differently, where would that leave a trace, and which number the business already tracks does it touch. Then a three-question check to participants' managers ninety days later. That is an hour of someone's time and it produces a finding that survives a budget meeting, because it rests on described occasions rather than ratings.

Measuring behaviour change sets out the whole structure, including how to state a result honestly when a reorganisation happened in the same quarter.

Where HDX fits

Shift is the direct answer: four friends held by comfort, fear, habit and over-analysis, a team with limited time, and a debrief connecting each trap to the people it describes back at work. It runs virtually in six hours or as a classroom day.

Where the change is structural rather than attitudinal — growth outrunning capability, a reorganisation that keeps producing the same bottleneck — Rooted is usually the better fit, because it makes the structure itself physical and lets a team watch it fail under load.

Worth reading first: how to debrief an experiential session so the learning sticks. On a change session the debrief is not the wrap-up, it is the intervention.

---

If a change has already been announced and you need the room to move rather than understand, tell us what it needs to leave with.