From the first question to the last feedback loop.

Discover

The problem you think you have usually isn’t the problem.

Discovery tests assumptions before they’re expensive. The goal isn’t a research report — it’s a clearer picture of who has the problem, how severe it is, and what the team is secretly assuming. Interviews, journey mapping, competitive context, hypothesis statements. Where it helps, lightweight prototypes so stakeholders and users react to behavior, not slides.

Teams that skip discovery don’t skip the questions. They answer them later, with more invested, and less room to be wrong.

Interviews and insights · User personas · Competitive analysis · User journey maps · Hypothesis statements

Define

A problem well-framed is half the solution.

Define turns signal into direction — a problem statement specific enough to design against, and alignment on what success means. The temptation is to jump to UI. The discipline is staying in the problem until the viable wedge is obvious, including when the right answer is to narrow scope or stop.

Workshops, storyboards, and low-fidelity prototypes test direction before build investment. The output is a frame the whole team can argue with — and a short list of what we are not building yet.

Collaboration artifacts · Storyboards · Low-fidelity prototypes · Iterative design

Develop

Ideas are cheap. Tested ideas are not.

Develop explores and winnows options. The goal isn’t idea volume — it’s viable ones with evidence behind them. Interactive prototypes and usability tests before friction hardens. High-fidelity when direction is confirmed, not when the room wants to feel progress.

This is where the design-to-code loop is most visible: clickable flows, production-shaped builds, metrics from real use. AI compresses synthesis and iteration time; it doesn’t replace watching an expert user hit a wall you didn’t anticipate.

High-fidelity designs · Interactive prototypes · Usability metrics

Deliver

Shipping is the beginning of the feedback loop, not the end.

Deliver hands off what engineering needs — UI, specs, design systems, test scenarios — but launch is when the honest loop starts. Post-launch instrumentation, training, and iteration paths are designed in, not bolted on after disappointment.

The compounding work happens here: a mental model that deepens, a design system that earns its keep, a product meaningfully different six months later because decisions were validated with real people. That arc is what I optimize for — not a clean handoff at launch.

Style guides / Design systems · Production-ready assets · Test cases and scenarios · Feedback loops · Training materials