When an EHS implementation stalls — or the data exists but no one can act on it — the problem is usually architectural.
I diagnose it, rebuild the infrastructure, and spec the products that make it work. I've shipped EHS software from that seat, not just advised on it from outside.
EHS software fails because it's specced by people who've never investigated a fatality. The data model reflects what's easy to capture, not what a root-cause analysis needs.
Most EHS KPIs measure what already went wrong. The data architecture required for leading indicators is something most organisations have never designed. Most wouldn't know how to spec it.
The best integrated management system becomes invisible. That's an information design problem, not a training one. Compliance should be a byproduct of how people naturally work, not an enforcement layer.
Regulatory change isn't a risk to manage. It's a roadmap signal. It tells you where operational gaps will be priced in before the inspection arrives.
"Digital transformation" projects fail when the tool is bought before the data model is designed. Most EHS implementations are bought first.
Safety culture is an output, not an input. You can't train your way to it. It emerges from systems that make the right behaviour easier than the wrong one.
Have a question? Want to discuss a challenge? Reach out.