Latest / The Caribbean Workplace Wellness Channel / Fix the system not the person

Transcript

Fix the system not the person · The Caribbean Workplace Wellness Channel

0:12
Adrian: So picture this.
0:13
Adrian: You're sitting in uh just a horribly lit conference room.
0:18
Adrian: Or maybe you're staring at this grid of faces on a remarkably tense video call.
0:24
Sarah: Oh yeah.
0:25
Sarah: We've all been there.
0:26
Adrian: Right.
0:26
Adrian: A major project has just completely failed.
0:29
Adrian: Or I don't know, maybe a critical deadline was blown, or a massive operational error just cost the company a very, very uncomfortable amount of money, and the room is just heavy.
0:39
Sarah: Aaron Ross Powell You can practically hear everyone holding their breath, right?
0:42
Sarah: The collective dread in those moments, I mean, it literally feels like the air pressure in the room just drops.
0:48
Adrian: Aaron Powell It really does.
0:49
Adrian: Yeah.
0:49
Adrian: It's exactly like that dread you'd get as a kid being called into the principal's office.
0:53
Sarah: Yeah.
0:54
Adrian: You know?
0:54
Sarah: Oh, absolutely.
0:55
Adrian: Trevor Burrus, Jr.: Except now you're an adult and you're walking into a room full of people whose entire job is to figure out what you did wrong.
1:01
Adrian: You're just sitting there waiting for the hammer to fall.
1:03
Sarah: Yeah, you're waiting for the inevitable.
1:05
Adrian: Exactly.
1:05
Adrian: And the reason we feel that way is because we all know the script.
1:09
Adrian: We know exactly what's coming next, which is the classic corporate post-mortem.
1:13
Adrian: But today, our mission on this deep dive is to uh kind of completely rewire that experience.
1:20
Sarah: Aaron Powell Which is so desperately needed, honestly.
1:22
Adrian: It is.
1:23
Adrian: We're going to explore how the absolute best teams handle catastrophic failures, but without destroying their culture in the process.
1:31
Adrian: And we're pulling from this really fascinating framework provided by the Caribbean Workplace Wellness Channel and the Institute for Mental Health and Well-Being.
1:39
Sarah: Aaron Powell And it is just a deeply necessary framework because the way most organizations currently handle failures, well, it's fundamentally broken.
1:47
Sarah: They treat these postmortem meetings as tribunals, you know, like a trial rather than actual rigorous investigations into what happened.
1:54
Adrian: Aaron Powell Right.
1:55
Adrian: So let's unpack this.
1:56
Adrian: Because the standard corporate reflex, and I mean I've I've seen this, you've seen this.
2:00
Adrian: When things go wrong, the immediate instinct from senior leadership is to start hunting for a culprit.
2:06
Adrian: The very first question out of someone's mouth is usually, who dropped the ball here?
2:10
Adrian: Or uh who is responsible for this oversight?
2:13
Sarah: Aaron Powell Which, to be fair, is an entirely predictable human response.
2:17
Sarah: I mean, when a complex project fails, it creates chaos.
2:21
Sarah: Totally.
2:22
Sarah: It creates this terrifying sense that things are just out of control.
2:25
Sarah: So psychologically, pointing a finger at one specific person finding a villain, it actually provides immediate emotional closure for the leadership team.
2:33
Adrian: Aaron Powell Oh, that makes sense.
2:34
Adrian: It's a quick fix.
2:35
Sarah: Exactly.
2:36
Sarah: It neatly ties up the narrative.
2:37
Sarah: A manager can just say, ah, well, Steve and accounting messed up.
2:40
Sarah: We've reprimanded Steve.
2:42
Sarah: The problem is solved.
2:43
Adrian: Aaron Powell Right.
2:43
Adrian: So it gives this illusion of fixing the problem without actually having to do the hard, tedious work of looking at the machinery underneath.
2:51
Sarah: Aaron Powell That is the trap right there.
2:52
Sarah: It's just the psychological band-aid.
2:54
Sarah: But the damage this uh this punitive approach does to an organizational culture is incredibly severe.
3:01
Sarah: Aaron Powell.
3:02
Sarah: Well, when you run a post-mortem like a witch hunt, you are actively conditioning your staff to do three very dangerous things.
3:09
Sarah: First, you teach them to hide their mistakes at all costs.
3:13
Adrian: Because they don't want to be the one yelled at.
3:14
Sarah: Right.
3:15
Sarah: Second, you teach them to shift blame onto their colleagues just as a survival tactic.
3:21
Sarah: And third, you teach them to obscure operational data.
3:25
Adrian: Oh, wow.
3:26
Adrian: And obscuring operational data means leadership is now basically flying blind.
3:30
Sarah: Precisely.
3:31
Adrian: You're making strategic decisions based on these sanitized reports where all the real problems have been scrubbed out, just because people are terrified to show you the ugly truth.
3:40
Sarah: You've hit on the fundamental tension there.
3:42
Sarah: When a company operates on fear, the data stream gets corrupted.
3:46
Sarah: Leaders think everything is totally fine right up until the moment a massive failure occurs.
3:51
Adrian: Okay, but hold on though.
3:52
Adrian: I'm thinking about the realities of running a team here.
3:54
Adrian: Sure.
3:55
Adrian: If someone genuinely messes up, like let's say Steve in accounting literally types the wrong authorization code and just crashes a client's server.
4:05
Adrian: Isn't calling them out just basic accountability?
4:07
Adrian: I mean, how do people actually learn if we don't say, hey, you drop the ball here?
4:11
Sarah: That is uh that's the most common pushback to this concept, actually, and it's exactly why the punitive model persists.
4:18
Adrian: Because it feels like common sense.
4:20
Sarah: It does.
4:21
Sarah: But if we look closely at the mechanics of failure, pointing fingers doesn't actually prevent the mistake from happening again.
4:28
Sarah: In fact, it actively ensures that the same mistake will repeat itself.
4:32
Adrian: Wait, why?
4:33
Adrian: Because punishing Steve doesn't change the environment he was working in.
4:36
Sarah: Exactly that.
4:37
Sarah: If you just blame Steve and move on, you haven't changed the system that allowed Steve to make the mistake in the first place.
4:44
Adrian: Ah, I see.
4:45
Sarah: And this realization is exactly why industries where mistakes literally mean life and death had to invent a completely different approach.
4:52
Sarah: We're talking about high reliability industries, you know, aviation, nuclear power, complex software engineering.
4:59
Adrian: Okay, knowing this framework comes from nuclear power, and aviation definitely makes me set up and pay attention.
5:05
Adrian: Because if a commercial flight has a critical malfunction or like a reactor goes into a warning state, the safety boards don't just look for a single operator to yell at.
5:14
Sarah: They cannot afford to.
5:15
Sarah: In those fields, they conduct what are called blameless debriefs.
5:19
Adrian: Blameless debriefs.
5:20
Adrian: Okay.
5:20
Sarah: Yeah.
5:21
Sarah: And this model rests on one core non-negotiable philosophy.
5:26
Sarah: Human error is merely a symptom of a flawed system.
5:30
Sarah: It is almost never the root cause.
5:32
Adrian: Human error is a symptom, not the cause.
5:35
Adrian: That is a massive paradigm shift.
5:37
Sarah: It completely changes how you view a workforce.
5:40
Sarah: The framework highlights something simple but often forgotten, which is that employees do not come to work intending to fail.
5:46
Adrian: Right.
5:47
Sarah: With the incredibly rare exception of intentional sabotage, nobody wakes up, logs into their computer, and thinks, man, I really can't wait to ruin this project today.
5:56
Adrian: Right.
5:57
Adrian: People generally want to succeed, they want to do good work, get paid, and go home.
6:00
Sarah: Right.
6:00
Sarah: So if an employee wants to succeed, but a catastrophic error still occurs, we have to look for the real culprits.
6:06
Sarah: And according to the research, those culprits are systemic.
6:09
Adrian: Like what?
6:09
Adrian: Exactly.
6:10
Sarah: Well, the internal processes are ambiguous, or the software tools provided are inadequate, maybe the training was incomplete, or critical safety checks were entirely missing from the workflow.
6:19
Sarah: If you just punish the worker, the system stays broken.
6:22
Adrian: I love a good analogy.
6:24
Adrian: And this is painting such a clear picture for me.
6:26
Adrian: It's like it's like firing a delivery driver because they crashed a truck, but completely ignoring the fact that the brake lines were cut.
6:34
Sarah: Yes.
6:34
Sarah: That is perfect.
6:35
Adrian: Right.
6:36
Adrian: You can yell at that driver, you can fire them, you can go out and hire the most skilled, expensive driver in the world to replace them.
6:42
Adrian: But the absolute second you put the new driver in that same truck, they're gonna crash too.
6:48
Sarah: And taking it a step further, the new driver might crash even worse because they don't even know the truck is flawed.
6:54
Adrian: Oh wow.
6:54
Adrian: Yeah.
6:54
Sarah: Firing the original driver gives leadership that temporary emotional closure, like we talked about, but it leaves the next worker incredibly vulnerable.
7:03
Adrian: Aaron Powell So the blameless debrief is entirely about getting under the hood and fixing the brakes.
7:08
Sarah: Exactly.
7:08
Sarah: And the sources actually outline three highly actionable rules-like actual steps for how you can run these debriefs with your team.
7:16
Adrian: Well, let's get into the mechanics of this then, because I want the listener to be able to take this into their very next team meeting.
7:23
Adrian: How do we practically shift a room full of stressed-out, defensive people away from the blame game?
7:29
Sarah: Aaron Powell The transformation starts with the first rule of the framework, which is separate system performance from personal accountability.
7:36
Adrian: Okay.
7:36
Sarah: When you sit down in that conference room, the systemic design has to remain the absolute unwavering focus of the conversation.
7:43
Adrian: Aaron Powell Meaning we have to basically decouple the person from the process.
7:47
Sarah: Yes.
7:47
Adrian: But how do you actually say that out loud?
7:49
Adrian: Do you just start the meeting by announcing, uh, hey everyone, nobody is in trouble.
7:54
Sarah: Actually, yeah, pretty much.
7:55
Sarah: You need a concrete script to set the tone right away.
7:58
Sarah: A leader should open the meeting by explicitly stating something like: Our goal today is to map the system, not to evaluate the personnel.
8:07
Sarah: We are looking for where our workflow broke down.
8:10
Adrian: That sets a very different vibe.
8:11
Sarah: It does.
8:12
Sarah: And the sources provide a really clear story to illustrate how this plays out in real life.
8:17
Sarah: Imagine a scenario where a mid-level employee makes a wrong choice that basically derails a major project timeline, causing a huge delay for a client.
8:26
Adrian: Okay.
8:26
Adrian: Under the old way, like the traditional corporate tribunal, that employee gets hauled in, reprimanded, maybe put on a 90-day performance improvement plan.
8:36
Adrian: Or even fired.
8:37
Sarah: Exactly.
8:37
Adrian: The entire meeting is just focused on their failure to execute.
8:40
Sarah: Aaron Powell, but under the blameless debrief model, leadership starts with the assumption that the employee wanted the project to succeed.
8:47
Sarah: So the meeting explores why they made the choices they did.
8:50
Adrian: Interesting.
8:51
Sarah: And in this specific case study, the debrief revealed two critical systemic flaws.
8:57
Sarah: First, the project dashboard the employee was required to use was highly confusing.
9:01
Sarah: Key metrics were buried under three different menus, and the data was lagging by 24 hours.
9:06
Sarah: That's a nightmare.
9:07
Sarah: Right.
9:07
Sarah: And second, the process timeline handed down by the sales team was impossibly rushed, giving them zero buffer for QA testing.
9:14
Adrian: So the employee was basically set up to fail.
9:17
Adrian: They were flying a plane with faulty instruments while being told to break the speed limit.
9:21
Sarah: Exactly the case.
9:22
Sarah: And because the blameless debrief uncovered those specific systemic issues, the solution isn't to fire the employee.
9:30
Sarah: Right.
9:30
Sarah: The actionable solution is that the team works with IT to fix the confusing dashboard, and they implement a new rule requiring a mandatory 48-hour buffer on all sales timelines moving forward.
9:43
Sarah: They fix the system.
9:44
Adrian: But let me ask about the gray area here.
9:46
Adrian: Because I know someone listening is wondering this.
9:48
Adrian: What if the employee actually is just slacking off?
9:52
Adrian: Does a blameless debrief mean nobody is ever held accountable for their behavior?
9:56
Adrian: Because honestly, that sounds like a recipe for a completely chaotic workplace where nothing matters.
10:02
Sarah: That is a vital caveat in the framework, and it's really important to clarify the definitions here.
10:06
Sarah: A blameless debrief does not mean an absence of accountability.
10:10
Adrian: Okay, what does it mean then?
10:11
Sarah: What we are doing is shifting the type of accountability.
10:15
Sarah: Individuals are absolutely still accountable for their professional effort and for adhering to agreed upon documented protocols.
10:24
Sarah: Got it.
10:24
Sarah: If a clear safety protocol exists and they are fully trained on it, they have the time to execute it and they willfully ignore it, that is an HR issue.
10:33
Sarah: That's a completely different conversation.
10:35
Adrian: Okay, that makes perfect sense.
10:37
Adrian: We expect professional effort, but if you give your best professional effort and you still crash the truck, we look at the system.
10:43
Sarah: Exactly.
10:44
Adrian: But human nature makes that incredibly difficult.
10:47
Adrian: After a disaster, it is so easy for management to look at the wreckage and say, Well, obviously that dashboard was confusing, you should have figured that out, or you should have known that timeline was too tight and pushed back.
10:57
Adrian: How do we fight off that instinct?
10:59
Sarah: That instinct is what the framework calls hindsight bias.
11:03
Sarah: And it brings us to the second rule.
11:05
Sarah: Focus on context over hindsight.
11:08
Adrian: Hindsight bias.
11:09
Sarah: Yeah.
11:10
Sarah: It is deeply toxic to an investigation.
11:13
Sarah: It's the trap of sitting in a sterile, well-lit conference room a week after the event, looking at all the data and saying, oh, they should have known X would happen.
11:23
Adrian: It's so easy to do that though.
11:24
Adrian: It reminds you of like armchair quarterbacking.
11:27
Sarah: Yes.
11:28
Sarah: It is so.
11:28
Adrian: Or like looking at a post-operative report and criticizing a surgeon for making a sloppy incision.
11:33
Adrian: It's incredibly easy to judge the cut when you're sitting at a desk reading a PDF with your morning coffee.
11:39
Adrian: Right.
11:39
Adrian: But you aren't the one standing in the operating room during a sudden power outage holding a faulty scalpel while a patient's vitals are crashing and an alarm is blaring in your ear.
11:49
Sarah: That is the perfect visualization of the problem.
11:52
Sarah: Hindsight bias strips away all the reality, all the stress, and all the friction of the actual moment.
11:58
Sarah: Right.
11:58
Sarah: To defeat it, the framework gives us a specific tool, a literal mock scenario script for leaders to use.
12:05
Sarah: Instead of asking the accusatory question, why did you do this?
12:08
Sarah: Yeah, you have to reconstruct the exact context of the moment the decision was made.
12:12
Adrian: And what does that actually sound like in practice?
12:15
Sarah: You frame the question like this.
12:17
Sarah: Given the information pressure and time constraints present on Tuesday at 3.0 p.m., why did this choice make sense to the operator?
12:25
Adrian: Let me just repeat that for the listener, because that phrasing is a total game changer.
12:30
Sarah: It really is.
12:31
Adrian: Given the information, pressure, and time constraints present on Tuesday at 3-0 p.m., why did this choice make sense to the operator?
12:40
Adrian: It completely removes the judgment from the equation.
12:44
Sarah: It replaces judgment with genuine curiosity.
12:46
Sarah: And if we look at the psychology behind why this works, when you ask why a decision made sense to someone at the time, you are actively validating their intelligence.
12:55
Adrian: Oh, I see.
12:56
Sarah: You are signaling, I know you are a smart, capable professional.
12:59
Sarah: So if this seemed like the right move at 3 p.m.
13:01
Sarah: on Tuesday, what were you seeing on your screen that I am not seeing on mine?
13:05
Adrian: And that lowers their defensive threat response.
13:07
Adrian: Exactly.
13:08
Adrian: Instead of crossing their arms and protecting themselves, they can say, Well, at 3 p.m.
13:11
Adrian: the system was flashing green, my manager had just emailed me to hurry up, and the standard operating manual explicitly said to proceed under those conditions.
13:20
Sarah: Great.
13:20
Adrian: Suddenly, you aren't looking at a careless employee.
13:24
Adrian: You are looking at a broken warning light, a communication breakdown, and an outdated manual.
13:29
Sarah: You've successfully reconstructed the context.
13:32
Sarah: You found the cut breaks.
13:33
Sarah: Wow.
13:34
Sarah: But discovering that the manual is outdated doesn't actually help the organization if that discovery never leaves the room.
13:40
Sarah: Okay.
13:40
Sarah: Which leads us to the final piece of the puzzle.
13:43
Sarah: The third rule: publish and share lessons learned enterprise-wide.
13:47
Adrian: Publish it.
13:48
Adrian: Like actively broadcast our failures to the rest of the company.
13:52
Sarah: Yes.
13:52
Sarah: A blameless debrief is practically useless if the findings stay locked inside a departmental silo.
13:59
Sarah: The framework emphasizes that the ultimate goal is transforming a local mistake into what they call organizational intelligence.
14:06
Adrian: Organizational intelligence.
14:07
Adrian: Yeah.
14:07
Adrian: Okay, so it means the whole company gets smarter because one single team stumbled.
14:12
Sarah: Exactly the goal.
14:13
Sarah: The actionable step here is to meticulously document the findings of your debrief and push them out across departments.
14:19
Sarah: You share the story of the confusing dashboard and the rushed timeline.
14:23
Sarah: You do this so that other teams can proactively audit their own workflows for similar vulnerabilities.
14:29
Sarah: The marketing team might read that report and realize wait, our dashboard has the exact same lag issue.
14:35
Sarah: We need to fix this before it burns us too.
14:38
Adrian: I mean, I understand the logical utility of that.
14:40
Adrian: It's incredibly efficient.
14:42
Adrian: But the cultural reality of sending that email, it must take an incredible amount of psychological safety to publish your team's mistakes in a company-wide newsletter.
14:51
Sarah: It does.
14:52
Adrian: In most corporate cultures, if you make a mistake, you bury it deep in the woods.
14:55
Adrian: You certainly don't write a memo about it.
14:57
Sarah: It does feel counterintuitive.
14:59
Sarah: But here is the beautiful psychological paradox of this framework.
15:03
Sarah: The act of publishing the failure is actually what builds the psychological safety.
15:08
Adrian: Wait, really?
15:09
Adrian: Explain the mechanism there.
15:10
Adrian: How does broadcasting a failure make people feel safer?
15:13
Sarah: Well, think about it.
15:14
Sarah: When an employee reads a company-wide memo where senior leadership openly takes responsibility for a bad process, when they see an email that says, Here is where our timeline failed, our project manager, and here is how we are fixing the timeline, it sends a powerful signal to the employee's brain.
15:32
Adrian: It proves that they won't be thrown under the bus.
15:35
Sarah: Exactly.
15:36
Sarah: It proves that it is safe to report their own near misses.
15:39
Sarah: It lowers the organizational threat response.
15:42
Sarah: It models a vulnerability from the top down.
15:45
Adrian: Okay, that is brilliant.
15:46
Adrian: You aren't just telling them it's safe, you're showing them the proof.
15:49
Sarah: Right.
15:49
Adrian: So for the listener who wants to start doing this tomorrow, what does that publication actually look like?
15:54
Adrian: Are we just sending out a long, dramatic apology letter?
15:56
Sarah: Not at all.
15:57
Sarah: It should be highly clinical and structured.
15:59
Sarah: You want to create a standard template.
16:01
Sarah: It usually has three short sections.
16:03
Sarah: First, the incident, what happened without any names attached.
16:06
Sarah: Second, the systemic cause, the context, and the broken processes discovered.
16:12
Sarah: Third, the fix the concrete steps taken to update the system so it doesn't happen again.
16:16
Sarah: Keep it focused entirely on the engineering of the work.
16:19
Adrian: So synthesizing all of this for the listener who is, you know, maybe dreading their next project review, what is the core takeaway here?
16:27
Adrian: What does this all mean for the future of their team?
16:30
Sarah: The biggest misconception we really need to break is that blameless debriefs eliminate accountability.
16:36
Sarah: They don't.
16:36
Sarah: Right.
16:36
Sarah: They elevate it.
16:37
Sarah: They move a team away from superficial, lazy scapegoating and push them toward rigorous, deep systemic improvement by committing to this framework, separating the system from the person, focusing on context over hindsight, and publicly sharing the lessons learned leaders replaced the witch hunt with an engineering mindset.
16:55
Sarah: Yeah.
16:56
Sarah: And in doing so, they rebuild the very trust that punitive meetings destroy.
17:01
Adrian: It's the ultimate reframe.
17:02
Adrian: Failures completely transform.
17:04
Adrian: They stop being these shameful radioactive secrets that we have to sweep under the rug, and they literally become stepping stones for institutional excellence.
17:13
Sarah: Exactly.
17:13
Adrian: We cannot actually get better unless we are willing to look at the broken pieces together without pointing fingers.
17:21
Sarah: And when a team finally feels that shift, when they realize leadership is genuinely hunting for bad processes instead of hunting for bad employees, the trust skyrockets.
17:32
Adrian: Because they know you have their back.
17:34
Sarah: Right.
17:34
Sarah: People actually start raising their hands during the week and saying, Hey, I almost made a mistake today because this software tool is highly confusing.
17:41
Sarah: That allows you to fix problems before they ever escalate into a disaster.
17:45
Adrian: Which is the holy grail of management, preventing the fire before a single spark catches.
17:50
Sarah: Absolutely.
17:51
Adrian: Well, we've spent this entire time talking about corporate teams, enterprise workflows, and postmortem meetings, but I want to leave you with a final thought to mull over something entirely outside the boardroom.
18:02
Adrian: Think about your own life.
18:04
Adrian: What would happen if you applied the blameless debrief to your personal relationships?
18:09
Sarah: Oh, it's a fascinating application of the core psychology.
18:12
Adrian: Right.
18:13
Adrian: I mean, think about it.
18:14
Adrian: The next time a massive communication breakdown happens with a partner or a spouse or a close friend, instead of jumping to that immediate natural reflex of asking, why did you do that?
18:26
Adrian: How could you say that?
18:27
Sarah: Yeah, the classic blame game at home.
18:29
Adrian: Exactly.
18:30
Adrian: What if you both sat down at the kitchen table, took a breath, and used the script?
18:34
Adrian: What if you asked, given the information, exhaustion, and the emotional pressure we were both under on Tuesday at 3 or UPM, why did that argument make sense to us?
18:42
Adrian: And how do we fix our communication dashboard?
18:45
Adrian: It might just change the way you look at everything.
18:47
Sarah: Blameless curiosity.
18:48
Sarah: Whether you are in the office or at the kitchen table, replacing judgment with curiosity is always a path to better understanding.
18:54
Adrian: Absolutely.
18:55
Adrian: Well, thank you so much for joining us on this deep dive.
18:57
Adrian: We hope you can take this framework, ditch the hindsight bias, and start fixing the systems in your own world.
19:03
Adrian: Until next time, stay curious.