Latest / The Caribbean Workplace Wellness Channel / You Can Mandate Change But You Cannot Mandate Transition

Transcript

You Can Mandate Change But You Cannot Mandate Transition · The Caribbean Workplace Wellness Channel

0:12
Sarah: Have you ever found yourself sitting in a, you know, one of those brightly lit conference rooms where maybe you're staring blankly into a grid of faces on a long video call?
0:21
Adrian: Oh, I know exactly where this is going.
0:23
Sarah: Right.
0:23
Sarah: You're enduring a mandatory training session for some shiny, incredibly expensive new piece of software, and you're nodding along enthusiastically, you're taking notes, you're saying all the right things to the trainer.
0:34
Sarah: Yep.
0:35
Sarah: But then the very minute that meeting ends, you immediately go right back to using your secret, off-system, completely unauthorized legacy spreadsheet.
0:45
Adrian: The Phantom Spreadsheet.
0:46
Adrian: It is such a universal experience.
0:48
Adrian: I mean, I think everyone has that one specific workaround they just refuse to let go of, no matter how many memos management sends out.
0:55
Sarah: Oh, absolutely.
0:56
Sarah: I've definitely been guilty of it.
0:58
Sarah: And uh that is exactly our mission for today's deep dive.
1:01
Sarah: We are unpacking the hidden psychological barriers to workplace transformation.
1:06
Adrian: It's such a crucial topic.
1:07
Sarah: It really is.
1:08
Sarah: Today we're pulling from a truly fascinating paper published by the Caribbean Workplace Wellness Channel and the Institute for Mental Health and Wellbeing.
1:17
Sarah: It's titled Managing the Transition Gap.
1:20
Sarah: Right.
1:20
Sarah: And what it reveals about how our brains actually handle workplace changes and why we cling to those old spreadsheets is going to fundamentally change how you view your office dynamics.
1:32
Adrian: It really is a paradigm shift because if you think about it from management's perspective, they see that behavior, the reverting to old ways, the off-system emails, and they just label it as stubbornness.
1:45
Sarah: Right, or like a disinterest.
1:46
Adrian: Exactly.
1:47
Adrian: Maybe even insubordination.
1:48
Adrian: They look at the team and think, you know, why won't these people just use the new highly efficient tool we just spent millions of dollars buying for them?
1:56
Sarah: Yeah, they take it personally.
1:57
Adrian: But organizational psychology reveals a completely different reality.
2:00
Adrian: The resistance isn't about the new system at all.
2:03
Adrian: It is actually about unacknowledged grief.
2:05
Sarah: Wait, grief.
2:07
Adrian: Yeah, a profound, very real sense of loss associated with the old way of working.
2:12
Sarah: Okay, let's unpack that word because applying grief to a software rollout sounds, well, intense.
2:18
Adrian: It does, but it fits.
2:19
Sarah: So you're saying when management rolls out a new CRM platform, they think they're handing us the keys to a shiny, top-of-the-line new car.
2:27
Sarah: Right.
2:27
Sarah: But psychologically, to the team actually doing the work, it feels like someone just snuck into our driveway in the middle of the night and towed away our reliable, perfectly broken-in old vehicle without even letting us say goodbye.
2:41
Adrian: That is the perfect way to visualize it.
2:43
Adrian: I mean, think about your relationship with that old car.
2:46
Adrian: You loved it.
2:47
Adrian: You knew exactly how far you could push the gas pedal before the engine sputtered.
2:51
Sarah: Yes.
2:51
Sarah: You knew the exact weird angle you had to hit the radio dial to make it work.
2:55
Adrian: Exactly.
2:56
Adrian: It was pure muscle memory.
2:57
Sarah: Yeah.
2:58
Adrian: So when management brings in the shiny new car, they expect you to be immediately thrilled about uh the Bluetooth integration and the heated seats.
3:06
Adrian: Right.
3:06
Adrian: They completely miss the fact that you are standing in an empty driveway, staring at the oil stains on the concrete, mourning the loss of your familiar routine and your deep competence.
3:17
Sarah: Because I didn't ask for the heated seats, I just wanted my old car to start in the morning.
3:21
Adrian: Exactly.
3:21
Sarah: And this brings us to why management gets this so consistently wrong.
3:26
Sarah: The research points out that leaders fundamentally fail to understand a very critical distinction in how human beings process reality.
3:34
Adrian: Yes.
3:35
Adrian: The foundation of this whole framework comes from a model developed by organizational consultant William Bridges.
3:42
Adrian: And he makes a crucial distinction between two concepts that corporate culture normally uses interchangeably.
3:51
Sarah: Change and transition.
3:53
Sarah: So let's break those down because they are definitely not the same thing.
3:55
Sarah: And understanding the difference seems to be the key to this whole puzzle.
3:59
Adrian: They are completely different phenomena.
4:01
Adrian: So change is just the external event.
4:03
Adrian: It is purely situational, it's structural.
4:06
Sarah: Like launching a new platform or shutting down a regional office.
4:09
Adrian: Exactly.
4:10
Adrian: Merging two departments, restructuring the reporting lines, those are changes.
4:14
Adrian: A change is the thing that happens on a specific date on the calendar.
4:17
Adrian: It's the go live date.
4:19
Sarah: Right.
4:19
Sarah: Okay.
4:19
Adrian: Transition, however, is the internal psychological three-stage process that people must go through to mentally come to terms with that new situation.
4:29
Sarah: So change is what happens to the organization, but transition is what happens inside the minds of the human beings working there.
4:37
Adrian: You nailed it.
4:38
Adrian: You can mandate a change overnight.
4:41
Adrian: You cannot mandate a transition.
4:43
Adrian: And this is the core failure that derails most corporate transformation plans.
4:48
Sarah: Because management tries to force employees to jump straight to the finish line.
4:53
Adrian: Exactly.
4:53
Adrian: They expect immediate enthusiasm and instant competence, completely skipping the messy, uncomfortable psychological middle phase where the actual adaptation happens.
5:03
Sarah: Wait, so management is essentially treating human beings like light switches.
5:07
Adrian: Yes.
5:07
Sarah: They think they can just flip off the old system on Friday at 5 p.m.
5:10
Sarah: and flip on the new one on Monday at 8 a.m.
5:12
Sarah: and we'll all just magically illuminate the room with productivity.
5:15
Adrian: That's a delusion, yeah.
5:16
Sarah: When in reality, our brains operate way more like slow booting computers that need time to process the entirely new operating system in the background.
5:23
Adrian: It's all about cognitive load.
5:25
Adrian: Using the old system was like driving home on autopilot.
5:29
Adrian: It took zero active mental energy.
5:31
Sarah: Right, because of that muscle memory.
5:33
Adrian: Right.
5:33
Adrian: A new system forces the prefrontal cortex into overdrive.
5:36
Sarah: Yeah.
5:37
Adrian: Everything takes intense conscious thought.
5:40
Adrian: When leadership expects immediate enthusiasm for enhanced efficiency, they are operating under that light switch delusion.
5:47
Sarah: Okay, so if we accept that humans are slow booting computers, we have to look at where that transition actually begins.
5:54
Sarah: And counterintuitively, every transition process begins with an ending.
5:58
Adrian: It feels backwards, right?
5:59
Adrian: Yeah.
5:59
Adrian: Yeah.
6:00
Sarah: Usually a rollout is pitched as a big beginning.
6:02
Sarah: But the psychology says stage one is all about endings, losing, and letting go.
6:06
Adrian: Exactly.
6:06
Adrian: You have to end before you can begin.
6:08
Adrian: Think about the psychological reality of the employee in this first stage.
6:12
Adrian: There's a genuine sense of loss.
6:14
Adrian: Yeah.
6:14
Adrian: There's a very real visceral fear of incompetence.
6:18
Adrian: People have a deep, ego-driven attachment to their old mastery.
6:22
Sarah: Right.
6:22
Sarah: Think about an employee who has spent five years mastering a wildly complex, buggy legacy database.
6:30
Sarah: They are the go-to person.
6:32
Sarah: People bring them coffee just to get a report run.
6:35
Adrian: They have status.
6:36
Sarah: They are an absolute wizard at it.
6:39
Sarah: It's part of their workplace identity.
6:41
Adrian: And overnight, a new system is introduced.
6:44
Adrian: Suddenly, their hard-earned mastery is totally gone.
6:47
Adrian: They are a beginner again, fumbling around just like the new intern.
6:51
Sarah: That is Russ.
6:52
Adrian: So when leaders stand up in a company-wide town hall and dismiss the old tools as inefficient or archaic, what long-serving staff actually hear is that their past expertise is being directly devalued.
7:03
Sarah: Ouch.
7:04
Sarah: That really stings.
7:05
Sarah: You're basically standing on a stage telling them, hey, that thing you were the absolute best at, it's garbage.
7:08
Sarah: Exactly.
7:09
Sarah: No wonder there is massive passive resistance.
7:12
Sarah: You're attacking their professional self-worth.
7:14
Sarah: So how does a leader actually counteract that?
7:16
Sarah: Because I mean you still have to replace the software.
7:18
Adrian: The required managerial action here is vital.
7:21
Adrian: You have to honor legacy contributions before you can demand focus on the future.
7:25
Adrian: You must explicitly acknowledge what is ending.
7:28
Sarah: Okay, but how?
7:29
Sarah: The research recommends holding a brief ceremony or like a formal debrief, explicitly thanking the team for the years of value delivered through the old system.
7:39
Sarah: Right.
7:39
Sarah: Now I have to push back on this a little bit.
7:42
Sarah: A ceremony for an outdated spreadsheet?
7:44
Sarah: I can hear middle managers everywhere rolling their eyes so hard they might get stuck.
7:49
Sarah: Well, for sure.
7:50
Sarah: I mean, how does a leader actually execute this without it feeling incredibly cheesy or patronizing?
7:57
Sarah: Do we bring in a sheet cake with a floppy disk drawn and frosting?
8:01
Adrian: I get the skepticism, and no, you definitely skip the floppy disk cake.
8:05
Sarah: Okay, good.
8:06
Adrian: Let's look at the underlying mechanism here.
8:08
Adrian: It is not about worshipping the actual software.
8:11
Adrian: Nobody loved the clunky interface.
8:13
Adrian: It is about validating the human effort and the immense mastery that went into using it.
8:18
Adrian: Okay.
8:18
Adrian: It's an exercise in empathy.
8:19
Adrian: If you want a real-world example of honoring a legacy system without being cheesy, think about a highly structured lessons learned debrief.
8:27
Sarah: Paint that picture for me.
8:28
Sarah: What does that sound like in a meeting?
8:30
Adrian: Well, a good manager might open the meeting by saying, before we officially turn off this old CRM on Friday, I want to formally acknowledge something.
8:38
Sarah: Setting the tone.
8:39
Adrian: Exactly.
8:40
Adrian: This clunky tool helped us hit our revenue targets for six straight years.
8:44
Adrian: It required massive manual data entry.
8:47
Adrian: It was frustrating.
8:48
Adrian: And I want to sincerely thank you for the late nights you spent holding it together with duct tape.
8:52
Sarah: Oh, wow.
8:53
Adrian: You kept us afloat.
8:55
Adrian: So today, let's capture the two or three workflows from this old system that you actually loved so we can make sure we replicate that success in the new system.
9:03
Sarah: Okay, that entirely shifts the tone.
9:05
Sarah: It completely reframes the narrative.
9:07
Adrian: It does.
9:08
Sarah: It goes from your old work was inefficient to your old work was heroic, you did the best with what you had, but now we have a better tool to support you.
9:15
Adrian: Exactly.
9:15
Adrian: By protecting the employees' pride in their past work, you are systematically lowering their defensive shields for the future.
9:23
Adrian: You're separating their identity from the software.
9:26
Sarah: That makes so much sense.
9:27
Sarah: And once you've done that, once the team has officially let go of the old system psychologically, they are ready to move forward.
9:35
Adrian: Right.
9:35
Adrian: But letting go doesn't mean they magically achieve mastery of the new system the next day.
9:40
Sarah: No, they don't.
9:41
Sarah: And this is exactly where corporate transformations usually fall apart.
9:44
Sarah: Once people let go of the old trapeze bar, they are suspended in midair before they catch the new one.
9:49
Adrian: They fall right into the gap.
9:50
Sarah: Which brings us to the absolute core focus of our discussion today.
9:54
Sarah: Stage two, the neutral zone.
9:57
Adrian: The neutral zone.
9:58
Adrian: The research also calls this the bridge.
10:01
Adrian: And it describes this phase as a period of intense anxiety, ambiguity, confusion, and experimentation.
10:08
Sarah: It is essentially the void.
10:10
Adrian: It is the single most vulnerable time for any organization.
10:14
Adrian: People are no longer doing things the old way, but they aren't fully competent at the new way yet.
10:19
Adrian: Everything feels broken.
10:20
Sarah: Everything takes twice as long.
10:22
Adrian: Exactly.
10:22
Sarah: And this leads to my absolute favorite insight from this deep dive.
10:25
Sarah: Honestly, the most validating part for any listener who has ever struggled to keep their head above water during a massive rollout.
10:32
Adrian: Oh, the productivity dip.
10:33
Sarah: Yes.
10:34
Sarah: The research states, as an unavoidable matter of fact, that team productivity will temporarily decrease.
10:41
Sarah: It is inevitable while staff master new software or navigate new reporting lines.
10:46
Adrian: It is an absolute biological certainty.
10:48
Adrian: The cognitive load we talked about earlier demands it.
10:51
Adrian: Yet, how often do we see management completely panic when the output numbers dip in the first month?
10:58
Sarah: Literally all the time.
10:59
Sarah: The executive team stares at the dashboard, sees the red arrows, and immediately start sending angry emails about driving adoption.
11:06
Adrian: And that's exactly what not to do.
11:07
Sarah: So what is the actual tactic here?
11:09
Sarah: How do you manage the void?
11:11
Adrian: Managers have to actively plan for the productivity dip.
11:14
Adrian: They need to provide very clear short-term goals.
11:17
Adrian: They need to manufacture psychological safety so people aren't terrified of making learning errors.
11:22
Sarah: And protect their focus.
11:23
Adrian: Yes, ruthlessly protect the team's focus from other distractions.
11:26
Sarah: Okay, I want to really dig into this because this sounds great in a psychology paper, but it is incredibly tricky in the real world.
11:33
Sarah: It is It's one thing to say expect a productivity dip, but how does a business actually survive it?
11:39
Sarah: It reminds me of remodeling your kitchen.
11:42
Adrian: Oh, that's a good analogy.
11:43
Sarah: Right.
11:43
Sarah: You tear out the old cabinets, you know it's going to be gorgeous eventually.
11:47
Sarah: But right now, you're eating cold microwave meals on the living room floor, there is drywall dust in your coffee, and everyone is cranky.
11:56
Adrian: Very cranky.
11:57
Sarah: Are corporate managers really willing to bake lower productivity into their aggressive quarterly timelines?
12:03
Sarah: How do you even sell a deliberate slowdown to higher-ups who just spent millions on an efficiency tool?
12:10
Adrian: It's the ultimate corporate friction point.
12:12
Adrian: But the research is unflinching on this.
12:14
Adrian: You cannot force human minds to adopt new habits through mandate alone.
12:18
Adrian: You just can't.
12:19
Adrian: Executive mandates do not rewire neural pathways.
12:23
Adrian: If a manager tries to enforce the old high-level productivity metrics during the neutral zone, the team will simply panic.
12:29
Sarah: They feel threatened.
12:30
Adrian: And what do humans do when they feel threatened?
12:32
Adrian: They retreat to safety.
12:33
Adrian: They will secretly revert to their legacy spreadsheets, work-off system, and manually duplicate data just to hit those unrealistic numbers.
12:40
Sarah: Because they're terrified for their jobs.
12:42
Sarah: They don't have time to learn the new system if they are being punished for not hitting their old quota.
12:47
Adrian: Exactly.
12:48
Adrian: And then what you have is a hidden dip.
12:51
Adrian: On paper, productivity looks fine because people are faking it, but the new system isn't actually being used.
12:57
Sarah: And the data becomes wildly siloed and inaccurate.
13:01
Adrian: And the millions of dollars spent on the software are entirely wasted.
13:04
Adrian: Baking the productivity dip into the timeline up front is the only way to achieve sustainable long-term adoption.
13:12
Sarah: So what does that practically look like for a team leader?
13:14
Adrian: Aaron Powell It means setting hyperspecific short-term goals that have nothing to do with output and everything to do with learning.
13:21
Sarah: Like what?
13:21
Adrian: You might say, okay, team, this week, our only goal, our only metric for success is that everyone successfully logs into the new system, navigates to the dashboard, and creates one single test record without locking themselves out.
13:33
Sarah: That's it.
13:34
Adrian: That's it.
13:35
Adrian: You celebrate that small win.
13:36
Adrian: Furthermore, psychological safety means when someone inevitably clicks the wrong button and accidentally deletes a client record in week one, they aren't publicly shamed.
13:45
Sarah: It's a learning experiment.
13:46
Adrian: Treated openly is a highly valuable one.
13:49
Adrian: Hey, Sarah found a bug in how we process forms.
13:52
Adrian: Let's all look at what happened so we can avoid it.
13:54
Sarah: You're guiding them through the kitchen remodel.
13:56
Sarah: You're acknowledging that the microwave meals are temporary, and you're explicitly telling them that you do not expect them to host a five-course dinner party amidst the drywall dust.
14:06
Adrian: I love that.
14:06
Adrian: Yes.
14:07
Adrian: You give them permission to be slow, you give them the space to experiment, make mistakes, and slowly build their new neural pathways until competence returns.
14:16
Sarah: Okay, so assuming a manager has the courage to do this and successfully navigates their team through the messy, anxious, dusty neutral zone, how do they finally anchor them on the other side?
14:27
Adrian: Uh stage three.
14:28
Sarah: Yes.
14:28
Sarah: How do we reach stage three, the new beginning?
14:31
Adrian: The psychological shift when a team finally enters stage three is palpable.
14:35
Adrian: The fog lifts, the cognitive low drops back to normal levels.
14:39
Sarah: That must feel amazing.
14:40
Adrian: The research notes that employees suddenly experience a surge of new energy.
14:45
Adrian: They find alignment with a new workplace identity, they have renewed purpose, and they finally show clear, fluid mastery of the new tools.
14:53
Sarah: So the new kitchen is finally finished, the dust is swept up, and they are effortlessly cooking a masterpiece.
14:59
Adrian: Yes.
15:00
Adrian: And the required managerial action at this stage is to heavily reinforce those new behaviors.
15:05
Adrian: You celebrate the quick wins publicly, and crucially, you align their incentives and bonuses with the new operational goals.
15:12
Sarah: That makes sense.
15:12
Adrian: But here is the secret: getting them fully out of the neutral zone and into this new beginning rarely happens just because a manager tells them to.
15:21
Adrian: It requires a specific operational tactic.
15:23
Sarah: And this is where we get into mobilizing informal champions.
15:27
Sarah: I found this to be the smartest, most pragmatic advice in the whole deep dive.
15:31
Adrian: It's brilliant.
15:31
Sarah: Because every single department, every office, every Slack channel has those informal opinion leaders.
15:38
Sarah: These are the voices that actually shape peer culture, regardless of what the org chart says.
15:43
Adrian: It's a profound recognition of how workplace dynamics actually function in reality.
15:48
Adrian: Authority does not always equal influence.
15:51
Sarah: Exactly.
15:51
Sarah: So the tactic here is identifying these key individuals and bringing them in early.
15:56
Sarah: The research talks about involving them in user acceptance testing or UAT, gathering their feedback and transforming them into peer guides.
16:04
Sarah: Right.
16:05
Sarah: Now, for anyone who hasn't been through a tech rollout, UAT is basically when a company lets a small group of actual employees test drive the software before giving it to the whole company, usually to hunt for bugs.
16:16
Adrian: Yes.
16:17
Adrian: Normally UAT is treated as a technical exercise, but psychologically, it should be treated as an influence-building exercise.
16:24
Sarah: Because of human nature.
16:25
Adrian: Right.
16:25
Adrian: Think about it.
16:26
Adrian: If a VP of operations who hasn't done frontline data entry in 10 years, stands up and tells you a system is great, you are going to be inherently skeptical.
16:34
Sarah: Oh, 100%.
16:36
Adrian: But if your colleague, the person who sits two desks down and does the exact same grueling daily grind as who says the system's actually pretty great, you believe them.
16:44
Sarah: So let me make sure I'm synthesizing this correctly.
16:47
Sarah: Instead of the boss standing at the front of the room waving a shiny new manual and demanding compliance, you look for the most influential person in the office.
16:55
Adrian: Exactly.
16:56
Sarah: You know the one, the person everyone secretly slacks when the printer jams or when they need to know the real way to navigate expense reports.
17:03
Sarah: You grab them, you put them in the UAT group, you let them beta test the new software.
17:09
Sarah: Most importantly, you actually listen to their gripes and fix the things they hate.
17:13
Sarah: And then when it goes live, if they sign off on it, the rest of the team just naturally follows their lead.
17:19
Adrian: That is exactly the mechanism.
17:21
Adrian: Peer influence is the strongest bridge out of the neutral zone.
17:25
Adrian: It completely bypasses the friction of top-down mandates.
17:29
Sarah: Aaron Powell, it's like having an insider.
17:31
Adrian: Exactly.
17:31
Adrian: By turning that informal leader into a peer guide, you are essentially providing an experienced Sherpa for the rest of the team.
17:39
Adrian: They help their colleagues navigate the anxiety and ambiguity of the void because they've already walked the path.
17:44
Sarah: We've lived it.
17:45
Sarah: Right.
17:45
Sarah: They've already processed their own grief, let go of the old system, and found genuine value in the new one.
17:51
Adrian: It's brilliant because it's side-to-side support rather than top-down pressure.
17:54
Sarah: Yeah.
17:55
Adrian: Okay, let's pull all of this together for you, the listener.
17:57
Sarah: Yes.
17:57
Adrian: Whether you are a senior leader directing a massive multimillion dollar tech rollout, or you are just an everyday employee trying to survive one without losing your mind, remember the core lesson here.
18:11
Adrian: Resistance isn't stubbornness.
18:13
Sarah: Not at all.
18:13
Adrian: It is a natural, biologically expected psychological transition.
18:17
Adrian: You simply cannot force human minds through mandates.
18:21
Adrian: If you want sustainable adoption, you have to honor the past and validate the legacy mastery.
18:26
Sarah: And you have to actively bravely plan for the messy neutral zone productivity depth.
18:31
Adrian: Yes.
18:32
Adrian: And you have to lean on peer champions to pull everyone into the new beginning.
18:35
Sarah: And if we look at why this matters so deeply to your daily life, understanding this distinction between a situational change and a psychological transition is honestly a superpower.
18:45
Adrian: It really is.
18:46
Adrian: It can instantly reduce your workplace frustration.
18:49
Adrian: When the next big re-org happens, or an entirely new software suite drops on your desk on a Monday morning, you will have the empathy to understand what your colleagues and even you yourself are actually experiencing.
19:02
Sarah: It isn't just a new login screen.
19:04
Adrian: No, it's a profound process of letting go of your old competence, recognizing that one fact changes how you interact with everyone around you.
19:13
Sarah: It really does.
19:13
Sarah: It replaces frustration with grace.
19:16
Sarah: The insights we've explored today show us how carefully and intentionally we need to manage the transition away from legacy systems.
19:22
Sarah: Very true.
19:23
Sarah: But you know, digging into all this psychology makes you wonder what if all that passive resistance to change isn't actually a bug in human psychology that needs to be overcome?
19:32
Adrian: Oh, that's an interesting thought.
19:34
Sarah: What if it's rather a built-in, highly evolved protective feature?
19:38
Sarah: What if our natural stubborn hesitation is the only thing preventing organizations from blindly throwing away vital, hard earned institutional memory every time a shiny new piece of software hits the market?
19:50
Sarah: Next time you find yourself aggressively clinging to an old, messy spreadsheet, ask yourself are you just afraid of learning something new?
19:59
Sarah: Or are you secretly protecting something incredibly valuable that the new system entirely missed?