I've spent five years in construction safety — implementing and building programs, managing compliance, and trying to make jobsites less dangerous. The traditional playbook (more training, stricter enforcement, better documentation) works up to a point. Then it stops working.
What actually moved the needle was treating field problems like product problems. I started doing user research before I knew what to call it. I built MVPs before I knew that's what they were. The difference between a safety program that sticks and one that doesn't comes down to the same things that make software good: it has to fit how people actually work, not how you wish they worked.
On the side, I take on a small number of projects each year — typically EHS technology evaluations, early-stage construction tech tools, or product consulting where someone needs both domain expertise and product judgment in the same person. If that's relevant to you, let's talk.