Imagine you've identified exactly what you want employees to do.
The behavior is specific. It's observable. It's simple enough to use during everyday work. It helps people reconnect with current conditions, recognize when something has changed, and respond deliberately. You teach employees why it matters. They learn how to do it. They practice. They demonstrate that they can perform it correctly.
Then they go back to work. Now comes the harder part: Will the new behavior become part of how they actually work?
Because the behavior isn't entering a blank slate. It's competing with routines employees have performed hundreds or thousands of times before. And the old behavior has one enormous advantage: It's already routine.
That's why the third organizational imperative is to embed those behaviors into everyday work.
Learning a Behavior Isn't the Same as Adopting It
Training has an important job. Employees need to understand why a behavior matters, what it looks like, when to use it, and how to perform it. They need opportunities to practice until they can use it correctly and confidently.
But capability is only the beginning.
When employees return to work, they return to the same environment that shaped their existing routines. The same equipment. The same processes. The same coworkers. The same supervisors. The same pressures and competing priorities.
One training experience has to compete with all of that. That's why the real test of behavior change isn't whether someone can demonstrate a behavior during training. It's whether they use it three weeks later when no one is reminding them to.
Getting from something employees learned to something that becomes part of how they work requires three different questions:
1. Can they do it?
2. Are they doing it?
3. What will keep them doing it?
Can They Do It?
Before a behavior can become routine, people have to be able to perform it. That requires more than telling employees what you want them to do.
* If you want people to deliberately scan their environment, they need to understand what they're looking for and how to perform the scan.
* If you want people to challenge assumptions, they need questions they can actually use.
* If you want people to verify critical information, they need to know what good verification sounds like.
They also need opportunities to practice. Knowing about a behavior isn't the same as being able to use it when the situation calls for it. Training should give people the opportunity to try the behavior, receive feedback, and build enough skill and confidence to use it on the job.
But being able to do something doesn't mean people will actually do it. That's the next challenge.
Are They Doing It?
For a new behavior to become routine, people need to know when to use it. And they need enough opportunities to use it for the behavior itself to become familiar.
Start with the cue.
Teaching someone a new technique but leaving them responsible for remembering when to use it creates another demand on the very resource we're trying to protect: attention.
So don't just teach the behavior. Connect it to something recognizable. That might be before a critical step. After an interruption. During a handoff. When the crew changes. When conditions don't match the plan. At a natural transition in the work.
The more clearly people can connect "when this happens" with "do this", the less the behavior depends on someone remembering it at exactly the right moment. Ideally, that cue is connected to something that already happens in the work.
* Can the behavior become part of an existing job brief?
* Can it happen at a handoff that's already taking place?
* Can an existing transition in the work become the cue?
The easier it is to integrate the behavior into what people are already doing, the less it feels like an additional safety activity sitting on top of the work. That integration also creates something essential: Repetition.
Every time someone encounters an opportunity to use the new behavior, they either get another repetition or fall back on the more familiar response. Over time, those repetitions matter. Routine work is constantly reinforcing what the familiar response should be.
The new behavior isn't competing with ignorance. It's competing with something people already know extremely well.
Your new behavior may have one repetition. The old habit may have five thousand.
That's why explanation and training rarely change an established routine. People need opportunities to use the new behavior again and again until it becomes the familiar response.
What Will Keep Them Doing It?
Early use is important. But new behaviors are fragile. For a while, the old routine is still easier and more familiar. What happens after training can either strengthen the new behavior or allow the old one to take back over.
That's where leaders and supervisors matter.
* What do they ask about?
* What do they model themselves?
* What do they coach?
* What happens when someone actually uses the new behavior?
If leaders consistently reinforce the behavior, they send an important message: this isn't simply something employees did during training. It's part of how we expect the work to happen.
And reinforcement doesn't need to be complicated.
* If you're asking employees to deliberately scan the environment, a supervisor can ask: What did you notice?
* If crews are supposed to discuss what's different today: What was different?
* If employees are expected to question assumptions: What assumption did we make here?
Those questions keep the behavior visible and give people another opportunity to practice the thinking behind it.
But reinforcement isn't only about what leaders say and do. The surrounding system also sends signals about which behaviors are actually expected and practical.
Organizations sometimes train one behavior while unintentionally reinforcing another. We tell people to pause when something doesn't look right while emphasizing the impending deadline. We ask employees to verify information but make the verification process cumbersome. We encourage people to raise concerns but respond impatiently when they do.
When that happens, the new behavior isn't only competing with an old habit. It's competing with the environment. So ask:
What in the surrounding system will make this behavior easier or harder to sustain?
The answer might mean changing the work itself, modifying a procedure, changing a supervisor's response, clarifying a production expectation, or providing a better tool. If the behavior matters, the surrounding environment should make it easier, not harder, to use.
When the New Behavior Becomes Routine
Eventually, something important begins to change. The employee no longer has to consciously remind themselves to use the new behavior. The deliberate scan happens naturally at that point in the task. The question gets asked. The critical information gets verified. The pause becomes part of the way the work happens.
Re-engagement itself becomes routine.
And that's what we've been working toward. In the previous article, I described the process of engaging with changing conditions as:
Reconnect → Notice → Respond
First, employees periodically reconnect with what's actually happening around them.
That gives them an opportunity to notice whether reality still matches the expectations guiding their work.
If everything fits, automatic execution can continue doing exactly what it's good at.
If something doesn't fit, they've recognized a reason to respond more deliberately: ask a question, verify information, communicate a concern, adjust the plan, stop the work, or take whatever action the situation requires.
When the behaviors that initiate that process become part of everyday work, employees don't have to consciously monitor every aspect of familiar work all day long. Instead, they have reliable ways to periodically come out of automatic execution and check whether the familiar pattern still fits.
That's a much more realistic goal than asking people to “pay more attention.”
Making Routine Work Safer
We started this series with a simple observation: routine work isn't necessarily as simple or predictable as it feels. Experience makes people faster, more skilled, and more efficient. It also allows more of familiar work to happen automatically.
We shouldn't try to eliminate that. We should design around it.
1. Design work to make the best use of human attention.
2. Develop employees' ability to recognize and respond to changing conditions.
3. Embed those behaviors into everyday work.
The goal isn't a workforce that consciously thinks through every familiar action. It's work designed so people can benefit from automatic execution and reliably re-engage when the situation requires something different.
That's the balance we've been trying to create throughout this series. The brain's ability to automate familiar behavior created the challenge we started with. But that same ability can also become part of the solution.
We can make safer behaviors routine.
Explore the full series: Making Routine Work Safer