About

I work on products where clarity is missing, stakes are real, and decisions compound.

Most of my work sits upstream of UI, at the point where teams are still negotiating what problem they’re actually solving, what constraints matter, and what tradeoffs they’re willing to accept. This is where products quietly succeed or fail long before anything ships.

My role is to reduce ambiguity early, before it leaks into delivery, rework, or loss of trust.

I focus on:

• Framing underspecified or conflicting problem spaces

• Turning weak signals into testable direction

• Designing systems that remain legible as they scale

• Supporting decisions under time, data, and organizational constraints
  
  

I care about rigor, but not ceremony. Research, models, and frameworks are tools, not outputs. They only matter if they help teams commit with confidence and move forward without creating downstream drag.

I’ve worked across early-stage discovery and market-scale systems, including products that reached unicorn valuation and teams that shipped under real commercial pressure. The environments change, but the failure modes repeat: unclear ownership, premature solutioning, and decisions made without shared understanding.

I’m comfortable operating across strategy and execution, abstraction and detail, but I don’t believe in design that’s detached from delivery reality, nor in velocity that ignores consequences.

If you need someone to:

• Make sense of messy inputs

• Ask the uncomfortable but necessary questions

• Help your team decide what not to build

• Strengthen judgment, not just output
  
  

We’ll likely work well together.

If you’re optimizing purely for speed, optics, or volume of features, I’m probably not the right fit.