Builder by habit. I take the slow, repetitive, error-prone parts of an operation and turn them into systems that run on their own, prove they ran, and only interrupt a person when something actually changed.
Map how the work really moves, find where it waits, and remove the wait. The best step is the one nobody has to do.
Once a process is understood, it can be run by software: portals driven, files built, checks made, results delivered, every night, without a hand on it.
Numbers pulled from where they live, compared with yesterday's, and shown as the one line that matters. No dashboards for their own sake.
Heartbeats, watchdogs and quiet confirmations, so a system that stops is noticed by the system, not by the person who needed it.
Every improvement starts with a number: how long, how often, how many hands. If it cannot be measured, it is an opinion.
When a system is not sure, it says so and stops. A confident wrong answer costs more than an honest missing one.
A tool that needs a person standing next to it has only moved the work. Done means it runs, proves it ran, and asks for help only when it should.
I work in the construction industry, where the gap between how a process is supposed to run and how it actually runs is measured in days and dollars. I spend my time closing that gap: studying the work, automating what should never have been manual, and leaving behind systems that keep running after I walk away.
If you have a process that eats your week, I would like to hear about it.