Watch the recording of the webinar:
View and download the slides:
Alternative Slides Download (PDF)
Listen to the recording via our podcast:
Most improvement efforts don't fail because the solution was wrong. They fail because people didn't change their behavior. Leaders show the data, build the business case, explain the savings, and then watch the rollout flatten under polite resistance, fatigue, or quiet disengagement.
The missing piece is almost always psychology. In this session, Tracy O'Rourke -- 25 years in process improvement, Lean Six Sigma instructor at UC San Diego, co-host of the Just-In-Time Cafe podcast -- walks through the change psychology she returns to over and over because it actually works on real teams. She also makes the case that process gemba walks are one of the most underused behavior-change tools in the lean toolkit.
Tracy starts with an analogy from social psychologist Jonathan Haidt's The Happiness Hypothesis, made famous by Chip and Dan Heath in Switch. Everyone's brain has two parts that need to be addressed in any change effort.
The rider is the rational, analytical part. It runs the numbers, weighs the options, and knows what the right thing to do is. The elephant is the emotional, motivational part. It's where the energy actually comes from.
The rider sits on the elephant's back holding the reins. As long as the elephant is willing, the rider can steer. But when the rider and the six-ton elephant disagree about which direction to go, the rider loses every time.
This is why most change efforts stall. We've all experienced the rider losing to the elephant: knowing we should go to the gym and choosing the couch, knowing we should eat the salad and ordering the cookie, knowing we should start that project and procrastinating instead. The rider knows. The elephant decides.
In organizational change, leaders almost always speak only to the rider. They build the business case, present the dollar savings, explain the strategy. None of that motivates the elephant. The elephant needs to feel something.
Tracy tells a story from a project at a ship repair company. Project managers each had their own version of a checkbook for tracking costs on their ships -- 20 different formats, all idiosyncratic. The team built a standardized digital checkbook and rolled it out.
Predictable response: nobody wanted to use it. "I've been doing it this way for 20 years." "I like my version." "Why are you changing this?"
What turned the rollout around wasn't a stronger argument. It was reminding the project managers of the pain they had asked the team to solve in the first place. When a PM went on vacation and a colleague had to cover their ship, the colleague would spend hours figuring out a checkbook they'd never seen. New PMs onboarding to the role had to learn five or six different versions from five or six different people. The pain was already there, every day. They just hadn't connected it to the solution being rolled out.
Once the team surfaced the pain explicitly -- not as a sales pitch, but as a reminder of the original problem -- adoption moved. Now everyone uses the standardized checkbook. The change argument was the same the whole time. What changed was that the elephant got engaged.
There's a misconception baked into how most leaders approach change. We assume the sequence is: think, analyze, change. Read the report, weigh the options, make the new decision.
The actual sequence is: see, feel, change.
Seeing and feeling are how the elephant gets activated. Tracy walks through a campaign that illustrates this directly.
Two health researchers wanted Americans to switch from whole milk to 1% or skim, since whole milk is the largest source of saturated fat in the American diet. The rider-friendly version of the message was a label comparison: 70 calories versus 0, 25% saturated fat versus 0%. Compelling on a spreadsheet. Not motivating in a kitchen.
The version that actually moved behavior: one glass of whole milk has the same fat as five slices of bacon. That's a sensory image. You can see it. You can feel it. After a six-month campaign built around that single reframing, market share for low-fat milk in the test market moved from 18% to 41%, and held at 35%.
Same facts. Different framing. The reframing reached the elephant.
The Switch framework has three components for getting the emotional brain engaged. Tracy works through each one with practical examples.
Find the feeling. Make the change emotional, not just logical. In healthcare, this often happens naturally -- improving a process saves lives, and that's a clear emotional anchor. In other domains it takes more work. Tracy describes a Cub Scouts volunteer day at the San Diego food bank. The kids spent four hours covered in carrot peelings, doing tedious prep work. At the end, the staff said: "You prepped 30 pounds of carrots, which will feed 50 families." The room shifted. Suddenly the work wasn't carrots -- it was 50 families. Tracy's note: she wishes the food bank had said that at the beginning. The motivation is more useful in the moment than in retrospect.
Shrink the change. Make the first step small enough that the elephant doesn't get spooked. Researchers ran a car wash loyalty card experiment. One group got an 8-stamp card. The other group got a 10-stamp card with two stamps already filled in -- still 8 stamps to go, but visually they were already on their way. Six months later, 19% of the eight-stamp group had earned a free car wash. 34% of the head-start group had, and they finished faster. Same actual effort. Different perception of progress. Dave Ramsey's debt snowball method works on the same principle, even though it violates standard financial advice -- pay off the smallest debt first, get the win, build momentum, instead of attacking the highest-interest balance and feeling no progress for a year.
Grow your people. People make decisions in two ways. The consequences model weighs costs and benefits. The identity model asks: who am I, and what would someone like me do in this situation? When change aligns with identity, it lands. When it conflicts with identity, it almost can't land regardless of how strong the business case is. For a public-sector team, framing process improvement as "we are good stewards of taxpayer dollars" hits identity directly. For a manufacturing team, framing safety improvement as "we are people who go home to our families every night" does the same. The frame isn't manipulation -- it's connecting the change to who people already believe themselves to be.
A common shortcut leaders reach for is the burning platform. "If we don't do this, we lose the market in 18 months." That can work. Sometimes it has to work, because the platform actually is burning.
But fear as a primary, repeated motivator builds toxic culture. Teams that operate in constant burning-platform mode burn out. The signal stops working because everything feels like a crisis, and nothing actually changes faster as a result.
Tracy's preference, and the position the Switch framework takes, is to lead with positive emotion: pain reduction, pride in the work, identity, progress, meaning. Use fear sparingly, and only when the threat is real and immediate. The default tool should be finding the feeling that already exists in the work and naming it.
Most lean leaders think of gemba walks as a leadership routine -- get out of the conference room, see the work, ask questions. Tracy adds a layer. A process gemba walk -- walking an end-to-end process with the people who actually live in each step -- is one of the most powerful behavior-change tools available, because it produces the see-feel-change sequence directly.
The setup matters. A process walk is not an audit. It's not a gotcha. The goal is to build profound knowledge of how the process actually works and to surface the pain inside it. The ground rule Tracy enforces: talk about the process and your own pain in it. Don't talk about what other departments need to do differently. That's their job to figure out -- your job is to show what's actually happening at your step.
What happens during these walks is consistent. Two departments who didn't get along walk the process together. One team sees, often for the first time, what the other team is actually dealing with. Tracy describes a moment where one department had been frustrated with another for years, watched them walk through their part of the process, and said: "I'm sorry. That's worse than mine. I had no idea."
That moment is the elephant getting engaged. Empathy lands. Resistance softens. Now the conversation isn't about who's right -- it's about how to fix the process. Tracy's framing: in any genuinely bad process, the biggest victims are the people who work inside it. Why blame them? They're the ones who deal with it every day.
Transactional processes need this even more than physical ones. You can walk into a factory and see a bottleneck. You can't walk into a room and see a broken employee onboarding process or a tangled approval workflow. The pain is invisible until you walk it. That invisibility is exactly why these processes resist change -- there's no shared picture of how bad it actually is. The walk creates the picture.
There are four versions of every process: what people think it is, what it truly is, what it should be, and what it could be. Most teams operate on what they think it is. The walk forces a confrontation with what it truly is, which is almost always the precondition for genuine improvement.
Tracy uses a few quick examples to show the same principle in everyday life.
A school speed limit sign that says "25 MPH" speaks to the rider -- compliance with a number. A sign with two figures of children speaks to the elephant -- there are kids here. A sign that says "Drive like your kids live here" goes further still -- the connection is to your own family, not someone else's.
A construction site sign that says "Wear PPE" is logical. A sign that says "Nothing you do today is as important as going home to your family tonight" makes the same point in a way that gets remembered. The information is similar. The emotional connection is not.
The same principle applies inside a process improvement program. "We need to reduce cycle time by 12%" is a rider message. "We need to stop making nurses stay 90 minutes past shift change to finish documentation" is an elephant message. They might be the same project. The framing determines whether the team gets behind it.
A few things the platform does that connect to what Tracy is describing. KaiNexus makes process pain visible by tracking improvement opportunities, ideas, and the impact of changes over time -- so the case for any specific change is grounded in real data and real stories rather than abstraction. It makes progress visible at the team level, which is the shrinking-the-change principle in action; people can see the small wins accumulate instead of waiting for a single big result. And it spreads improvements across the organization, so a process pain that one team has solved becomes visible to other teams dealing with the same pain.
If you have improvement work happening but the behavior change isn't sticking, the platform won't fix that on its own -- that's a leadership and culture question. What it does is remove the friction that lets good changes quietly fade after rollout.
Tracy O'Rourke is a Lean Six Sigma Master Black Belt and co-author of The Problem Solver's Toolkit (second edition available now). She is co-founder and co-host of the Just-In-Time Cafe podcast, a Lean Six Sigma instructor at UC San Diego, and a process improvement zealot. Over more than 25 years she has trained over 5,000 people, mentored thousands of problem solvers through root cause analysis projects, and consulted across cultural change, leadership development, strategic alignment, and process improvement. She is also known for her parody music videos, including Baby Got Tools, which bring humor and joy into the practice of process improvement.
Why do people resist change even when the logic is sound?
Logic speaks to the rational part of the brain (the rider in Jonathan Haidt's analogy). Motivation lives in the emotional part (the elephant). When the two disagree, the elephant wins. Most change efforts fail because they make a strong case to the rider while leaving the elephant unmoved. To change behavior, leaders need to make the change emotionally meaningful, not just rationally correct.
What is the rider and elephant model?
It's a metaphor for how human motivation works, popularized by Chip and Dan Heath in Switch. The rider is the analytical, rational mind. The elephant is the emotional, motivational mind. The rider can steer when the elephant cooperates, but when they disagree, the elephant's size and strength wins. Effective change addresses both: rational case for the rider, emotional connection for the elephant.
How do you motivate change without using fear?
Fear works in the short term but builds toxic culture if it's the primary lever. Better motivators include reducing pain in people's daily work, connecting the change to a meaningful outcome (saving lives, serving customers better, going home on time), making progress visible, and aligning the change with people's identity. The Switch framework uses three moves: find the feeling, shrink the change, and grow your people.
What is a process gemba walk?
A process gemba walk is an end-to-end walk of a process with the people who work in each step. The goal is to build profound knowledge of how the process actually operates and to surface the pain inside it. It's not an audit and not a gotcha exercise. The ground rule is that participants describe their own pain in the process, not what other departments should do differently.
How does a process walk help with behavior change?
Walking the process produces the see-feel-change sequence that motivates the elephant. People often discover that other departments have it worse than they realized, which builds empathy and softens resistance. The walk also surfaces invisible pain in transactional processes (HR, finance, IT) that can't be seen the way you can see a manufacturing bottleneck. Once the pain is visible to everyone who touches the process, the conversation shifts from blame to redesign.
How small should the first step of a change be?
Small enough that it doesn't spook the elephant. The Switch framework calls this shrinking the change. The car wash loyalty card experiment showed that giving customers a 10-stamp card with two stamps already filled in (same effort required) doubled completion rates compared to a blank 8-stamp card. People are far more likely to act when they feel they've already started than when they're standing at the beginning of a long road.
How does the identity model work for change?
People make decisions partly through a consequences model (cost vs. benefit) and partly through an identity model (who am I, and what would someone like me do here?). When a change aligns with identity, adoption is far easier. Framing process improvement in a public-sector team as "we are good stewards of taxpayer dollars" or framing safety in a manufacturing team as "we are people who go home to our families" connects the change to identity rather than to compliance.
.svg)
Copyright © 2026
Privacy Policy