Chronic Unease in Safety Leadership Why Staying Slightly Uncomfortable Prevents Risk
The strongest safety leaders do not relax just because the dashboard is green. They know that major accidents often grow inside ordinary operations, quiet workarounds, and repeated success.
That mindset has a name: chronic unease. It is a disciplined sense that risk is never fully gone. It is common in high-risk industries such as aviation, oil and gas, mining, construction, chemicals, rail, utilities, health care, and maritime operations.
Chronic unease does not mean panic. It does not mean stopping work at every unknown. It means leaders stay alert enough to ask better questions before small problems become system failures.
What Chronic Unease Means In High-Risk Work
Chronic unease is a state of informed discomfort. It is the habit of asking, “What are we missing?” even when production is on target, injury rates are low, and audits look clean.
The concept is closely linked to high reliability organizations. Researchers such as Karl Weick and Kathleen Sutcliffe have described high reliability organizations as especially alert to failure, weak signals, and operational complexity. These organizations do not treat success as proof that controls are strong. They treat success as something to examine.
In simple terms, chronic unease means leaders believe three things at once:
Serious risk can exist without obvious warning.
People often adapt around weak systems to get work done.
Past success does not prove future safety.
That last point matters. Many catastrophic events were preceded by periods of normal performance. The work continued. Targets were met. The system appeared stable.
The 2005 BP Texas City refinery explosion is a widely studied example. The U.S. Chemical Safety and Hazard Investigation Board found deep problems in safety management, process safety culture, and warning signs that were not acted on with enough urgency. Fifteen people died and many more were injured. The event is often cited because it showed how low personal injury rates can hide major process safety risk.
The 2003 Space Shuttle Columbia disaster offers another lesson. Foam had struck the shuttle before, and the organization had come to treat it as a maintenance problem rather than a mission-ending threat. The Columbia Accident Investigation Board described cultural and organizational factors, not just technical ones. Success had normalized a hazard.
Chronic unease pushes against that drift.
It asks leaders to look at:
Near misses that did not cause harm.
Controls that work only because skilled workers compensate.
Repeated exceptions that have become normal.
Silence from teams doing difficult work.
Good results that lack a clear explanation.
Equipment that “always does that.”
Procedures that no longer match the work.
These are not proof of disaster. They are proof that leaders should investigate.
Why Healthy Skepticism Improves Risk Management
Healthy skepticism is not cynicism. Cynicism assumes people do not care. Skepticism assumes the system may be giving an incomplete picture.
Safety leaders need skepticism because risk information is filtered before it reaches them. Reports get summarized. Metrics get averaged. Bad news gets softened. People often solve problems in the field without documenting the workaround. By the time information reaches senior leaders, the edges can be gone.
A skeptical leader does not reject the data. They test it.
If a site reports no serious incidents for a long period, the wrong response is automatic celebration. A better response is, “What explains the result?”
That question can lead to useful follow-ups:
Are people reporting near misses?
Are supervisors closing actions on time?
Are critical controls verified in the field?
Are contractors included in the data?
Are low numbers consistent across shifts?
Are workers confident that reporting will not create blame?
Have production pressures changed behavior?
The point is not to discredit success. The point is to understand whether success is strong or fragile.
James Reason’s Swiss cheese model remains useful here. Harm occurs when several layers of defense have holes that line up. A good month does not mean the holes disappeared. It may only mean they did not align.
Healthy skepticism keeps leaders from confusing luck with control.
It also helps them challenge three common traps.
The Trap Of Green Metrics
Green dashboards can mislead when they measure what is easy to count rather than what matters most.
Recordable injury rates, audit scores, and training completion percentages have value. They also have limits. They often measure lagging outcomes or administrative activity. They may not show whether high-consequence risk is under control.
For example, a chemical plant can have a strong personal safety record while process safety barriers are degrading. A construction project can have few injuries while lifting plans are rushed. A hospital unit can meet compliance targets while staff rely on memory to catch medication errors.
Good leaders ask what the metric does not show.
They also compare lagging indicators with leading indicators, such as:
Critical control verification.
Backlog of safety-critical maintenance.
Quality of pre-job risk assessments.
Repeat audit findings.
Emergency drill performance.
Effectiveness of corrective actions.
Frequency and quality of near-miss reporting.
Metrics should start conversations, not end them.
The Trap Of Familiar Risk
People become comfortable with hazards they see every day. That comfort is dangerous.
A worker who has crossed the same live traffic zone hundreds of times may stop seeing it as unusual. A maintenance crew may accept a recurring alarm because it clears after a reset. A drilling team may normalize small deviations because previous jobs finished safely.
This is not a failure of individual character. It is a known human pattern. Familiarity lowers perceived risk. Repetition creates confidence, even when the underlying hazard remains.
Chronic unease interrupts that pattern. It brings fresh attention to familiar work.
A strong leader might ask:
“Which hazards have become background noise?”
“What do experienced workers ignore because they have learned to manage it?”
“What would a new person find confusing or unsafe here?”
“Which alarms, defects, or deviations have we stopped treating as signals?”
These questions help teams see the workplace again.
Why Curiosity Finds What Compliance Misses
Compliance asks, “Did we meet the requirement?” Curiosity asks, “How does the work actually happen?”
Both matter. Compliance creates minimum standards. Curiosity reveals whether those standards work under pressure.
In high-risk industries, the gap between documented work and real work can be large. Procedures may be accurate on paper but hard to use in the field. Staffing assumptions may fail on night shift. Tools may be unavailable. Weather may change the task. Production schedules may compress decision-making.
A curious leader wants to understand these conditions before an incident exposes them.
That requires more than scheduled audits. It requires time in the field, direct observation, and honest dialogue. Leaders need to see work as performed, not only work as imagined.
A useful practice is to ask workers to walk through the last time a job became difficult. Not the ideal version. The real one.
Questions can include:
“What made this task harder than expected?”
“Where did the procedure help?”
“Where did the procedure slow you down or create confusion?”
“What did you have to adjust?”
“What would have made the safe way easier?”
“What do people do when the plan does not fit the job?”
These questions avoid blame. They focus on how the system shapes behavior.
Curiosity also improves learning from weak events. A near miss can become a paperwork exercise if leaders only ask who made an error. It becomes valuable when leaders ask why the error made sense at the time.
People usually do not come to work planning to fail. They make decisions based on goals, constraints, cues, and previous experience. A curious leader studies those conditions.
That is where better risk management begins.
Curiosity Changes The Tone Of Investigations
Many organizations say they want learning, then investigate in a way that feels like prosecution. Workers notice. The next time something happens, they share less.
A chronic unease mindset changes the tone.
Instead of asking, “Who failed to follow the rule?” leaders ask:
“What conditions made the rule hard to follow?”
“What assumptions did the plan make?”
“What signals were available?”
“What signals were missed?”
“Which controls worked?”
“Which controls depended on human recovery?”
“Where else could the same pattern exist?”
This does not remove accountability. It places accountability at the right level. Reckless behavior still needs firm action. But most events involve system weaknesses, not simple carelessness.
A learning-focused investigation looks for patterns that repeat across sites and teams. It treats the event as a window into normal work.
That approach builds trust. It also generates better fixes.
A retraining memo may satisfy an action tracker. It rarely changes the conditions that shaped the event. Better actions may include redesigning tools, changing staffing, improving permits, clarifying authority, simplifying procedures, or fixing equipment.
Curiosity turns weak signals into prevention.
Why Weak Signals Deserve Strong Attention
A weak signal is an early sign that something may be wrong. It is often small, ambiguous, and easy to dismiss.
Weak signals include:
A near miss with no injury.
A repeated alarm.
A maintenance deferral.
A skipped step that has become common.
A permit signed but not understood.
A contractor raising the same concern twice.
A supervisor saying, “We are making it work.”
A trend of minor leaks, trips, or dropped objects.
A quiet team that used to raise issues.
A critical control verified from memory rather than observation.
Weak signals rarely arrive with a label that says “major risk.” Leaders must interpret them.
The challenge is that organizations are good at explaining away weak signals. They call them one-offs. They blame unusual circumstances. They treat near misses as proof that defenses worked, not as proof that defenses were tested.
Chronic unease makes leaders slower to dismiss small signs.
A useful rule is to ask whether a weak signal shows a local issue, a system pattern, or a control weakness.
If a worker bypasses a guard one time, the issue may involve training or supervision. If several workers bypass the same guard, the design may make the task difficult. If multiple sites report similar bypasses, the organization may have a broader control problem.
The signal gets stronger when it repeats.
Near misses deserve special attention because they show what could have happened without the cost of tragedy. Aviation has long treated incident reporting as a source of learning. Health care, nuclear power, and other high-risk sectors have adopted similar ideas because near misses can reveal risk before harm occurs.
The value comes only when reporting leads to action.
If workers report hazards and nothing changes, reporting declines. If leaders act only after injury, workers learn that pain gets attention and prevention does not.
Sensitivity to weak signals requires visible follow-through.
Why Leaders Must Question Success
Success can be risky when it stops inquiry.
After a strong quarter, safe project completion, or long period without a recordable injury, organizations often move quickly to recognition. Recognition has value. People should see that safe work matters. But strong leaders also ask what the success teaches.
Did the plan work as designed, or did people rescue it?
Did controls prevent exposure, or did luck prevent harm?
Did the team have enough time and resources, or did they absorb pressure quietly?
Did the absence of incidents reflect strong reporting, or weak reporting?
These questions may feel uncomfortable after good news. That is the point.
Success can hide fragile systems. Teams may deliver results by relying on informal knowledge, extra effort, unreported shortcuts, or last-minute fixes. Those adaptations can create resilience. They can also mask broken processes.
A leader with chronic unease studies success with the same seriousness as failure.
This is common in aviation and emergency response. Teams often hold debriefs after normal operations, not only after failures. They review what went well, what was difficult, what changed, and what should be improved. The goal is not to criticize success. The goal is to understand it.
High-risk organizations should do the same.
After a shutdown, lift, confined space entry, live electrical task, emergency drill, or complex patient transfer, leaders can ask:
“Where did the plan match reality?”
“Where did the team have to adapt?”
“Which controls mattered most?”
“Which controls were assumed but not tested?”
“What almost surprised us?”
“What would have failed if conditions were slightly worse?”
“What should we change before the next job?”
This practice turns success into data.
It also reduces overconfidence. Teams that succeed under difficult conditions can start believing they are immune to failure. That belief weakens defenses.
Questioning success keeps humility in the system.
Chronic Unease Is Not Anxiety Or Excessive Caution
Chronic unease is often misunderstood. Some people hear the phrase and think it means worry, fear, or constant hesitation.
That is wrong.
Anxiety is a stress response. It can narrow attention, reduce confidence, and make decisions harder. Excessive caution can stop useful work, overload teams with controls, and create frustration. Neither one is the goal.
Chronic unease is controlled, practical, and evidence-seeking. It supports action.
The difference is clear:
Chronic Unease | Anxiety Or Excessive Caution |
Looks for evidence | Reacts to fear |
Asks clear questions | Repeats vague concerns |
Focuses on critical risk | Treats all risks the same |
Encourages reporting | Creates silence or fatigue |
Supports timely decisions | Delays decisions without new information |
Tests assumptions | Avoids responsibility |
Builds learning | Builds stress |
Chronic unease does not mean leaders should stop work whenever there is uncertainty. High-risk work always includes uncertainty. The right response is to understand the uncertainty, check the controls, and decide with discipline.
A good leader can say, “We know the hazard. We know the controls. We verified they are in place. We are ready to proceed.”
That is not complacency. It is confidence built on evidence.
The opposite is false certainty. False certainty sounds like:
“We have done this for years.”
“The team knows what to do.”
“We passed the audit.”
“Nothing has gone wrong.”
“The procedure covers it.”
“We cannot afford to slow down.”
“This is routine.”
Routine work can kill. Routine work often receives less attention than unusual work because people assume it is controlled.
Chronic unease restores attention without creating fear.
The Best Leaders Stay Calm And Unsatisfied
The emotional tone matters. Leaders should not spread alarm. They should model calm attention.
A leader who walks into the field looking angry will get compliance behavior. People will hide the mess. A leader who walks in curious, prepared, and respectful will get better information.
Chronic unease works when it feels like disciplined care, not suspicion.
That means leaders must manage their own reactions. If every bad finding produces blame, weak signals will disappear. If every concern triggers excessive paperwork, people will stop raising concerns. If leaders reward only clean reports, clean reports will arrive.
A mature safety culture can tolerate discomfort. It can hear bad news early. It can discuss uncertainty without panic. It can pause work without shame. It can restart work with confidence.
Practical Leadership Behaviors That Build Chronic Unease
Chronic unease becomes useful only when it changes behavior. Posters and slogans do not create it. Daily leadership practices do.
The following behaviors make the mindset visible.
Ask Better Field Questions
Generic questions produce generic answers. “Any safety issues?” often gets silence.
Better questions make it easier to share real conditions:
“What is the most likely way someone could be hurt on this job today?”
“Which control matters most?”
“How do we know that control is working?”
“What changed since the plan was written?”
“What would make you stop the job?”
“Where are we relying on experience instead of a physical control?”
“What is harder than it needs to be?”
These questions show interest in risk, not just compliance.
They also reveal whether people understand the critical controls. If a team cannot name the most important control, the job may not be ready.
Treat Bad News As Valuable Information
Leaders get the reporting culture they reward.
If bad news creates punishment, delay, or embarrassment, people will filter it. If bad news creates support and problem-solving, people will bring it earlier.
A strong response to a weak signal sounds like:
“Thank you for raising it.”
“What makes this concern important?”
“Who else needs to know?”
“What immediate control do we need?”
“What system issue does this point to?”
“How will we close the loop?”
Closing the loop matters. People need to see what changed because they spoke up.
Verify Critical Controls In The Field
A critical control is a control that prevents or limits a serious event. Examples include isolation, ventilation, fall protection, gas testing, lifting exclusion zones, machine guarding, pressure relief, traffic separation, and emergency shutdown systems.
Leaders should not rely only on paperwork for these controls. They should verify them where the work happens.
That means checking:
The control is present.
The control is being used.
The control is suitable for the task.
The workforce understands why it matters.
The control will still work if conditions change.
This is different from a general inspection. It focuses attention on fatal and high-consequence risk.
Review Success Before Celebrating It
Recognition should not erase learning.
After a strong result, leaders can hold a short success review. The aim is to understand what produced the outcome.
Ask:
“Which decisions helped us succeed?”
“Which controls performed well?”
“Which issues did the team absorb?”
“What nearly went wrong?”
“What should be repeated?”
“What should be improved?”
This practice prevents the organization from learning the wrong lesson. Success should not teach teams that risk was low if the truth is that recovery was strong.
Watch For Drift
Drift happens when small deviations become normal. It often starts for practical reasons. A step takes too long. A tool is missing. A form does not fit the job. A client asks for speed. A supervisor tolerates a shortcut once.
Over time, the workaround becomes the process.
Leaders need routines that detect drift:
Compare procedures with actual work.
Track repeat exceptions.
Review overdue maintenance.
Study permit quality.
Look at contractor practices.
Ask experienced workers what has changed.
Pay attention to tasks described as “just the way we do it.”
Drift is easier to correct early. After it becomes culture, it takes more effort.
Make Stop-Work Authority Real
Many organizations say anyone can stop work. Fewer prove it.
Stop-work authority is real when people believe they can use it without retaliation or ridicule. Leaders prove this through their response.
When work stops, leaders should focus on the condition, not the inconvenience. They should thank the person, assess the risk, and help resolve the issue. If the stop was unnecessary, leaders should still protect the intent and use it as a learning moment.
A single poor reaction can undo years of messaging.
Separate Production Pressure From Safety Decisions
Production pressure is normal. Pretending it does not exist weakens credibility.
Leaders should name the pressure and create clear decision rules.
For example:
“We are behind schedule, but isolation steps do not change.”
“We can adjust the sequence, but not the exclusion zone.”
“If the weather crosses the limit, we stop.”
“If the gas test is not current, entry does not happen.”
“If the lift plan no longer matches conditions, we replan.”
This clarity helps supervisors and workers make safe decisions when time pressure rises.
Learn Across Boundaries
Risk patterns rarely stay inside one crew, site, or department. A weak signal in one area may warn another area.
Leaders should create simple ways to share learning across boundaries:
Short alerts focused on what changed, not who erred.
Cross-site reviews of serious near misses.
Common critical control checks.
Peer visits between teams.
Contractor inclusion in learning reviews.
Follow-up checks to confirm actions worked.
The best learning is specific. “Be careful” is not learning. “Verify stored energy isolation at the valve and the local panel before removing the guard” is useful.
Build Psychological Safety Without Lowering Standards
Psychological safety means people can speak up, question, and report concerns without fear of humiliation or retaliation. It does not mean anything goes.
High standards and openness belong together.
Leaders can say, “We expect procedures to be followed. We also expect people to tell us when the procedure does not match the job.”
That combination matters. If leaders only stress compliance, workers may hide the gap. If leaders only stress openness without standards, work can become inconsistent. Chronic unease needs both.
How To Tell If Chronic Unease Is Working
Chronic unease should improve decision quality. It should not create noise.
Signs it is working include:
Leaders spend more time discussing serious risk than minor compliance issues.
Workers report concerns earlier.
Near-miss reports contain better detail.
Corrective actions address conditions, not only behavior.
Critical controls are verified in the field.
Teams challenge assumptions before complex work.
Success reviews identify real lessons.
Stop-work events are treated as learning.
Senior leaders ask about weak signals, not only injury rates.
Production plans change when controls are not ready.
Signs it is turning unhealthy include:
Teams delay work without new risk information.
People fear making decisions.
Leaders react emotionally to every issue.
Reporting becomes a burden with no visible value.
Controls multiply without reducing serious risk.
Workers see safety as paperwork rather than protection.
The organization treats all hazards as equal.
The goal is tension, not paralysis. A high-risk organization needs enough discomfort to keep looking, learning, and verifying. It also needs enough confidence to act.
That balance is the mark of mature safety leadership.
The Takeaway For Safety Leaders
Chronic unease is one of the most useful habits in high-risk work because it challenges the stories organizations tell themselves.
“We are safe because nothing happened.”
“We are safe because the dashboard is green.”
“We are safe because the audit passed.”
“We are safe because our people are experienced.”
Each statement may be partly true. None is enough.
Strong leaders stay slightly uncomfortable because they understand how risk behaves. It hides in normal work. It grows through small compromises. It is softened by success. It appears first as weak signals that are easy to explain away.
The answer is not fear. The answer is disciplined curiosity.
Ask what the data misses. Verify critical controls. Study success. Protect bad news. Listen for quiet signals. Look for drift. Make it safe to stop work. Keep standards high and blame low.
Chronic unease in safety leadership is not a mood. It is a practice. Done well, it keeps organizations humble, alert, and ready before the incident happens.
