Imagine you've done everything you can to design routine work around limited attention. You've simplified unnecessary decisions. Made important information easier to see. Reduced distractions where attention matters. Built stronger protections around critical steps.
Something will still change.
A piece of equipment breaks down. A crew member is absent. The weather changes. Information turns out to be incomplete. A contractor does something unexpected. The plan doesn't quite fit what people find in the field.
No organization can anticipate every condition employees will encounter. At some point, people have to recognize that something is different. And that's harder than it sounds.
You Have to Notice the Change Before You Can Respond to It
Experienced employees are often very good at solving problems once they recognize them. They know the equipment. They understand the work. They've seen things go wrong before. They have years of experience to draw from when deciding what to do next.
But all of that expertise depends on something happening first:
They have to recognize that the situation requires their attention.
That's where the Productivity–Awareness Paradox comes into play. As work becomes familiar, more of it can be performed through automatic execution. The employee isn't consciously evaluating every step, decision, or cue because they don't need to. That's what allows experienced people to work efficiently.
The challenge arises when something changes. The familiar pattern may no longer fit the situation, but because much of the work is being performed automatically, the difference may not immediately rise into conscious awareness. Before employees can question, communicate, decide, or adapt, they have to reconnect with what's actually happening long enough to recognize the difference.
That's where structural design reaches its limits. Some variability will always require people themselves to recognize what's changed and respond.
That brings us to the second organizational imperative: develop employees' ability to recognize and respond to changing conditions. I think of that process simply as....
Reconnect. Notice. Respond.
Reconnect. Interrupt automatic execution long enough to consciously engage with what's happening now.
Notice. Does reality still match the mental picture guiding the work? Is everything unfolding as expected? Has something changed? If everything still fits, automatic execution can continue. If something doesn't fit, the employee has a reason to engage more deliberately.
Respond. Ask a question, verify information, communicate a concern, adjust the plan, stop the work, or take whatever action the situation requires.
Safer routine work starts with recognizing change, but recognition depends on re-engagement. If people never reconnect with current conditions, they may never recognize that their automatic response no longer fits. Once they recognize the discrepancy, their experience becomes an important resource. They can bring their knowledge and judgment to deciding how to respond.
The question for organizations is how to make that process more reliable.
That's where specific behaviors come in.
“Be More Aware” Isn't a Behavior
Organizations recognize the importance of employees noticing and responding to the work and conditions around them. That's why we tell people to:
* Maintain situational awareness.
* Think critically.
* Communicate effectively.
* Exercise good judgment.
All of those things matter. But none of them tells someone what to actually do. You can't observe someone “being situationally aware,” but you can observe them deliberately scanning the environment. You can't observe someone “thinking critically,” but you can observe them asking a question that challenges an assumption. You can't observe “effective communication,” but you can observe someone verifying critical information with another person before acting on it.
Situational awareness, critical thinking, and effective communication are outcomes. If we want those outcomes to occur reliably, we need to identify the specific behaviors that help create them.
Instead of asking: How do we get people to be more aware?
Ask: What specific actions will help people reconnect with current conditions, recognize when something has changed, and respond deliberately?
Building Anti-Habit Habits
I sometimes call the behaviors that accomplish these things anti-habit habits.
The name sounds contradictory because it is. We're not trying to eliminate the habits that allow experienced people to work efficiently. Instead, we can intentionally build behaviors that periodically check whether those existing habits still fit the situation.
Over time, those behaviors can become habits themselves.
Many already exist in the workforce. Experienced employees often develop their own ways of reconnecting with the work. Someone might have a habit of deliberately scanning the environment at a particular point in the task. A crew might routinely ask a question that challenges an assumption. Two employees exchanging critical information might automatically verify that they have the same understanding before either acts.
The opportunity may be less about inventing a new behavior than identifying what's already working and making it more deliberate and reliable.
What Makes a Behavior Useful?
The answer isn't simply to add more behaviors. A new safety behavior can easily become another checklist item, requirement, or cognitive demand layered onto an already complicated job.
Useful behaviors tend to be specific, observable, and simple enough to repeat during everyday work. Most importantly, they should help someone reconnect, notice, or respond, rather than simply create another action to complete.
What that looks like depends on the outcome you're trying to create.
If the goal is situational awareness, a deliberate scan such as Up, Down, Around can redirect attention from the familiar task to what's happening in the surrounding environment.
If the goal is critical thinking, asking a question such as “What's different today?” can challenge the assumption that today's work will unfold exactly like yesterday's.
If the goal is communication, practices such as two-way or three-way communication can expose differences in understanding before someone acts on critical information.
The specific tool isn't the point. Ask: What does someone need to notice, question, communicate, or verify? What specific action will help them do that?
That's the mindset shift: move from telling people to be aware, think critically, and communicate effectively to identifying what you actually want them to do to create those outcomes.
Structural and Behavioral Support Work Together
Developing employees' ability to recognize and respond to changing conditions isn't a substitute for good work design.
First, design the work to make the best use of human attention. Then develop people's ability to recognize and respond where human judgment remains essential.
Structural support changes what the work demands from people's attention. Behavioral support gives people specific ways to reconnect with current conditions, recognize change, and respond deliberately when the work itself can't provide the answer.
We need both.
Coming Up Next
Identifying and teaching the right behavior is only the beginning. Employees can learn it, practice it, and leave training knowing exactly what to do. But when they return to work, that new behavior has to compete with years of established routines.
And the old behavior has one enormous advantage: It's already routine.
The real test isn't whether employees can demonstrate the new behavior in training. It's whether they still use it weeks later when no one is reminding them to. That brings us to the third organizational imperative: Embed those behaviors into everyday work.
That's what we'll tackle next.
Next in the series: How New Behaviors Become Routine