Your Heat Program Is Not a Water Cooler

Most heat programs start with good intentions.

A water station.
A reminder poster.
A toolbox talk.
Maybe a weather alert forwarded when the forecast turns ugly.

Those things matter.

But they are not a heat program.

They are pieces of one.

The real question is not whether your people have access to water. The real question is whether the way you plan, staff, pace, and supervise the work gives them a realistic chance to manage heat exposure.

That is where many sites get exposed.

Heat illness prevention often gets treated like a worker behavior issue.

Drink more water.
Speak up sooner.
Take a break when you need one.

But workers do not operate in a vacuum. They operate inside a production system.

They respond to schedules, downtime pressure, supervisor expectations, manpower shortages, PPE requirements, and the unspoken message that the job still has to get done.

If the job plan assumes the same output in higher heat, the system has already made a decision.

It has chosen production pace and left the worker to absorb the heat burden.

That is not a water problem.

That is an operating control problem.

OSHA’s 2026 update to its National Emphasis Program for outdoor and indoor heat-related hazards reinforces that heat exposure remains an active enforcement and prevention issue. OSHA says the revised program focuses inspections and outreach on industries and workplaces where heat stress risks are most likely to occur, using recent OSHA and Bureau of Labor Statistics data to target higher-risk settings.

The practical takeaway is simple.

Heat risk needs to be built into the operating rhythm before the forecast forces the conversation.

That means leaders need to review work pace, break timing, acclimatization, staffing, emergency response, indoor heat sources, and PPE burden before the day gets away from them.

It also means supervisors need clear authority to adjust work when conditions change.

A heat plan that only exists on paper will fail under pressure.

So will a plan that depends on workers to self-manage while production expectations stay untouched.

The better system asks different questions.

What tasks create the most heat load?

Which employees are new, returning, or not acclimatized?

Where does PPE make the job hotter?

What work should be moved, slowed, rotated, or rescheduled?

Who decides when the plan changes?

Who verifies that breaks actually happen?

What happens when the heat plan conflicts with production?

Those are not safety-department-only questions.

Those are operational planning questions.

Water matters.
Shade matters.
Rest matters.
Training matters.

But the strongest heat programs do more than remind people to drink.

They make heat visible in the plan.

They give supervisors decision rights.

They treat heat exposure like any other production constraint that can disrupt people, quality, and output.

A water cooler can help a worker recover.

It cannot fix a schedule that was never designed for the heat.

Safety is the outcome.

Before the next heat advisory, do not just ask whether the water is stocked.

Ask what part of the work needs to change.

Zero Losses: Building a Culture Where Chronic Problems Aren’t Normal

In many plants and facilities, chronic equipment problems and recurring safety incidents are quietly baked into budgets and schedules.
Leaders talk about continuous improvement, yet they tolerate machines that always run slow, lines that need extra labour or defects that are “always caught downstream.”
Over time, these losses become accepted as unavoidable “noise.” A zero‑losses mindset challenges that thinking. It doesn’t pretend perfection is easy; instead it asks a different question: “Why are we still living with this?”

Why a Zero‑Loss Mindset Matters

Treating improvement as a separate program quietly erodes frontline performance and consumes margins. When improvement isn’t woven into daily work, hidden losses build up—wasted time, stalled initiatives, thinning trust and rework. In a 2026 study cited by SafetyCulture, fewer than one in five frontline supervisors said most improvement initiatives fully succeeded. Leaders often believe improvement is happening, but only 39 % of frontline supervisors say it’s embedded in their day‑to‑day work. This “improvement paradox” means more initiatives can actually make the system noisier rather than better.

A zero‑loss approach treats chronic losses as gaps to close, not friction to endure. It starts by naming and measuring losses so they no longer hide in the background. Once losses are visible and owned, teams can work systematically to eliminate them.

Hidden Costs of Accepting Losses

When improvement lives outside daily operations, the costs don’t always show on the balance sheet, but they add up quickly. Frontline supervisors and leaders report that failed improvement efforts translate into wasted time, resources, lower trust and missed customer expectations. Incomplete initiatives increase rework and firefighting, and poorly executed programs can even damage a company’s culture or reputation. These hidden losses erode performance and margins, undermining the very gains leaders hope to achieve.

Building a Zero‑Loss Culture

Solving the improvement paradox isn’t about launching another program—it’s about redesigning the system. Four capability areas form the backbone of a strong continuous‑improvement model:

1. Culture and enablement: create psychological safety and shared responsibility so issues can be surfaced and solved.

2. Leadership and governance: define clear purpose and decision rights, provide active sponsorship and remove barriers.

3. Systems and tools: use intuitive platforms that support decisions and embed improvements into workflows.

4. Measurement and feedback: establish shared metrics, hold regular reviews and close feedback loops so teams see the impact of their ideas.

Building a zero‑loss culture also requires aligning goals across layers, pushing decision rights closer to the frontline and empowering employees to act. Leaders must standardise processes, train people and model the behaviours they expect.

Case Study: General Mills’ Journey to Zero Losses

Food company General Mills offers a real‑world example of embracing a zero‑loss culture. Facing stalled safety improvement, General Mills partnered with dss⁺ to make safety not just a priority but a value. They introduced a safety observation process, trained more than 1 000 team leaders and 5 000 employees, and conducted more than 2 million safety contacts to reinforce safe behaviours.

The company established global safety standards and a Global Safety Governance Board to oversee progress, aligning safety requirements—like PPE and risk assessment methods—across all production facilities. They also implemented a single Environmental and Safety Management System to provide uniform processes worldwide. Training workshops helped more than 1 600 leaders learn how to lead in a zero‑loss culture.

The results speak for themselves. Over six years (2011‑2018), General Mills reduced injuries by 52 % and cut its recordable rate from 2.2 to 0.77, the lowest in the company’s history. Continuous safety observations and corrective actions continue to rise as evidence that the zero‑loss culture is sustainable.

Steps to Start Your Own Zero‑Loss Journey

Implementing a zero‑loss mindset doesn’t require radical new technology; it begins with leadership asking different questions and committing to systematic improvement:

• Identify chronic losses: catalogue defects, downtime, injuries and recurring problems. Accept none of them as normal.

• Make losses visible: measure and share data regularly so everyone sees the gap between current performance and the ideal state.

• Empower the frontline: push decision rights closer to where the work happens. Encourage employees to surface issues without blame and give them tools to act.

• Align goals and metrics: connect frontline priorities with strategic outcomes and use a small set of shared metrics to prevent initiatives from pulling in different directions.

• Standardise and train: develop clear standards for processes and safety, and ensure leaders are trained to model and reinforce desired behaviours.

• Close feedback loops: regularly review progress, recognise successes and show how employee suggestions translate into action.

Conclusion

A zero‑loss mindset isn’t about chasing perfection; it’s about refusing to accept avoidable losses as the cost of doing business. By embedding improvement into daily workflows and aligning culture, leadership, systems and measurement, organisations protect margins, build trust and make safety an everyday value. As General Mills’ success shows, when leaders stop treating chronic losses as background noise and instead treat them as gaps to close, operational excellence and safety performance can improve dramatically.

Stop Using Training to Fix What Design Broke.

November 11, 2025
By Nick Combs, CSP

Retraining is one of the most common ways leaders avoid a harder truth.

It feels responsible. It sounds supportive. It gives the organization something visible to do.

It is also frequently the wrong first move.

Training matters. New people need it. Changed processes need it. Critical tasks need reinforcement. Standards need to be taught clearly and repeated consistently.

But training is not a repair strategy for bad design.

When an incident repeats, when a quality miss keeps resurfacing, or when operators rely on workarounds to get through the shift, leaders often default to the same response: retrain the team.

Sometimes that helps.

A lot of times it hides the real failure.

If the job is poorly designed, no amount of retraining will make it stable. If the cycle time is unrealistic, the layout is awkward, the tool is unreliable, the handoff is weak, the standard is hard to follow, or the competing priorities are obvious, people will keep adapting. They have to. The system is asking them to choose between formal compliance and getting the work done.

That is not a training gap.

That is a leadership gap.

Consider how often this happens in plants. A jam clearance step requires awkward reach and poor visibility. A sanitation task is scheduled into an impossible window. A forklift route crosses pedestrian traffic because the flow was never truly separated. A changeover depends on tribal knowledge instead of visual standards. A permit process exists, but everyone knows production pressure can quietly override it.

Then something goes wrong.

The response is a toolbox talk.

That is too small.

Before a leader assigns training as the solution, a few questions should come first. Was the standard clear in the field, not just on paper? Was the task physically set up to be performed that way? Did the operator have the time, tools, and authority to follow the standard? Were there conflicting incentives pushing the wrong behavior? Did supervision reinforce the rule when the schedule got tight? Could the team pause the work without punishment?

Those questions matter because people usually follow the system they actually live in, not the one leadership thinks exists.

That is why repeated retraining can quietly damage trust. Operators see the mismatch. They know when the real issue is staffing, layout, access, equipment condition, changeover time, or mixed signals from leadership. When management keeps sending them back to class instead of fixing the work, the message becomes clear: we are going to explain the problem to you instead of solving it with you.

That rarely improves performance for long.

A better sequence is simple. First, observe the job where it happens. Second, identify what the work is asking people to overcome. Third, change the conditions that make the wrong action easier than the right one. Then train to the improved standard.

That order matters.

Good training stabilizes a well-designed process. It does not rescue a broken one.

Plant leaders should remember this: the goal is not just informed people. The goal is reliable execution. Those are not the same thing. A highly informed operator inside a poorly designed system will still be forced to adapt. And repeated adaptation is where risk, drift, and fatigue start to grow.

Training has a place.

A very important place.

But when it becomes the automatic answer, it usually means leadership is choosing the most comfortable intervention instead of the most effective one.

Do not ask people to memorize their way around weak design.

Fix the work.

Then teach the standard that the work can actually support.

Calm Is Not Complacency. It Is Control.

February 19, 2026
By Nick Combs, CSP

Some plants look strong because they move fast under pressure.

That is not strength.

That is adaptation.

There is a difference.

A plant that survives on heroics can look impressive from a distance. Supervisors are everywhere. Maintenance is improvising. Production is pushing. Good people are carrying the day again. The line stays moving. Orders still ship. Everyone goes home tired and convinced they won.

But repeated heroics are usually evidence that the system is unstable.

Real control is quieter than that.

A controlled plant does not need constant rescue. Standards are visible. Work is sequenced well. Handoffs make sense. Risk is known before the task begins. Operators do not have to guess. Supervisors do not have to translate expectations in real time. Problems get seen early, when they are still small enough to fix without drama.

That kind of calm makes some leaders uncomfortable.

Calm does not look urgent. It does not create the same emotional signal as a last-minute recovery. It does not give people a stage to prove how committed they are. It just produces repeatable work.

And that is exactly why it matters.

When leaders reward the save more than the stable process, the organization learns the wrong lesson. It starts to admire exhaustion. It starts to normalize confusion. It starts to believe that struggling hard is the same thing as running well.

It is not.

A plant leader should pay close attention to where heroics show up most often. Look at the changeover that only works when your best operator is present. Look at the startup that always feels messy. Look at the area where the same housekeeping issue reappears. Look at the near miss that has been “talked about” three times but still lives in the work. Those are not people problems first. Those are design signals.

That is where leadership should go to work.

Walk the process and ask better questions. What part of this job depends on memory instead of standard work? Where does the handoff get weak? What gets rushed when the schedule tightens? What do your best people do silently that the system has never captured? What friction are you asking operators to absorb every shift because it has become normal?

That is practical leadership.

Not louder direction. Better design.

In most plants, instability hides inside familiar routines. A tagout that takes too long. A permit process nobody trusts. An inspection route that gets skipped when staffing is tight. A material flow issue that forces unnecessary motion. A startup checklist that exists on paper but not in practice. Small things. Repeated things. Expensive things.

A calm plant is not one with fewer expectations. It is one with fewer surprises.

It still has urgency. It still has standards. It still has accountability. But it does not ask people to create control from scratch every day. The system carries more of the load.

That is the point.

Plant leaders do not need to make work look intense. They need to make work hold under pressure. They need processes that survive fatigue, turnover, shift changes, visitor pressure, and production demand. They need teams that can pause early instead of recover late.

Calm is not passive.

Calm is disciplined.

Calm is a leadership decision.

And in a plant, it is one of the clearest signs that control is real.

No Action Is Complete Without Proof.

January 8, 2026
By Nick Combs, CSP

Plants do not usually drift because nobody cares.

They drift because closure gets too easy.

Somebody says the issue was handled. A supervisor says the conversation happened. A manager says the team has it. Engineering says the change is in motion. Safety says training was completed. Maintenance says the repair is done.

Maybe all of that is true.

Maybe none of it is.

Without proof, leadership is not tracking progress. It is tracking optimism.

That matters more than most teams realize.

A lot of plant work lives in the gap between decision and verification. Guarding gets approved but the condition is not photographed. A procedural change gets discussed but the document never changes. Training gets delivered but there is no roster, no observation, and no evidence that the job was actually performed to standard. A corrective action gets marked closed because the pressure moved on.

Then the same issue returns.

Not because people lied.

Because the organization accepted intention as completion.

That is expensive.

Proof does not have to be complicated. It just has to be real. A revised SOP. A signed-off work order. A photo of the repaired condition. A completed training roster. A field verification. A PM revision in the system. A documented permit change. A supervisor observation that shows the new standard is actually being used.

That is closure.

Everything else is conversation.

Some leaders resist this because they think it creates bureaucracy. In reality, it removes noise. Teams waste enormous time re-litigating old issues when nobody can tell what was actually done. They repeat meetings. They repeat arguments. They repeat promises. Proof shortens all of that. It gives the organization memory.

It also sharpens accountability.

When every action has one owner, one due date, and one clear closure standard, performance becomes easier to see. Leaders can distinguish between slow progress and no progress. They can tell the difference between a blocked item and a neglected one. They can escalate early instead of getting surprised late.

That is not administrative discipline for its own sake.

That is operational control.

Plant leaders should be especially careful with recurring actions tied to safety, quality, and reliability. Those are the easiest places for verbal closure to create false confidence. If a conveyor guard was modified, show it. If a lockout step changed, show it. If a near miss led to a new control, show it. If a contractor requirement was tightened, show it.

The standard should be simple: if someone new walked into the area tomorrow, could they see the change or verify it without needing a long explanation?

If not, the action probably is not closed.

This also changes the quality of meetings. Weekly reviews get shorter when teams stop speaking in generalities. “We’re working on it” is not an update. “The new interlock was installed Tuesday, tested Wednesday, and operator signoff is attached” is an update. One creates motion. The other creates confidence.

Plants do not improve from agreement alone.

They improve from evidence.

So the next time an action comes back marked complete, ask one more question.

What is the proof?

That question will clean up more drift than another speech ever will.

The Silent Killers: Why Confined-Space Work Demands Our Urgent Attention

Confined-space work remains one of the most dangerous activities in general industry. Despite decades of awareness and regulation, workers continue to lose their lives in preventable tragedies. Recent incidents and research emphasize the critical need for improved compliance, training, and cultural accountability in confined-space safety.

On May 7, 2025, a maintenance worker in Palm Desert, California, fell approximately 20 feet into an underground vault. Emergency crews responding to the scene reported the presence of hydrogen sulfide gas, an extremely hazardous atmospheric condition. Despite their efforts, the worker was pronounced dead at the scene (KESQ News Channel 3, 2025). This is not an isolated case but one of many similar incidents occurring across the United States each year.

In September 2023, a contractor working inside a water tank near Oklahoma City succumbed to asphyxiation. OSHA’s investigation revealed that the employer failed to conduct atmospheric testing and lacked a permit-required confined space (PRCS) program, resulting in citations totaling over $103,000 (U.S. Department of Labor, 2023). These failures are consistent with broader patterns seen across industries.

Purdue University’s Agricultural Confined Space Incident Database (2024) documented 51 confined-space incidents in 2023, including 22 fatalities. Notably, Indiana alone accounted for five incidents, and most cases involved grain bin entries, which are especially hazardous due to engulfment and oxygen-deficient environments. The data underscores the pressing need for training and oversight, particularly in the agricultural sector.

Statistical analysis shows that 56% of confined-space fatalities are attributed to hazardous atmospheres, 20% to mechanical hazards, and 11% to engulfment (National Institute for Occupational Safety and Health [NIOSH], 2020). Furthermore, nearly two-thirds of confined-space fatalities involve would-be rescuers who attempt entry without proper training or equipment (Centers for Disease Control and Prevention [CDC], 2017).

Despite OSHA’s PRCS standard (29 CFR 1910.146), many organizations fail to implement comprehensive entry procedures. OSHA estimates that only about 30% of workers involved in confined-space work receive annual training, though enhanced training could reduce fatalities by up to 85% (OSHA, 2023).

To reverse this trend, employers and safety leaders must prioritize:

1. Strict adherence to PRCS requirements, including entry permits and atmospheric testing.

2. Regular, comprehensive training for all personnel involved in confined-space operations.

3. Availability of non-entry rescue equipment and trained standby personnel.

4. A cultural shift that places safety above productivity.

Confined spaces—such as tanks, silos, vaults, and pits—should not be death traps. The continued occurrence of preventable fatalities is a moral failure as much as it is a regulatory one. The lives lost in Palm Desert and Oklahoma City must not be in vain. These incidents must serve as a call to action for employers, regulators, and the broader public to treat confined-space safety with the urgency it demands.

References

Centers for Disease Control and Prevention. (2017). Fatal occupational injuries involving confined spaces. https://www.cdc.gov/niosh/topics/confinedspace/

KESQ News Channel 3. (2025, May 7). Worker dies after falling into underground vault in Palm Desert. https://kesq.com/news/2025/05/07/worker-dies-underground-vault

National Institute for Occupational Safety and Health. (2020). Preventing deaths and injuries of workers in confined spaces. https://www.cdc.gov/niosh/docs/86-110/

Occupational Safety and Health Administration. (2023). Confined spaces standard: 29 CFR 1910.146. https://www.osha.gov/confined-spaces

Purdue University. (2024). Summary of U.S. agricultural confined space-related injuries and fatalities 2023. https://engineering.purdue.edu/ABE/Research/Surveys/GrainBinEntrapment

U.S. Department of Labor. (2023, October). Oklahoma tank death results in citations for confined space violations. https://www.osha.gov/news/newsreleases