Organizations do not change people do
Transcript
Made automatically from the audio, so it may contain mistakes. Click a line to play from there.
In 2003, NASA faced this this really massive reckoning. After the tragic loss of the space shuttle, Columbia, the organization realized something kind of terrifying.
Right, because it wasn't just a technical issue, right?
Exactly. The smartest engineers on the planet, you people who literally calculate orbital mechanics in their sleep, they didn't just have a technical problem with foam insulation breaking off a fuel tank. They had a human problem.
A completely cultural problem, yeah.
Right. They realized they needed to completely overhaul how they communicated and you know how they assessed risk and how they reported problems up the chain of command.
Which is incredibly difficult.
It is because how do you actually get thousands of entrenched, highly intelligent people to just like change their daily habits? I mean, if you've ever tried to change a simple habit of your own, let alone overhaul a massive corporate culture, you know that human change is wildly unpredictable.
Oh, it is incredibly murky. I mean, when we build a bridge, it's just engineering, you know. You calculate the load, you put it the concrete and the bridge stands.
Yeah, the math just works.
Right. And we expect that same mathematical precision when we try to implement like a new software system at work or roll out a new environmental policy. But the moment you introduce human emotion and personal ambition and frankly fear into the equation, that precision just vanishes.
Which is exactly why today's deep dive is so vital, honestly. We are tearing apart a concept called the 80 car change model to really understand the actual anatomy of successful change and why we so often fail at it.
It's a really powerful framework.
It totally is. And we've got a fantastic stack of sources on the table for you today. We're pulling heavily from Jeff Hyas' massive 2006 book on the model, which is actually backed by data from like 900 organizations across 59 countries.
That's a huge data set.
Yeah, it's massive. And we're layering that with a 2019 academic review by Havana Sa Engtian to see how it works in the real world. Plus, because no model is perfect, obviously, we are dissecting a pretty sharp critique by Stephen Warlow.
Because he exposes some major blind spots in this whole theory.
Exactly. And the foundational secret we are exploring today for you, the thesis that kind of ties all these sources together is this organizations do not change. People do.
Right. You cannot mandate a culture shift. I mean, you can only facilitate the transition of one individual person at a time, step by step.
Okay, let's unpack this because it actually circles back to that engineering mindset you mentioned. The guy who developed AD Carr, Jeff Hyatt, he actually started his career as an engineer at Bell Labs.
Yeah, and think about Bell Labs for a moment. I mean, this is the institution that brought us the transistor, the laser, like the very foundation of the modern digital age.
Right.
Hyatt spent almost two decades there leading these large-scale process and system changes, and he had all this rigorous undergraduate and graduate engineering training.
So he expects things to work logically.
Exactly. Yet he realized that the most complex, intractable problems he faced, they weren't technical at all. The physics and the mathematics always worked out. It was the people who broke the systems.
It is that classic trap. I mean, I've seen this happen so many times. A company decides they need to modernize, right? So they spend millions mapping out the new processes, buying the shiny new software, redesigning the whole organizational chart.
And they focus entirely on the tangible technical side.
Totally. And they completely ignore the soft, messy transitional side of the actual human beings who have to, you know, log into that software every morning.
Hyatt actually used to joke that his change initiatives would have gone flawlessly if it weren't for all the people involved.
That is so true.
And because he was an engineer, he grew deeply frustrated by how abstract and vague the the people side of change management was at the time. You know, consultants would come in and prescribe endless communication blitzes.
Or those really vague team building retreats.
Exactly. Hyatt kept looking at these activities and asking to what end? What is the specific measurable result this trust fall is supposed to produce?
He wanted a blueprint.
He wanted a results-oriented framework, yeah. And that relentless focus is what produced ADK or NOR. It's an acronym that lays out a very strict sequence for individual change.
And the sequence is awareness, desire, knowledge, ability, and reinforcement. Right. Hold on though, I need to push back on this right out of the gate. You're telling me human beings who are famously irrational and emotional and messy process change in a perfect linear five-step checklist.
I know it sounds a bit rigid.
It sounds exactly like an engineer's fantasy of how psychology should work. Like, do we really just march from A to D to K like robots?
It's a very fair skepticism, and we're absolutely gonna dive deep into that exact criticism when we get to Warlow's analysis later. Human nature is chaotic.
Right.
But Hyatt's data suggests that while the human experience is messy, the requirements for transition are not. His argument is that this sequence represents the necessary milestones of change.
So you have to hit them in order.
Exactly. You simply cannot jump to training someone, which is knowledge, if they haven't made the personal choice that they actually want to learn it, which is desire.
So it's more like a diagnostic sequence. Like if something is broken, you check the steps in order.
What's fascinating here is that the data shows businesses constantly make the mistake of ignoring the sequence. A company rolls out a new system, the employees immediately push back and complain, and management's knee-jerk reaction is always, oh, they don't understand the system. We need to schedule more training sessions.
Oh, wow, yeah.
They're trying to train people out of resistance. They confuse a lack of desire with a lack of knowledge.
Okay, that makes so much sense. It's like trying to build a house by installing the roof before you've poured the foundation. You just can't do it.
No, you really can't.
Which takes us to that foundation, the very first A in the acronym awareness. Yeah. And we should probably clarify, awareness is not just HR sending out a company-wide email saying, Hey everyone, we're migrating to a new server on Monday.
Not at all. That is communication. That's not awareness. According to Hyatt's research, true awareness is an individual's deep internalized understanding of the nature of the change.
So it's about the why.
Yes. It's understanding why the change is needed, and most crucially, understanding the risk of doing nothing. In a massive study of companies undergoing major shifts, the number one reason employees cited for resisting change was simply a lack of awareness of why the change was happening in the first place.
Because we aren't cogs in a machine. You know, we need a reason. But giving someone a why seems like it should be easy. Just tell them the business is losing money or the current system is outdated. Why is creating that awareness so difficult?
Well, because your message is filtered through the psychology of the person receiving it. The sources identify five specific factors that complicate how awareness is actually built.
Okay, what's the first one?
The first is simply the individual's view of their current state.
The if it ain't broke, don't fix it mentality. Like, if I've spent five years mastering a specific software and I'm comfortable, my default reaction to a new system is going to be denial. The status quo is working perfectly fine for me, so I will actively block out your reasons for changing it.
Which bleeds right into the second factor, how a person perceives problems in general. The text highlights some really fascinating research here by Dr. Michael J. Curtin.
Oh, the adapters and innovators, right?
Yeah. He studied the cognitive styles of managers and found they generally fall on a spectrum between what he calls adapters and innovators. Adapters are wired to look for internal threats. They want to economize, downsize, and you know, fix inefficiencies within the system that already exists.
And the innovators are different.
Right. Innovators are the opposite. Their radar is pointed outward. They are scanning the horizon for external events, shifting market trends, new technologies, stuff like that.
This is such a brilliant way to understand conflict in an office, honestly. It's like it's like you have two people sitting in a living room. The adapter is hyper focused on a leaky faucet in the kitchen. They are completely obsessed with fixing this internal inefficiency. Meanwhile, the innovator is staring out the window, watching a massive tornado forming on the horizon.
That is a perfect analogy.
Right. Because if you walk into that house and try to build awareness about the tornado with the adapter, they might completely ignore you or even get angry because in their mind the real tangible problem is the leaky faucet.
Yeah, you have to tailor your awareness message to match how the person actually perceives the world. But even if you frame the problem perfectly, you hit the third factor, the credibility of the sender.
Oh man.
The message is only as strong as the messenger.
That's the boy who cried Wolf syndrome.
Yeah.
If a CEO has a history of announcing massive revolutionary changes every January, only to just quietly abandon them by April, employees learn to just nod and smile.
Exactly. They won't internalize the awareness because they fundamentally don't believe the sender will follow through.
And nature abhors a vacuum. Right. Which brings us to the fourth factor.
Yes, the circulation of misinformation and rumors. If leadership lacks credibility or, you know, withholds information, the water cooler talk takes over. And a manager will spend significantly more time trying to deprogram the false rumors than they would have spent just explaining the harsh truth on day one.
Which leaves the fifth factor, which is how debatable the reasons for change actually are. The text calls this contestability, right?
Yes. If a change is driven by an undeniable external force, say, like a new federal regulation awareness is relatively easy to build.
Because the law is the law.
Exactly. But if the reasons are internal and subjective, like a new VP deciding to restructure teams just to shake things up or you know, create synergy people, will naturally contest the logic. The more debatable the reason, the harder it is to build awareness.
To really see how these factors play out in the real world, the sources provide some wild case studies. Let's look at the pineapple growers in Ghana. This is a perfect example of overcoming that initial resistance.
Oh, this is a great one.
Yeah. These farmers were facing the implementation of new, stringent agricultural codes of practice. It required reducing pesticide use and completely altering generations of growing methods. To the farmers, this just sounded like a massive, risky internal headache.
And you couldn't just mandate compliance from afar. I mean, the farmers had no view of the current state that suggested anything was broken. So the organizers had to launch a massive awareness campaign.
Right.
But crucially, they didn't focus the campaign on the technical agronomic details of the new codes. That would have bored or alienated the farmers entirely. Instead, they focused entirely on the external threat.
The UK supermarkets.
Exactly. They made the farmers deeply aware that highly lucrative buyers of the UK were making code compliance a non-negotiable prerequisite. The message wasn't you need to farm better. The message was if we do not comply, we lose access to our biggest, most profitable market.
They built awareness by making the severe economic risk of not changing incredibly visible.
They made the tornado visible to the adapters, basically.
Yeah. Another fascinating example from the text comes from Graz, Austria. The city officials there had a huge problem. They needed to lower automobile emissions. But a city government can't just force citizens to buy different cars.
Right, and emissions are invisible.
Exactly. Individual drivers don't feel a daily urgent need to solve global air quality issues. So how do you build awareness for something you literally can't see?
The city of Graz implemented a brilliantly simple policy. They drastically lowered the parking tariffs for low emission vehicles, like hybrids. But the real genius was that they issued a special, highly visible parking sticker for those qualifying cars.
It turned an abstract environmental problem into a visible daily reality. Yes. Not only was there a financial incentive, but every time you walked down the street, you saw exactly which cars were contributing to the solution. It forced the public to constantly interact with the issue, which dramatically increased collective awareness without passing a single mandate.
The U.S. Environmental Protection Agency used a very similar tactic with Dell, actually. The EPA was struggling to make the public aware of the massive e-ways problem.
Right. Specifically the eighty million computers thrown into landfills every year.
Yeah, leaching toxic lead into the soil.
Because I mean, who thinks about where their old laptop goes? You throw it away and it just disappears.
Right. The public lacked awareness. So the EPA partnered with Dell, leveraging a massive government contract to lease a hundred thousand computers, with Dell acting as the primary recycler at the end of the life cycle.
Wow, that's smart.
By using Dell's massive corporate reach and advertising power, the EPA piggybacked on their platform to broadcast the recycling issue to a much wider audience. In all of these cases, the farmers, the drivers, the computer buyers, the first step was proving that the current state was no longer viable.
The house is on fire.
The house is on fire.
But here is where the model gets really interesting and well, really difficult. Let's go back to our burning house. You've done the work, you've convinced me the house is on fire.
Okay.
But what if I just sit down on the couch? What if I paralyzed by fear? Or I just don't care enough to run out the door. Awareness isn't enough to make me move, is it?
No, it is not. And this is the most perilous gap in change management. Moving from awareness to the second building block.
Yeah.
Desire. Desire. Desire represents the motivation and ultimately the personal choice to support and participate in the change. Hyde's research makes a very stark point here.
Yeah.
Leaders cannot control desire. You can mandate a process, you can mandate attendance at a meeting, but you cannot mandate that a human being actually wants to change.
Man, if you're managing a team right now, that is a terrifying reality. You can give your team all the facts, you can show them the spreadsheets, but the final choice remains locked inside their own heads. And according to the sources, that choice is driven by four factors. The most famous being, you know, what's in it for me, or the YFM. Does this change represent a threat to my job security or an opportunity for promotion? Is the compensation fair?
The YFM is the baseline, yeah. But the second factor is the organizational context, which we touched on a bit earlier. If an employee looks at the history of the company and sees that executives always get a pass during difficult transitions, or that past changes resulted in mass layoffs, despite promises to the contrary.
Their desire is gone.
It plummets.
And the third factor is something a manager might not even know about the individual's personal situation. What is happening in their life the moment they leave the office?
This is so important.
It is. Are they dealing with a brutal divorce, a health crisis? Are they drowning in debt? A person's capacity to embrace a disruptive change at work is deeply tethered to their emotional bandwidth at home. Like an employee might reject a promotion that requires learning a new system, which looks crazy to a manager, but it makes perfect sense if you know that employee is currently taking care of a sick parent and literally cannot handle one more ounce of stress.
That level of empathy is crucial. What is the internal engine that drives this specific person?
Right.
Some people are driven by a deep desire to help others. Some are driven by the accumulation of wealth or the pursuit of status, or simply just the avoidance of pain.
The sources provide a really intense breakdown of this by analyzing Lance Armstrong. And look, regardless of how his story ended with the doping scandals and everything, the text uses his decision to attempt a seventh Tour de France victory as a master class in dissecting desire.
It's a perfect encapsulation of those four factors operating simultaneously. I mean, think about the magnitude of the change required for him to attempt a seventh win. First, look at the nature of the change, the Y of M. The Tour de France is the pinnacle of the sport. The visibility, the cementing of a historical legacy, and the massive financial windfalls were just unparalleled.
Then look at the environmental context. He had a track record of complete dominance in this specific event. He had the weight of massive corporate sponsors and millions of fans expecting him to race.
He was aging in a brutal sport.
Yeah, cycling is rough.
Very. He had immense physical wear and tear, he had family obligations, and the sheer agonizing time commitment required to train at that level was a massive deterrent.
Which is why the fourth factor, intrinsic motivation, had to be so powerful. He had an internal drive to win, a psychological need to dominate that was strong enough to override the physical pain and the personal sacrifices. All four of those factors aligned, creating an overpowering desire to commit to the change.
Now compare Lance Armstrong's intrinsic motivation to win a global sporting event to a mid-level data entry clerk being told they need to learn a new software system by Friday. Right. If we connect with the bigger picture, organizational leaders consistently make the fatal assumption that by building awareness, they automatically manufacture desire.
They think it just happens.
Exactly. An executive will stand on a stage and say, We need to adopt this new system to increase shareholder value by four percent. That is the executive's intrinsic motivation. It is incredibly rare that increasing shareholder value is the intrinsic motivation of the frontline worker.
So if you're a manager and you realize you can't force desire, and you know your team isn't motivated by shareholder value, what can you actually do? Are you just helpless? Are you just crossing your fingers and hoping they find their inner Lance Armstrong?
You are not helpless. While you cannot mandate the choice, leadership is entirely about architecting the environment in which that choice is made. And this takes us deep into the mechanics of managing resistance.
To fix resistance, we have to understand what it actually looks like on the ground, right? The research outlines some very raw, very human reasons why employees push back. It's rarely just stubbornness.
No, it's usually fear.
People resist because they are terrified of layoffs. They resist because they look at the new required skills and feel completely inadequate. They cling to the old way because that is where they earn their current status and respect. Yep. Or perhaps most common of all, they see the new initiative as a slick way for the company to force them to do more work for the exact same pay.
And we cannot ignore manager resistance, which the data suggests can actually be far more toxic than employee resistance.
Wait, really?
Oh, absolutely. Managers resist change because it threatens their feastums, they fear a loss of budget or headcount, they're often already working at maximum capacity, and a new change initiative feels like the straw that will break their back.
Or they don't know how to lead it.
Exactly. They secretly realize they lack the soft skills required to coach their own employees through the emotional turmoil of the transition, so they quietly sabotage the project to avoid exposing their own incompetence.
So, how does an organization break through that wall of resistance? According to the ADK framework, it has to start at the absolute top, with the primary sponsor of the change, the CEO, or the VP driving the initiative. And the sources are brutal about this. The sponsor cannot just show up at the kickoff meeting, give a rousing speech, sign a memo, and disappear.
No, that is known as abdication. And it is fatal to change. The primary sponsor must remain active and visible throughout the entire lifespan of the project. They have to build a unified coalition among all the other leaders, ensuring there is no daylight between executives, and they must communicate directly with the employees on the ground.
The sources highlight the worst mistake a sponsor can make, which they call the flavor of the month syndrome.
Oh, I've seen this so many times.
Right. The CEO launches a massive, urgent initiative in Q1, everyone scrambles. But by Q2, the CEO gets distracted by a new shiny object or a new market trend and quietly shifts priorities. What that teaches the entire organization is that resistance is actually a highly effective strategy.
Just with them out.
Exactly. If they just drag their feet and wait long enough, the executive will get bored, the initiative will die, and they won't have to change at all.
Precisely why direct managers are so vital. While the executive sponsor sets the vision, the direct supervisor is the one who actually builds desire on a daily basis. And the strategies here are very practical. The first step is simply active listening.
Just hearing them out.
Yeah, because often an employee isn't rejecting the grand vision of the company, they are hung up on very specific localized obstacles.
I love the example in the text of the commuting VP. It illustrates this perfectly. You have a vice president who is actively resisting a role change. On paper, this role change is a lateral move, maybe even a slight promotion. It looks like a great opportunity, but the VP is fighting it tooth and nail.
And to leadership, it looks like pure irrational stubbornness or a power play.
Right. But when a senior leader finally sat down, stopped pitching the business case, and just asked the VP what the actual barrier was, the reality was entirely personal. The new role required a longer commute.
Simple as that.
The VP had recently made a solemn commitment to his family that he would not miss his son's after-school activities. The longer commute would break that promise. His resistance had zero to do with the corporate strategy or his capability. It was entirely about his personal situation.
And once that obstacle was dragged into the light, leadership could negotiate a flexible schedule, the obstacle was removed, and his desire to take the role materialized instantly.
But what happens when you can't just tweak a schedule? What happens when a manager is fundamentally ideologically opposed to the new direction of the company, and their resistance is actively poisoning the morale of everyone under them?
That's tough.
It brings up one of the most intense and controversial strategies in the entire book, The Sacrificial Lamb.
It is a harsh term, but it describes a very necessary reality in organizational turnarounds. When a prominent, powerful manager demonstrates persistent, damaging resistance, and all attempts to coach, listen, and negotiate have failed, leadership must remove that person. This doesn't always mean termination. Sometimes it means transferring them to an isolated corner of the business.
Okay, I have to challenge this. You isolate or fire someone to make an example out of them. Isn't that just ruling by fear? How does creating a culture of terror build genuine desire?
It's a delicate balance, and the sources stress this is absolutely a last resort. But consider the alternative cost. If senior leadership tolerates blatant, persistent insubordination from a prominent figure, what message does that send to the employees who are trying to change?
That the change isn't real.
It tells the culture that the new direction is optional. It tells them leadership is weak. Removing a major roadblock sends a shockwave through the company. It shifts the cultural momentum overnight, definitively proving that the organization is fully committed to the new reality.
It really highlights a brilliant distinction the text makes between management and leadership. Managers deliver change, and their behavior is defined by the existing culture. Leaders drive change and they are the ones who define the culture. And defining a new culture sometimes requires making incredibly difficult visible cuts.
Conversely, another high-level leadership strategy for dealing with powerful resistance is what the text calls the pall on the road to Damascus conversion.
Oh, I found this fascinating. Instead of marginalizing your loudest, most articulate critic, you actually target them for conversion. Yes. You spend intensive one-on-one time with your biggest dissenter. You pull them under the tent. Because if you can actually address their concerns, if you can genuinely convince them that the change is necessary, they transform into your most powerful evangelist. A converted skeptic has infinitely more credibility with the rest of the workforce than the CEO does.
That is exactly right.
Okay, let's take a breath and take stock of where we are. We've built the burning platform. We have awareness, we've navigated the personal obstacles, the fear, and the resistance. The employee now actually wants to change. They have desire. Now what?
Now we need knowledge.
Right. Because just because I want to fly a helicopter doesn't mean you should hand me the keys. Which brings us to the third building block of 80 care or knowledge.
Knowledge is the pragmatic how to of the transition. It encompasses the training, the education, and the deep understanding of the new systems, roles, and responsibilities. And crucially, Hyatt points out that knowledge has two distinct phases.
Okay.
Knowing what to do during the messy transition period and knowing how to perform at a high level after the change is fully implemented.
And just like awareness and desire, knowledge is not guaranteed just because you scheduled a training seminar. It is influenced by four distinct factors, right? First is the person's current knowledge base. If you are asking a team to move from an older accounting software to a slightly newer version, the knowledge gap is a small step. If you are asking a team that has used paper ledgers for 20 years to migrate to a cloud-based AI system, the knowledge gap is a massive canyon.
Right. And the second factor is the individual's capability to learn. We all process new information differently at different speeds and through different modalities visual, auditory, kinesthetic.
Definitely.
The third factor is the resources available for training. Do you have the budget, the dedicated time away from normal duties, and the skilled instructors necessary to teach the new skills? And fourth, does a required knowledge even exist yet, or are you building the airplane while flying it?
The sources offer a brilliant everyday example of flawlessly delivering knowledge in a way that hits all the preceding 80 car steps perfectly. It's the Green Hotels Association. We've all encountered this, those little placards sitting on the bathroom towel rack in a hotel.
Oh, it's a masterclass in change management compressed into a four by four inch card.
I always feel a little pang of guilt when I see those.
Which means the card is working. Look how it guides the guest through the model. First, it tackles awareness with the stark fact. Each day, we use millions of gallons of water and tons of detergent to wash towels that have only been used once. Boom! You are instantly aware of the environmental impact. The status quo is broken.
Then it pivots to desire. Decide for yourself. It doesn't mandate behavior. It hands the agency back to the guest, tapping into their intrinsic motivation to be a responsible citizen.
And finally, it delivers knowledge with absolute frictionless clarity. A towel on the rack means I will use it again. A towel on the floor means please exchange.
Three sentences. Awareness, desire, and knowledge, all achieved in five seconds. But what happens when the knowledge gap isn't about where to put a towel, but involves fundamentally rewiring how a person does their job.
Then it gets much harder.
The sources tell a cautionary tale of a network equipment manufacturer that tried to radically change how its sales force operated.
This is a classic organizational failure. The company realized that simply selling hardware boxes was no longer profitable. They needed to pivot to solution-based selling. Instead of selling a router, the salespeople needed to sell the long-term business value and the return on investment that the router would bring to the client's enterprise.
It was a massive cultural shift. And the crazy thing is, they had the first two steps. The salespeople had awareness. They could see their market share dropping. They knew the old way was dying. They had desire their commissions were suffering. They desperately wanted to make more money.
But when they hit the knowledge stage.
They hit a brick wall.
Because selling a tangible piece of hardware based on tech specs is an entirely different universe than sitting down with the chief financial officer and writing a complex business case for a multimillion dollar network upgrade.
The sales team didn't have MBAs. They didn't know basic financial terminology like net present value or internal rate of return. They had never written an ROI analysis in their lives. The company demanded a change without providing the deep foundational knowledge required to execute it.
And the result was catastrophic. A massive exodus of staff. The salespeople didn't quit because they didn't want to work.
This highlights the most common trap I see companies fall into. Knowledge is often the only thing organizations focus on. Think about it. A company decides to roll out a new enterprise resource planning software. What is the very first email that goes out?
Mandatory training sessions scheduled for next Tuesday in conference room B.
Exactly. They completely bypass awareness and desire.
Right. It's exactly like deciding you are going to learn a new language. You go online and buy the thickest, most expensive, comprehensive French textbook available. That textbook represents knowledge. But if you don't know why you are learning French, you don't actually have a trip to Paris planned, so there's no awareness of a need. Or if you simply don't have the intrinsic desire to sit at a desk for two hours every night studying verb conjugations, that expensive textbook is just going to gather dust on your shelf.
It's useless.
You can provide all the knowledge in the world, but without the foundation of awareness and desire, it is utterly useless.
That analogy perfectly illustrates the dependency of the sequence, but let's push your analogy one critical step further. Let's say you do have a trip to Paris planned. You do have a burning desire to connect with the logals, and you sit down and memorize that entire textbook, you know every grammar rule, you get a hundred percent on the written test. Okay. Does that mean when you land at Charles de Gaulleport, you can seamlessly hold a rapid-fire, nuanced conversation with a Parisian taxi driver navigating traffic?
Oh, absolutely not. I would freeze entirely. I would know the vocabulary in my head, but my mouth wouldn't make the sounds, I would panic.
And that panic is the precise gap between knowledge and our fourth building block ability. Knowing how to do something in theory is fundamentally different from possessing the demonstrated capability to actually execute it under pressure.
Here's where it gets really interesting. Because the ability stage is where theory meets reality, and for high performers, it is often a terrifying experience. To gain ability, you have to actually do the new thing, which means you have to endure a period where you are bad at You have to be a novice again. Yes. Ability is defined as the demonstrated execution of the change at the required performance level. And according to the research, it is blocked by five major factors.
What are they?
First and most potent are psychological blocks. Second are physical abilities. Third is intellectual capability. Fourth is the time available to actually practice and develop the skills. And fifth is the availability of resources, like a coach or mentor to guide that practice.
Let's talk about the psychological block, because the sources give a heartbreaking example that perfectly separates knowledge from ability. It's the story of a man named John who desperately wanted to be a volunteer firefighter in his town.
John is the perfect AD care candidate on paper. He had awareness, he read in the local paper that the fire department was desperately short staffed. He had deep desire, he wanted to serve his community and help people.
And he crushed the knowledge phase. He studied relentlessly. He passed his emergency medical technician exams and his written firefighting tests with flying colors. He knew exactly what to do.
But then came his very first call. A severe motor vehicle accident on the highway. John arrives on the scene, steps off the truck, and is confronted with a woman trapped in a car, severely injured with a massive amount of blood.
And John freezes.
He is entirely paralyzed.
He had the knowledge in his head, he knew the steps to apply tourniquet. But when faced with the visceral, chaotic reality of trauma, a deep psychological block triggered. He physically could not make his hands do the work. He lacked the ability to perform under that specific pressure.
It's tragic.
It is. And tragically, he eventually had to resign. It is a stark, heavy reminder that passing the written test does not guarantee performance in the field.
We see a less tragic but equally clear example regarding physical limitations with Vince Lombardi. Widely considered one of the greatest football minds in American history.
But he didn't play in the NFL.
Right. He lacked the physical abilities, the size, the speed, the strength to actually play professional football. Knowing the strategy of how to beat a 300 pound lineman does not give you the physical ability to actually do it.
Okay, let's pull this back to the corporate world because the sources have a great story about how managers constantly misdiagnose this gap. It's the story of the reluctant customer service agent. A call center manager is trying to implement a new cross-selling strategy. You know the drill, while I have you on the line. Would you like to upgrade your package?
We've all heard that. One of her agents is simply not executing the strategy. Her cross-sell numbers are at zero.
So the manager assumes, logically, that it's a knowledge gap. The agent must not know the script. The manager pulls the agent off the floor, puts her through a retraining session, goes over the scripts, practices the rebuttals, she sends her back to the floor. Two weeks later, still zero cross-sales. Now the manager assumes the agent lacks the intellectual ability to learn the system and begins the paperwork to demote or fire her.
But the moment the agent realizes she is about to lose her job, she begs for one final chance. The manager grants it. And suddenly, overnight, this agent becomes the top cross-seller on the entire team.
It's wild. She had the knowledge and the ability all along.
She did. The manager completely misdiagnosed the barrier point. The agent didn't lack knowledge. She didn't lack intellectual ability. She had a deep psychological barrier to feeling pushy or salesy with customers.
She felt it was rude.
Exactly. She lacked the desire to push through that personal discomfort. It was only when the environmental context changed, the severe consequence of losing her job, that her desire shifted, and she finally deployed the ability she had possessed the entire time.
It proves how surgical a leader needs to be. If you treat a desire problem with more knowledge training, you'll just infuriate the employee and waste company money. You have to diagnose exactly where on the 80 care spectrum the individual is stuck.
Right.
And once they finally push through, once they endure the awkwardness of practice and achieve ability, they are finally doing the new thing.
But the journey isn't over. In fact, this is where most organizations fail the hardest.
Right, because how do we make sure they don't just slip back into their comfortable old habits the second the manager leaves the room? That is the final building block, reinforcement.
Reinforcement is the mechanism that locks in the change. It prevents backsliding. But just as importantly, it builds a positive organizational history.
How so?
Well, if employees feel their hard work during a transition was recognized and rewarded, they will be much more likely to exhibit desire the next time a change is introduced.
And effective reinforcement isn't just throwing money at people, right? It relies on four specific factors. First, it must be meaningful to the individual. This requires leaders to actually know their people.
Yeah, you can't just guess.
The research points out that for many customer service employees, the absolute most desired form of recognition isn't a generic pizza party in the break room or an automated company-wide email. It is a specific, face-to-face private thank you from their direct supervisor acknowledging their specific effort.
Yes, personalization is key. Second, the reinforcement must be associated with actual accomplishment. Fake praise is incredibly destructive. If a manager praises an employee before they've actually mastered the new ability, it devalues the recognition entirely and breeds cynicism.
Third, there must be an absence of negative consequences. This is a sneaky one. Let's say an employee bravely adopts the new software system, but their peers, who are resisting the change, actively mock them or complain that the new system is slowing down the team's workflow.
Oh, peer pressure.
Yeah, that peer pressure acts as a massive negative consequence that will quickly kill the employee's new behavior.
And fourth, you need formal accountability systems. Metrics, measurements, and performance reviews that ensure the new behavior is tracked and expected over the long term. The sources look back at the NASA Columbia disaster for this.
Right, going back to where we started, NASA did the hard work. They changed the organizational structure. They brought in new safety protocols.
But the researchers note that while the systemic changes were implemented, individual engineers and managers needed ongoing, relentless personal reinforcement to ensure that those old, dangerous habits, the culture of silencing dissenting opinions or downplaying risk didn't quietly creep back into the daily workflow a year or two down the line when the spotlight faded.
Or to use a much lower sphicks example, let's go back to our hotel towel card. This perfectly illustrates how a lack of reinforcement destroys change.
It's the perfect example.
A guest reads the card, feels the desire to help the environment, possesses the knowledge of what to do, and uses their ability to hang the damp towel on the rack. They have completed the change. But then while they are out, the housekeeping staff comes in, ignores the towel on the rack, takes it away, and replaces it with a fresh, crisp white towel anyway.
What is the psychological effect on the guest?
Total defeat. The change was actively undermined. The guest will look at the fresh towel and think, why did I even bother? The next day, they will just throw the towel on the floor. The new behavior was extinguished immediately.
This raises an important question, right? Why is reinforcement the most neglected step in the entire ADCAR model? The answer lies in the nature of management. Management's attention is inherently forward-looking.
They move on to the next thing.
Exactly. Yeah. By the time a massive project reaches the ability and reinforcement stages, the executive sponsors and the project managers are already looking at next quarter. They declare victory on launch day, cut the ribbon, throw a party, and move on to the next fire. They walk away at the exact moment the employees are most vulnerable to slipping back into old habits.
So we have the complete framework, awareness, desire, knowledge, ability, reinforcement. It is a highly logical diagnostic tool. But to really test its mettle, the sources run this model through a massive stress test.
Sacro level.
They use ADCARR to diagnose failure on a macro societal scale. We are going to look at two real-world case studies from the text. And I want to be explicitly clear for you listening, these are inherently politically charged topics, but we are absolutely not taking a political stance or endorsing any policy here. Right, we're just analyzing. We are strictly acting as scientists, using the objective ADCAR one to five scoring profile detailed by Jeff Hyatt to analyze why these massive shifts are stalled.
The scoring system is the engine of the diagnostic tool. You score an initiative from one to five on each of the five AD care elements. One is the lowest, meaning complete failure or absence, and five is the highest. The critical insight you are looking for is the barrier point.
What's the barrier point?
The barrier point is the very first element in the sequence that scores a three or lower. That is where the entire chain of change breaks down.
Okay, let's apply this. Case study number one, Hubbard R.'s peak, commonly known as peak oil production. The premise here is the theory that global oil production will eventually hit a maximum peak and then enter a terminal decline, creating a massive, devastating gap between supply and demand that could cripple the global economy.
Okay.
The question is: if this is a looming threat, why isn't society transitioning to alternative energy at a much faster, more urgent rate? Let's look at how the AD care scores diagnosed this stall.
Based on the analysis in the text, the AD cars profile for society transitioning away from fossil fuels due to peak oil looks like this. Awareness score is a one, desire is a two, knowledge is a three, ability is a two, reinforcement is a one.
So reading left to right, the very first low score is awareness, sitting at a one that is the barrier point.
Exactly. When Jeff Hyatt surveyed hundreds of business professionals at conferences, he found that less than two percent had any concrete awareness of the specific economic implications of hitting peak oil production.
Wow, that's incredibly low.
Yeah, they might possess a vague generalized sense of environmental concern regarding emissions, but the acute systemic economic threat of supply failure is simply not widely understood. The public cannot transition if the foundational barrier is a total lack of awareness.
But the model is relentless because it reveals a deeper secondary complication. Let's say a massive global education campaign worked perfectly and awareness shot up to a five. Everyone understands the threat. The change would immediately crash into a brick wall at the very next step desire, which is currently sitting at a two.
Because the way I found what's in it for me is simply not acute enough for the average individual yet. Gas prices fluctuate sometimes painfully but they have not caused a fundamental catastrophic shift in daily survival. Human beings are terrible at feeling immediate pain for a theoretical problem that might not peak for another 20 years.
So if governments pour billions of dollars into researching better solar panels or electric vehicle grids, which are attempts to solve the knowledge and ability stages, those efforts won't drive immediate widespread societal adoption if the public lacks the foundational awareness of the threat and the desire to endure the inconvenience of the transition.
You can't fix an awareness problem with an ability solution.
Now let's look at a completely different profile that proves that point. The impending insolvency of the U.S. Social Security and Medicare systems. The mathematical and demographic reality is that the system faces a severe funding crisis in the coming decades. So why does meaningful legislative reform constantly stall?
Let's run the EDK scores from the text. For Social Security reform, awareness actually scores a five. Everyone knows it's an issue, it's debated on the news every single election cycle. But desire scores a two. Knowledge is a three, ability is a four, reinforcement is a three.
Notice the contrast. The sequence starts incredibly strong. Awareness is fully saturated at a five, but the process immediately crashes. The barrier point here is desire sitting at a two.
Right.
Why is desire so low if awareness is so high?
Because the demographics dictate the desire. The demographic group most immediately impacted by any systemic change to social securities, older voters who rely on it, actively desires no change. Their intrinsic motivation is to protect the benefits they have contributed to over a lifetime.
That makes sense. When politicians propose highly complex new financial structures or means testing formulas or privatization plans, what are they doing? They are proposing solutions aimed at knowledge and ability. But those proposals fail to gain traction because they are trying to solve a knowledge problem when the actual roadblock is desire.
And you can take this exact same macro logic and apply it to a stalled project at your own workplace tomorrow morning. If you are leading a new software rollout and morale is plummeting, stop guessing. Ask your team to anonymously score their own personal transition from one to five on A D K A and R.
If the aggregated scores come back and knowledge is a two, you know exactly what to do. You need better, clearer training materials. But if the scores come back and desire is a two, scheduling another PowerPoint training session will just make them angrier. You have to pivot your leadership strategy, go back to the drawing board, and address the WIIFM.
It provides clarity in the chaos.
It does. It feels incredibly satisfying to plot out these numbers, identify the exact bottleneck, and deploy a targeted solution. It feels like a flawless system. But is it perfect? If we pull in Stephen Warlow's critique from our sources, he throws some cold water on this engineering marvel. He suggests that ADACAR, precisely because of its rigid structure, has some fundamental and dangerous blind spots.
Warlow's evaluation is very sharp. He doesn't dismiss ADCAR. He acknowledges it is a fantastic, highly practical management checklist. But he argues that it carries a heavy bias inherited from its origins. Remember, Jeff Hyatt was an engineer. ADCAR is deeply rooted in the philosophy of business process reengineering, or BPR.
Okay, unpack BPR for me. What does that actually mean in practice?
Business process reengineering treats an organization like a giant circuit board. If a process is inefficient, you simply map out a better route, unplug the wires, and reroute them to a more efficient configuration. It is highly logical. It views human change through an engineer's lens. Identify the inefficiency, apply the new steps, achieve the result.
But humans aren't wires. We don't just passively accept being unplugged and rerouted.
Exactly. And Warlow points out three major critiques of this BPR approach. Critique number one is that ADCAR completely fails to distinguish between incremental change and step change.
If I am just upgrading my team from an old version of Excel to a new version of Excel and incremental change, ADCAR seems perfect. It walks me through the logical steps.
Yes, for incremental shifts, it shines. But a step change is a massive existential organizational earthquake, a hostile takeover, a merger of two rival corporate cultures, a complete pivot in a business model that makes entire departments obsolete.
That's a whole different level.
Warlow argues that the sheer magnitude, complexity, and chaotic scope of a massive step change overwhelm the simple, linear five-step checklist of ADCAR.
But I think critique number two is where Warlow really strikes a nerve. He argues that AD Car largely ignores the deep emotional dimension of human change. It relies entirely too heavily on logic. He brings in the work of William Bridges, who makes a profound distinction. Change is external, but transition is internal.
This is a crucial psychological concept. Change is the event that happens to you. The company merges, the factory closes, the new software is installed. That is an external change. Transition, however, is the messy psychological process you experience internally in response to that external event. And transition inevitably requires dealing with loss.
Even if the change is good, you are still losing something. You are letting go of your old identity, your established status as an expert, your comfortable daily routines, maybe even your work friends if your desk is moved.
Warlow connects this internal transition directly to the Kubler Ross grief cycle denial, anger, bargaining, depression, and acceptance. When a massive organizational step change occurs, employees essentially go through a mourning process for the reality that used to exist.
And if you look closely at ADCAR, the jump from awareness, understanding the business need to desire, wanting to participate is where this critique hits the hardest. ADCAR seems to assume that if leadership just communicates the logical business reasons well enough, an employee will logically develop the desire to change.
Which isn't how humans work.
Right. Warlow is essentially saying, wait a minute, you are asking these people to grieve the death of their professional identity, and you think a logical PowerPoint presentation on market share is going to make them desire that loss. Which leads to his third and final critique: micro versus macro. ADCAR is inherently a micro model. It is intensely focused on the individual employee. How does this specific person gain awareness? How does this specific person learn the new skill?
But Warlow argues that senior business leaders can not only operate in the micro, they have to manage the macro level program management. Translating a visionary, high-level corporate strategy into actionable, risk-assessed, synchronized, and budgeted steps for an enterprise of 10,000 people requires a macro framework.
It's just too big for ADCAR.
ADCAR simply doesn't provide the architecture to manage a massive portfolio of change. It only manages the individual nodes within that portfolio.
So, what does this all mean? If ADCAR isn't perfect, how do you use it? Do we throw it out?
Not at all. It means we must synthesize the approaches. Engineers love a clean, predictable system, and ADCAR provides an unparalleled diagnostic checklist to ensure no critical milestone is bypassed. Gives you the what. But psychologists know that human grief, fear, and loss can completely short circuit even the most perfectly designed logical process.
You use ADCAR to structure your approach to figure out exactly where the blockage is occurring, but you must execute those steps with deep emotional intelligence. When an employee's 80-car score shows a complete lack of desire, you don't just view them as a broken wire on a circuit board that needs to be fixed or removed.
No, you have to look deeper.
You recognize that they might not be stubbornly defying the company, they might be actively grieving a loss of competence.
It provides the necessary structure, but leadership must provide the empathy.
We have covered a massive amount of ground today. To distill this entire journey down, the AD car model, awareness, desire, knowledge, ability, and reinforcement is an incredibly powerful lens for dissecting why change stalls out. Whether we are analyzing a global energy crisis, a massive corporate restructuring, or a simple hotel towel policy.
Yeah, it applies everywhere.
It forces us to confront the foundational truth that organizations do not change, only individuals do. But as we learned from the critiques, we have to blend this logical sequential checklist with the deep, messy empathy required to lead complex human beings through the emotional loss that change inevitably brings.
It is the marriage of engineering precision and psychological grace.
I want to leave you with a final challenge. Take a moment today and pick one major change you are actively struggling to make in your own personal life right now. Maybe it's a fitness school you keep abandoning, a pivot in your career you are afraid to make, or trying to stick to a new financial budget.
Be honest with yourself.
Be brutally honest with yourself and score your own progress from one to five on A, D, K, A, and R. Find your exact personal barrier point. Are you failing because you genuinely don't know how to do it? Is it just a knowledge gap that a book or a coach could fix? Or if you look really closely at that diagnostic x-ray, are you failing? Because deep down, despite knowing all the logical facts and the benefits, you haven't actually made the emotional choice that you want to. Thank you so much for joining us on this deep dive. We hope this framework helps you navigate the messy, murky waters of your next big transition.