UX LEGENDARY
THE PROCESS

Four phases. One partner.Evidence at every gate.

The same method behind every engagement — from a two-week research sprint to a nine-month platform build. Predictable cadence, written gates, one partner accountable end to end.

THE FOUR PHASES

Every engagement moves through the same four gates.

PHASE 01

Understand

Week 1–2

We interview users, audit the product, and pin down the metric that matters. Nothing is designed until the target is agreed in writing.

DELIVERABLES
  • Kickoff memo
  • Stakeholder interviews
  • Product audit
  • Success metric contract
GATE TO ADVANCE

A signed decision memo — what we're solving, for whom, measured by what.

PHASE 02

Architect

Week 2–4

Flows, information architecture, and system decisions before a single high-fidelity pixel. The skeleton is where products are won or lost.

DELIVERABLES
  • User flows
  • Information architecture
  • Wireframes
  • Content model
GATE TO ADVANCE

A working prototype at wire fidelity — clicked, critiqued, corrected.

PHASE 03

Craft

Week 4–8

Interface, motion, and microcopy at obsessive fidelity. Prototypes you can feel, tokenized so engineering can ship without translation loss.

DELIVERABLES
  • Design system
  • Motion & interaction specs
  • Production-ready screens
  • Dev-QA'd handoff
GATE TO ADVANCE

A dev-QA'd build in staging that matches the spec pixel-for-pixel.

PHASE 04

Prove

Post-ship

Usability testing against the pre-agreed baseline. Every engagement closes with evidence — what changed, what it moved, what we recommend next.

DELIVERABLES
  • Post-launch usability round
  • Metrics readout
  • Recommendations memo
  • Handoff to your team
GATE TO ADVANCE

A signed close-out memo. If a metric missed, we say so and propose the fix.

THE PRINCIPLES

Four rules the process enforces.

ONE PARTNER, START TO SHIP

The partner who takes your first call runs the engagement to close. No account layer, no handoff to a junior mid-project.

EVIDENCE AT EVERY GATE

We do not advance past a phase on opinion. Each phase has a written artifact you sign before we move.

WEEKLY, NOT WATERFALL

You see work every week — often twice. If something is off, you know inside seven days, not seven weeks.

SHIPPED, NOT SHELVED

We stay through developer QA. Design that dies in Figma does not count as done.