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.

What I do.

I frame product direction, map operational workflows, define permissions and decision boundaries, and build enough to test whether the idea holds up.

At Compass Healthcare Digital that meant stopping a parallel rounding module before build, so rounding became a state in the follow-up lifecycle most sites already ran. At ServiceNow it meant one canonical partner request across five systems, with the role that holds it and the stage it is in stated on the record.

Enterprise Platforms · Healthcare Operations · Financial Services · Product Direction

Enterprise Platforms stamp with an engraved humpback whale.
Healthcare Operations stamp with an engraved jellyfish.
Financial Services stamp with an engraved shark.
Product Direction stamp with an engraved octopus.

Where I've done it.

The tools I reach for.

The stack changes. The loop doesn't: frame it, build enough to test it, then prove what changed.

01

Design

Figma · Framer

02

Build

Claude Code · Cursor · TypeScript · Next.js · Tailwind · shadcn/uiBuilt this site and the working review gate in Lumens in code.

03

AI + agents

Claude API · OpenAI API · MCPBo, the model-backed guide on this site, and the Lumens build.

04

Evaluate

Behavioral checks · browser verification · regression checks · citation checksEvery release of this site runs scripted copy, privacy, layout and Bo-answer checks before it goes live.

05

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 photograph places that feel lived in, and take the scenic route even when it's objectively inefficient. Dogs generally improve the plan.

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.

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.

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.

Because autonomy has to be earned. Bo's job is to help you understand the work, find the evidence, and ask a better question. He does not need to act on your behalf to do that. I give a system the smallest useful autonomy and widen it when the workflow proves it needs more.

Email me