When Standard Work Isn’t Followed, Your Reaction Is the Real Standard

The Sign on the Wall Was a Confession

Two staff members are repositioning a patient by hand. The lift assist that's supposed to be used for this — the equipment the hospital bought specifically so nobody does it this way — is sitting in a closet on a different floor.

If you lead this unit and you walk in on that, your first reaction might be frustration. You bought the equipment. You wrote the standard. And here are two people ignoring both, right in front of you.

Before acting on that reaction, it's worth asking a different question.

Here's what's actually at stake in that room. A patient being lifted by hand can be dropped. Can fall. Manual repositioning is also one of the fastest ways for a nurse or an aide to injure their back — and back injuries are how people leave this profession, not how they take a sick day. The lift assist exists to protect both people in that room at once. So this isn't a tidy little rule violation. Two human beings are exposed to real injury because the safer tool is a floor away.

Which makes the frustration understandable. The stakes are high, so the urge to correct, hard and now, feels not just acceptable but responsible.

It's still wrong. And the reason it's wrong is worth a closer look.

Nobody Lifts a Patient by Hand Because They Don't Care

Ask yourself why two people who presumably want to keep their backs intact would skip the equipment designed to save them. The answer is almost never that they don't care. It's that the lift assist is on another floor, it takes time they don't have, and the patient needs to move now.

The deviation isn't a motivation problem. It's a barrier problem. The standard asked people to walk to a different floor in the middle of patient care, and under real conditions, that standard loses. Every time.

This is the part the flare can't see. From where you're standing, it looks like staff who won't follow the rule. From where they're standing, it's staff who can't follow it without abandoning a patient mid-task. Same scene, two completely different stories, and only one of them is true. You can't tell which by looking. You can only tell by asking — and by asking in a way that makes the honest answer safe to say out loud.

What the Berating Sign Really Says

In this actual case, from Lean Hospitals, managers reacted the way the flare wants you to react. They hung a sign on the wall berating staff for not using the equipment.

I've come to read a sign like that as a confession.

It confesses that a leader saw two people at risk of getting hurt and decided the problem was their attitude. It confesses that the storage location — the thing the leader actually controls — went unexamined. It confesses that the cheapest possible response, a piece of paper, got chosen over the one that would have worked. The sign doesn't fix the barrier. It just relocates the blame onto the people the barrier is hurting.

A “thou shalt” sign (or something less stone tablety) is usually a symptom dressed up as a solution. It's the management equivalent of yelling at a check-engine light.

What finally worked in that hospital wasn't a sign. The unit used 5S to clear out a utility room of broken walkers and a surplus of old commodes, freed up space, and brought the lift assist onto the floor where the work happens. Once the equipment was a few steps away instead of a few floors away, people used it. The deviation didn't need to be scolded out of existence. It needed the barrier removed.

Make it easy for people to do the right thing.

Your Reaction Is a Teaching Event

Here's the thing leaders underrate. Whatever you do in that moment, you're teaching. Not with your stated values, with your reaction. Every staff member watching is running a quiet experiment on you, and the question they're answering is simple: what happens to the person who lets the boss see a problem?

They're better at reading your results than you are at controlling them. So it's worth being honest about what each reaction actually teaches.

Blame — “Who didn't use the lift assist?” — teaches that deviations are dangerous to be associated with. You might get a name and an apology. What you won't get is the next deviation, because it now happens when you're not on the floor. You feel like you handled it. You've actually blinded yourself, and traded a visible problem you could have fixed for an invisible one you can't.

Enforcement is subtler, and more common among leaders who think they're doing it right. The tone says “I'm not angry, but you will follow the standard.” No shaming, just firm correction. It teaches that the goal is the checkmark, not the truth. People comply when watched and revert when not, and the gap between the two goes invisible. This is how a leader ends up with beautiful audit results and no idea what's happening. I've seen the version where a nursing assistant came by at the end of the shift to fill in the missing checkmarks on the tracking sheet, because the manager clearly wanted to see boxes checked more than they wanted to know what happened on the floor.

Fixing it yourself on the spot — “It's on another floor? I'll have facilities move it” — comes from a good place and still costs you something. Over time it teaches that problems are the leader's to solve, not the team's to surface and work. People bring you problems and wait, rather than investigate their own barriers. You become the bottleneck, and the capability you needed people to build never gets exercised.

Silence teaches the loudest. Walk past two people lifting a patient by hand and say nothing, and everyone who saw it learns the standard is decorative and the safety reasoning behind it doesn't really matter. Saying nothing is a reaction. People read it.

Curiosity — “Walk me through what's happening here, why isn't the lift assist getting used?” — teaches that it's safe to show you reality, and that surfacing a barrier brings help instead of heat. The result is more problems exposed, earlier, while they're still small and cheap to fix.

The Counterintuitive Part

That last one has a consequence that trips up almost every leader who manages by dashboard. When you react with curiosity, the number of visible problems goes up. At first it looks like things are getting worse. They're not. You're just finally seeing what was always there.

I think of a chart Dr. Yasuda showed me at a hospital near Toyota City. She was smiling, and what she was smiling about was a steep increase in incident reports. That sounds backward until you understand what she was actually measuring. They were closing the gap between incidents that happened and incidents that got reported. The events weren't increasing. The reporting was, because people finally felt safe enough to report.

A hospital system in the Pacific Northwest showed the same pattern after rolling out a “safety stop” process modeled on the andon cord. Reported concerns, safety stops, and root cause analyses went up. Over the same period, serious safety events went down. More reports, fewer actual events. The two lines move in opposite directions, which is exactly why a leader watching only the reports could draw precisely the wrong conclusion.

So a unit that suddenly reports more near-misses after a leadership change usually doesn't have more near-misses. It has a leader people have decided to trust. And a unit where problem reports quietly dry up isn't getting better. It's going silent. A drop in reported problems gets celebrated all the time. Often it's the sound of people deciding it isn't worth it.

That word — worth — points at something Ethan Burris's research surfaces. We assume people stay quiet out of fear of retaliation. Fear is real, but Burris finds the futility factor is even more common: the belief that speaking up won't change anything. The fixer reaction feeds fear's quieter cousin in its own way, but futility mostly comes from the suggestion that vanished into a spreadsheet and was never heard from again. Which is why the reaction doesn't end with the conversation.

The Follow-Up Is Part of the Reaction

If you ask why and learn the standard is wrong, the standard has to change, and the person who told you should see it change. If you learn there's a barrier, moving the lift assist is yours to do, or yours to explain why it can't happen yet. Curiosity without follow-through is just a gentler way of getting compliance, and people figure that out fast. They'll answer your question once. Whether they answer the next one depends on what you did with the first.

There's also a brutal asymmetry here that's worth naming. A leader doesn't get judged on their average reaction. They get judged on their worst recent one, because people are doing threat assessment, and threat assessment weights the downside. One blame reaction can undo months of curious ones. This is why “I'm usually pretty good about this” offers no protection. The person deciding whether to tell you about the next near-miss isn't averaging your behavior. They're remembering the time someone got their head taken off, and deciding not to be next.

The Question That Reveals Where You're Really Looking

The lab at Children's Health in Dallas posted five questions to ask when standard work isn't being followed:

• Is the standard work appropriate?
• Are the right tools, equipment, and materials in place and of appropriate quality?
• Is the person following the steps and sequence?
• Has the person had adequate practice in the operation?
• Does the system allow the person to meet the standard?

Notice where four of those five questions point. Not at the person. At the system the leader is responsible for. Only one asks whether the individual is following the steps, and it sits surrounded by questions about whether the conditions made that possible in the first place. That ratio is the whole argument. Your instinct points one direction — at the person — and the useful questions point almost entirely the other way.

If the person isn't following the steps and sequence — ask why — and see the other four questions.

One more reason to ask before you correct: Sometimes the person working off-standard has found a better way. Standardized work is the current best-known method, not a permanent one. It's meant to be improved by the people doing the work. So a deviation can be a problem, or it can be a kaizen improvement nobody's noticed yet. React to every deviation with correction and you stamp out the improvements alongside the genuine errors, and you never learn which ones you killed.

So the next time you walk a unit and catch that flare — the one that says go get some compliance — it's worth a half-second pause to ask what you're about to do. Correct a person, or examine a system. Read the sign, or write one.

Whose standard is the deviation really pointing to. Theirs, or yours.