Discover without theater
Interviews, task analysis, and analytics that change the backlog—not slideshows that die on slide 40.
Interfaces thatfeel inevitable
Research-led product design for teams shipping complex software—flows, components, and prototypes engineering can adopt without reworking intuition.
[01] Practice
How we shape product UI
Structure first
IA, flows, and empty states designed before polish. Components only after the model is stable.
Prototype to decide
High-fidelity slices for the risky moments. Usability tests aimed at go / no-go choices.
System handoff
Tokens, specs, and Figma that engineers actually open. Adoption is part of the definition of done.
[02] Flow
From framing to shipped components
Frame
Jobs, constraints, and success metrics with product + eng in the same room.
Map
User flows, edge cases, and content models before visual design burns time.
Explore
Concept directions, low-fi tests, and a single principle set we commit to.
System
UI kit, patterns, and states. Dark/light readiness when the product needs it.
Validate
Usability sessions and crit with eng—shipping confidence, not opinions only.
Handoff
Specs, tokens, prototypes, and a hypercare loop after first release.
Coverage0% of core screens in system
[03] Package
What lands in Figma & Git
- Research briefFindings, personas, job statements, top friction points.
- Flow libraryAnnotated user journeys for primary and recovery paths.
- UI kitTokens, components, variants, content guidelines.
- PrototypeHigh-fi slices for demos, tests, and stakeholder buy-in.
- Handoff packSpecs, redlines where needed, and QA checklists.
[04] Engage
Need product design that engineering trusts?
Share product stage, stack, and the flow causing the most pain. We’ll propose a scoped engagement.
Start design workStart design work