Senior product designer · design engineer
I asked that all year. Now every project I touch starts with one.
I design complex workflow software that ships, and I built the governed AI process that hands engineering a working prototype to build from.
Tidemark is a small-business lender that doesn’t exist. Its payment-exceptions screen has been stuck in review for a month. This is the prototype I’d build in week one. Click around, then make the decision that unsticks it.
The prototype needs JavaScript to run.
Product craft
On building an insurance quote like a Ferrari.
At conferences, the thing agents told our agency-development team most often was that this was the smartest quoting interface they’d seen.
Obie’s first homeowners line, on a backend that had never contemplated it, and the seams we didn’t hide until agents found them.
When Obie opened its platform to independent agents, the page they’d live in was built for our own brokers. I redesigned what it was organized around. Nearly three years later, it’s one of the most-used pages in the product.
Writing
In insurance software, what a screen does is usually a rule. A frame shows what the screen looks like. It leaves the rule out.
Working with AI gave us time back. Here’s how we’re using it.
Fast is free now. The expensive part is making it safe, legible and adoptable, then proving it by handing the work to an engineer who wasn’t in the room.
The written law I use to run a fleet of AI build agents. Take it.
Machine-checking design tokens found a bug every human eye had passed for years.
An agent building a quote. A policyholder checking what they owe. An underwriter deciding on a risk. And an engineer, opening whatever I hand them. Designing for that last one is why our handoff became working software.