Bridges' transition model and why change fails

I’ve been thinking about this for a while. Why does change fail so often?

Not the structural stuff. Not the technology rollout or the new org chart. That part’s straightforward. You announce it, you roll it out, you move on. The part that fails is what happens inside people’s heads after you make that announcement.

That’s what William Bridges figured out, and honestly, it’s one of the most useful mental models I’ve come across for anyone managing a team through any kind of shift.

When you’re guiding people through these transition stages, having a structured way to track progress and communicate changes makes the whole process smoother. That’s where process improvement tools can help.

Difference between change and transition

Here’s the distinction that most people miss.

Change is external. It’s the new software system, the restructured department, the updated policy. It happens on a specific date. Done.

Transition is internal. It’s the slow, messy, emotional process that happens inside every person affected by that change. It doesn’t happen on a date. It happens over weeks, sometimes months.

Bridges identified three stages of transition:

• Ending, losing, and letting go
• The neutral zone
• The new beginning

Everyone moves through these at their own pace. Some people breeze through all three in a week. Others get stuck in stage one for months. One mid-sized nonprofit managing volunteer onboarding found that when members moved through their 60-day transition quickly, they were 50% more likely to become contributing members. That variance in adaptation speed is probably the most underestimated factor in any change initiative.

And here’s what gets me - most leaders don’t even acknowledge this process exists. They announce the change and expect people to just… adjust. That’s not how humans work.

Stage 1 - ending, losing, and letting go

This is the part nobody wants to talk about. When people first learn that something familiar is going away, they have an emotional reaction. Not a “professional concern.” An emotional reaction.

They feel afraid. They enter denial. They get angry. They feel disoriented, frustrated, sad. They experience a genuine sense of loss. I think we vastly underestimate how deeply people attach their identity to their work routines. When you change someone’s process, you’re not just changing their tasks - you’re disrupting something they’ve built competence around. That feels personal. I’ve seen senior managers who’ve been running the same process for fifteen years react to a software change like you’d told them their job didn’t matter. The fix here isn’t complicated, but it requires patience.

Be honest about why the change is happening. Don’t sugarcoat it with corporate speak. Tell people what’s changing, why it’s changing, and what their future role looks like. Show them that their skills still matter. Bridges believed most resistance comes from being confronted with things people don’t understand. Remove the mystery and you remove most of the fear.

At Tallyfy, we’ve noticed that when transitions involve documented workflows people can actually see, the fear drops considerably. There’s something grounding about being able to look at a screen and see exactly what’s expected of you next, rather than guessing.

Stage 2 - the neutral zone

This is the hardest stage. For everyone.

People have accepted that change is happening, but they’re not comfortable with the new way yet. They’re stuck in between - can’t go back, haven’t arrived yet. The learning curve feels steep, morale is low, and productivity drops.

You’ll see resentment. Skepticism. Anxiety about their new role. People will openly or quietly compare the old way with the new way, and the old way will win every time. Nostalgia is powerful.

As a leader, you’ll get frustrated too. You planned everything. You communicated the vision. You did all the right things. And people are still struggling.

Persistence matters here.

Keep reminding people where this is heading. Celebrate small wins - and I mean genuinely small ones. Someone completed the new workflow correctly for the first time? That’s worth acknowledging. A team reduced their error rate by even 5%? Say it out loud.

After watching hundreds of teams try this with workflow automation, we’ve seen that teams who have visible, trackable processes during transitions feel more grounded. They can see exactly where they are. There’s no ambiguity about what’s done and what’s next. Tallyfy was built for exactly this kind of visibility - not because tracking is fun, but because uncertainty during change is what’ll kill momentum.

Watch out for bottlenecks creating unmanageable workloads. One government contractor found their HR team could eventually handle 10-20 simultaneous new hire transitions - but only after they cut pre-onboarding from two weeks down to three days by automating the administrative burden. Expecting too much too soon is the most common mistake during this phase. Teams need time.

Trackable workflows for managing employee transitions

Example Procedure

Employee Onboarding

1HR - Set up payroll and send welcome email

2IT - Order equipment and set up workstation

3Office Manager - Prepare physical workspace

4IT - Create accounts and system access

5HR - Welcome meeting and company orientation

+3 more steps

View template

Example Procedure

New Hire Orientation

1Before arrival HR: Send new employee email and company handbook

2Before arrival Manager: Send new employee email and create work-plan for month 1-3

3Before arrival IT: Set-up desk and computer

4First day HR: Meet new employee and introduce manager, set up tax forms

5First day Manager: Introduce employee to department, begin training

+10 more steps

View template

Example Procedure

Employee Performance Review & Evaluation Workflow

1Schedule performance review meeting

2Define employee goals and development plan

3Create training and development plan

4Executive approval for senior manager evaluations

5Collect performance data and 360 feedback

+4 more steps

View template

Stage 3 - the new beginning

Have you ever gone through something difficult and then, almost without noticing, things started clicking into place?

That’s stage 3.

People begin to see results. The new way of working starts making sense. They understand why you pushed for the change, and they can see their efforts paying off.

The emotions flip:

• They feel energized
• They want to learn more
• They feel committed

This is the stage you want to sustain. Set clear objectives. Show people how hitting those objectives connects to the bigger picture. Share success stories.

But don’t get complacent. Some people can still slip back into stage 2. Others might not have left it yet. Stay watchful. Keep the support available.

Why AI makes this harder, not easier

Here’s something I keep coming back to.

If your change initiative hasn’t properly addressed the transition - if you haven’t guided people through the ending, through the neutral zone, into the new beginning - then automating that initiative with AI just means you’ll create confusion and resistance at machine speed.

I’ve seen organizations rush to automate change management processes without first understanding where their people are in the transition. The technology works fine. The people don’t.

This is why, at Tallyfy, we’re obsessed with making processes visible and trackable before anyone tries to automate them. You need to know where people are struggling before you can help them. Throwing an AI agent at a broken transition process is like giving someone a faster car when they don’t know the route.

Teams tell us the same thing in different words about digital transformation, the pattern is remarkably consistent - the organizations that struggle most are the ones that treated change as a technology problem rather than a people problem. The Bridges model gives you a structure for addressing the people side first.

Making Bridges’ model work in practice

So how do you actually use this?

Start by figuring out which stage each team or individual is in. You can’t apply the same approach everywhere. Stage 1 people need empathy. Stage 2 people need encouragement and visible progress. Stage 3 people need goals and recognition.

Map your change initiative against the three stages. For each stage, define what success looks like, what warning signs to watch for, and what kind of support to provide.

My honest recommendation - document these transitions as workflows. Not because I’m biased toward Tallyfy (though I am), but because written-down processes force you to think through each stage carefully. It’s the only way I’ve seen it work reliably. When someone can look at a dashboard and see “here’s where I am, here’s what’s next,” it takes away the ambiguity that makes transitions so uncomfortable.

Bridges’ transition model isn’t a complete change management approach on its own. It handles the people side - probably the most important part - but you still need to address the structural and strategic elements. Look at Kotter’s 8-step model or Lewin’s change management model for the bigger picture.

The point isn’t to pick one model and ignore the rest. It’s to recognize that behind every org chart change, every software rollout, every new process - there’s always people going through a transition. And if you ignore that transition, the change will fail. Maybe not immediately. But eventually.

That’s the insight Bridges gave us. Change is the event. Transition is the journey. And the journey is what determines whether the change sticks.