Process

From complex requirement to shipped experience.

Seven stages, never a straight line.

Continuous iteration: new insights and requirements feed back into the process.

Discover & define
01Understand the problem
Users, requirements and the real problem, agreed with stakeholders before any UI.The real problem, agreed before any UI.
What I do
Stakeholder talks, Requirements, Problem definition
Research & structure
02Map the product
Complex requirements turned into flows, IA and the edge cases nobody mentioned.Flows, IA and edge cases.
What I do
User flows, Information architecture, Edge cases
Ideate & explore
03Explore solutions
Several directions compared before committing to one.Options compared before committing.
What I do
Wireframes, Pattern options, Trade-offs
UI design & systems
04Design the experience
Clear, consistent UI built on the product’s design system.Consistent UI on the design system.
What I do
High-fidelity UI, Components, States
Test the experience
05Prototype & validate
Flows tested against real situations (errors, empty, permissions), not just the happy path.Tested beyond the happy path.
What I do
Prototypes, Scenario walkthroughs, State reviews
Feedback & refinement
06Review & iterate
Review, take feedback, and revisit decisions when constraints change.Feedback in, decisions revisited.
What I do
Design reviews, Iterations
Development & delivery
07Handoff & collaborate
Dev-ready handoff, then I review the build until it matches.Handoff, then build review.
What I do
Handoff, Specs, Implementation review

What makes my approach different

Four habits that show up in every project.

01
Systems, not screens.
How features connect matters more than any one page.
02
Explore before committing.
The first idea is rarely the best one.
03
Real product behaviour.
Errors, costs and status states, not just the happy path.
04
Collaborate and iterate.
Reviews and feedback are part of every project.