Selected work

Product decisions made visible.

Two case studies showing how I move from ambiguous questions to testable product direction. One is open — the other is available on request.

How I work

A process that earns its decisions.

The steps flex with the problem, but the order of operations stays the same: understand, frame, prototype, validate.

  1. 01

    Understand before designing

    I start with research — interviews, competitive analysis, and app-store or field evidence — so the problem I design for is the real one, not the visible one.

  2. 02

    Frame and make tradeoffs visible

    I map assumptions, journeys, and constraints so the team can see what we're betting on and argue about concrete choices instead of abstractions.

  3. 03

    Prototype the riskiest part first

    Rough flows and clickable prototypes go in front of people early, while the design can still change without sunk cost.

  4. 04

    Validate, then simplify

    Testing tells me what to cut. The final design is usually smaller and clearer than the first one — on purpose.

Toolbox

Tools I think with.

Tools change; the habits behind them don't. This is the current kit I use to research, design, and communicate.

Design & prototyping

FigmaFigJamFigma prototypingDesign systems

Research & testing

User interviewsUsability testingAffinity mappingJourney mapping

AI & exploration

ChatGPTClaudeAI prototyping

Communication & handoff

NotionDev handoff in FigmaWritten rationale

Building something useful? I’d love to help.

United StatesLinkedIn