About
I design systems that help people work better.
Technology is the medium. Improving how a business operates is the craft. Most of the work is looking closely at something everyone else has stopped seeing — the step people quietly work around, because complaining about it takes longer than doing it again.
The method is the same at every scale.
Find what something is quietly optimizing for. Recognize that the thing it optimizes for is not the thing that matters. Redesign it around how people actually behave.
At organizational scale that means request models, ownership at handoffs, and what someone sees while they wait. On a product it means knowing which assumption to kill. On an experience it means deciding what has to be understood, and in what order. The scale changes the name and almost nothing else.
Where this fits.
More than a decade across enterprise systems, workflow design, and operational reporting — requirements, configuration, automation, integration, UAT, training, and the executive reporting that turns a complaint into a decision.
I am not the engineer writing every line. I decide what should exist, design how it should work, test it honestly, and use AI to build it faster than I could alone. The judgment is the work.
What I am looking for.
A team where the operational layer has not caught up with the growth — where the tools are fine, the people are capable, and the space between them is where the work keeps catching.
If that sounds like your operation, get in touch.
The product in here is named Barry, after my dog. He is a Cavapoo, he has never once opened it, and it is still on version seven.
Employer and product names withheld where required · systems described by function · no confidential interface, data, or architecture shown