Bridges' Transition Model: The 3 Stages of Change Explained

By Brian Tr · Updated Oct 10, 2026

Bridges' Transition Model, created by consultant and author William Bridges, describes the psychological journey people take when something changes at work. It has three stages: Ending (letting go of the old way), the Neutral Zone (the uncomfortable in-between), and the New Beginning (accepting and committing to the new way). Change is the event. Transition is what happens inside people.

This guide explains each stage, compares the model with Kotter, ADKAR, Lewin and the Kubler-Ross curve, and gives you a step-by-step method and a template you can copy.

Key Facts

• Originator: William Bridges, author of Managing Transitions: Making the Most of Change, later updated with Susan Bridges.
• Core distinction: change is the external event (a merger, a new system, a reorganization); transition is the internal process of coming to terms with it.
• The three stages: Ending, Neutral Zone, New Beginning.
• Key twist: the stages start with an ending, not a beginning. You can't start something new until you've let go of something old.
• Not a straight line: people move through the stages at different speeds, and individuals can loop back.
• Best used for: the people side of change, especially when a rollout is "done" on paper but nobody seems to have moved on.
• Related models: Kotter's 8 steps, ADKAR, Lewin's model, and the Kubler-Ross change curve.

What is Bridges' Transition Model?

Most change plans are written in terms of outcomes: a new structure by March, a new system live by June. Bridges noticed that those plans routinely stumbled for a reason that never appeared on the project schedule. People weren't resisting the new thing. They were struggling to let go of the old one.

So he separated two ideas that managers tend to treat as one. According to William Bridges Associates, change is the external event, such as a new strategy, a leadership shift, a merger or a new product, and the organization focuses on the outcome it hopes to produce. Transition is the internal psychological process people go through as they come to terms with the new situation.

That distinction explains a common pattern. A change can happen in a day: the announcement goes out, the org chart is updated, the new tool is switched on. A transition can take months, because it runs on people's feelings, habits and sense of identity, not on a project plan.

The model sits on that idea. If you manage only the change, you get a new system nobody wants to use. If you manage the transition too, you give people a way to move.

Where the model comes from

The model was developed by William Bridges and is described in his book Managing Transitions: Making the Most of Change. The publisher's page for the 25th anniversary edition, written by William and Susan Bridges, presents the book as a guide to the psychological side of workplace change such as restructurings, mergers and layoffs. It argues that people, not companies, must adapt to change, and that transitions succeed when employees have a purpose, a plan and a part to play.

That "purpose, plan, part" idea is useful on its own. We'll come back to it in the how-to section.

The three stages explained

Stage 1: Ending (losing and letting go)

The first stage is the one most change plans skip. Before anyone can embrace the new way, they have to deal with what they're losing.

William Bridges Associates describes this stage as people identifying what they are losing, deciding what stays and what is left behind, and learning to manage those losses.

Losses at work are rarely dramatic, which is why they get ignored. Someone loses a reporting line, a familiar tool, a team they liked, a role they were good at, or the status that came with expertise in the old system. Even when the change is good for the company, and even good for the person, something still ends.

What the Ending stage can look like:

• Anger or irritation about "yet another change"
• Anxiety and worry about job security or competence
• Nostalgia for how things used to work
• Disorientation, or a sudden drop in confidence
• Quiet disengagement

What helps: name the losses out loud. Be specific about what's ending and what isn't. Acknowledge that the old way worked for a reason. And if possible, mark the end with something small, such as a farewell to the old process or a thank-you to the team that built it.

Stage 2: The Neutral Zone

The old way has gone, but the new way isn't fully in place. People are in between, and it's uncomfortable.

William Bridges Associates says psychological realignment happens in this stage and calls it "the seedbed for new beginnings." That's an important reframe. The Neutral Zone isn't dead time to be rushed through. It's where people actually reshape how they see their role, their team and their future.

In practice, this is the stage where:

• Productivity often dips because routines no longer work
• Old and new systems run side by side, creating confusion
• Rumors fill the gaps in information
• Some people feel stuck, while others get creative
• Skepticism peaks: "Is this really going to happen?"

Leaders tend to panic here and push for speed. The pressure to "just get to the new normal" can backfire, because people who haven't finished letting go aren't ready to take hold.

What helps: communicate more, not less, even when the answer is "we don't know yet." Set short-term goals so progress is visible. Provide temporary structures such as interim roles or checkpoints. Create safe ways for people to say what isn't working. If you want people to speak up during a messy period, psychological safety matters more here than at any other stage.

Stage 3: The New Beginning

This is where people accept the change and start to commit to it. William Bridges Associates describes it as people developing new understandings, values and attitudes, taking on new roles, and feeling reoriented.

The New Beginning isn't the day a project goes live. It's when people start to behave as though the new way is simply how work is done. You see it in small things: someone defaults to the new tool without being asked, a team uses the new process in a crisis, people stop saying "the old system."

What helps: reinforce the new behavior early and visibly. Celebrate small wins that connect to the change's purpose. Make sure the new way is easier, or at least clearly better, in daily work. Check that incentives, metrics and responsibilities match the new direction. And don't declare victory too soon. If some people are still in the Neutral Zone, they'll slide back.

The stages overlap

Although they're numbered, the stages aren't a clean sequence. In a large organization, one team may be starting a New Beginning while another is still in the Ending. Within one person, a setback can pull them back into the Neutral Zone. Treat the model as a map of the territory, not a timetable.

Bridges vs Kotter, ADKAR, Lewin and Kubler-Ross

The frameworks answer different questions, which is why they work well together.

A simple way to combine them: use Kotter to plan and drive the change, ADKAR to check each person's readiness, and Bridges to manage the human experience of the in-between. The same logic applies if you're redesigning the organization itself with something like the McKinsey 7S framework. The structure can change on paper in a week, while the shared values and skills take much longer to follow.

How to apply the Bridges Transition Model

1. Separate the change from the transition. Write down the change in one sentence ("From March, all regions move to one CRM"). Then write down what the transition will involve for people ("Sales reps lose the spreadsheet they built and trust").
2. Identify who is losing what. List every group affected. For each, name the specific losses: tasks, tools, relationships, status, autonomy, certainty. Include losses that seem small.
3. Plan the Ending. Decide what ends, what continues and what is left behind. Tell people directly. Hold a conversation, not just an announcement, and give people room to react.
4. Prepare for the Neutral Zone. Set up temporary routines, interim goals and clear points of contact. Decide how often you'll update people, and commit to it even if there's no news.
5. Give people a purpose, a plan and a part to play. Tell them why the change is happening, what the outcome looks like, how you'll get there, and what role they play. This echoes the book's point that transitions go better when people have a purpose, a plan and a part to play.
6. Spot the signals. Watch for missed deadlines, absenteeism, rumor loops, silent meetings and workarounds. These tell you which stage a group is in.
7. Support the New Beginning. Recognize early adopters, remove obstacles to the new way, and update performance goals so they reward the new behavior.
8. Review and adjust. Check in with each group, not only the project team. Move people along at their own speed, and repeat steps 2 to 7 for groups who need more time.

Bridges Transition Model template

Copy this table into a doc or spreadsheet. Use one row per affected group.

Here's a filled-in example row for a hypothetical company moving to a new reporting structure:

Examples by business function

These are illustrative scenarios, not real case studies.

Do's and don'ts

Do:

• Treat the Ending as real work. Name the losses before you sell the benefits.
• Plan for a bumpy middle. Tell people in advance that dips are normal.
• Communicate more often than feels necessary, especially during the Neutral Zone.
• Give people a role in shaping the new way, not only a role in following it.
• Use different tactics for different groups. Not everyone will be at the same stage on the same day.
• Look at what the change feels like to the people furthest from the decision.

Don't:

• Don't confuse the project timeline with the transition timeline.
• Don't dismiss resistance as stubbornness. It's often grief for something real.
• Don't rush the Neutral Zone to hit a deadline.
• Don't announce a "new beginning" while key groups are still letting go.
• Don't ignore the leaders. Managers go through their own transition too, and they need support before they can support others.

Common mistakes

Starting with the vision, not the loss. Leaders usually want to open with an exciting future. But people who haven't been allowed to say goodbye to the past tend to hear the pitch as dismissive. Acknowledge the Ending first, then paint the picture.

Treating the Neutral Zone as a failure. The messy middle is the point where old habits break and new ones form. Productivity dips and confusion are normal, and they don't mean the change is failing. If you panic, people will too.

Using one pace for everyone. Some people accept change quickly and others need much longer. A model that assumes one timeline will leave half the team behind.

Measuring only the project. A system that goes live on time but isn't used hasn't made a transition. Track adoption, behavior and sentiment, not just delivery dates.

Forgetting that leaders transition too. Senior people designing the change may have been living with it for months. They're often at the New Beginning while the rest of the organization is only now hearing about the Ending. That gap is where trust gets lost. The same idea shows up in transformational leadership, where leaders are expected to bring people with them, not just point them at a destination.