About
I work upstream, before the screens exist.
I work on the boundary between what a system can do on its own and what still needs human judgment.
How I work
What I do.
I frame product direction, map operational workflows, define permissions and decision boundaries, and build enough of the system to test whether the idea holds up.
Four practices, same shape: a high-stakes workflow, an AI system ready to act inside it, and no shared language for how the two should cooperate. My job is to make that cooperation legible through briefs, diagrams, prototypes, and working software.
The work I'm proudest of is upstream. Problem framing. Structural decisions. The diagrams that turn months of debate into one decision.
Where I've done it.
- Compass Healthcare Digital
- ServiceNow
- Charles Schwab
- Wells Fargo
- Full experience
Toolset
The tools I reach for.
A working kit, not a fixed stack. I use what gets the idea tested properly and into someone's hands.
Design
Figma · Framer
Build
Claude Code · Cursor · TypeScript · Next.js · Tailwind · shadcn/ui
AI + agents
Claude API · OpenAI API · MCP
Evaluate
Behavioral evals · regression checks · screenshot diffs · citation checks
Ship
Vercel · Playwright · Linear
Off the clock
Elsewhere, usually.
Off the clock, I'm usually somewhere between a long drive, a camera, a kitchen, and an animal I've stopped to watch for too long. I notice buildings, old signs, odd interfaces, and the way people improvise around systems. I like cooking when there's time to make a project of it, photographing places that feel lived in, and taking the scenic route even when it's objectively inefficient. Dogs generally improve the plan.
FAQ
Questions worth asking.
Consequential systems where the cost of being wrong is high. Healthcare workflows, regulated operations, agent supervision, and enterprise products where permissions, exceptions, handoffs, and judgment determine whether the system actually works.
AI products introduce probabilistic behavior where software once relied on explicit rules and states. I design the boundary: what the system may do, what requires approval, what evidence it exposes, and how a person can inspect, correct, or take control.
I build working systems when the question is interaction, state, workflow, or judgment. I partner with engineers when the hard problem becomes architecture, security, scale, or production reliability. The boundary follows the problem, not my job title.
Start with consequence, reversibility, and accountability. Let the system act where mistakes are recoverable, ask where judgment matters, and hand control back before it crosses a boundary it should not own.
I make the decisions hiding upstream visible: what we are actually solving, what the system should own, where judgment belongs, and which assumptions are carrying the roadmap. Then I build enough to make those calls concrete.
Compare notes
System acts
Where errors are bounded and recoverable.
Pauses for approval
Where a person sees the evidence before the system commits.
Hands control back
With a clear record of what changed, what triggered it, and why.
Send a note. I reply within two business days.