From understanding
to implementation.
A practical, adaptable approach. The depth and order of each stage depend on the product, the evidence available, and the team’s constraints. The goal is shared clarity, not process for its own sake.
01 / Understand
Establish business context, intended users, existing workflows, and constraints through stakeholder conversations, subject matter expert interviews, product review, and requirements clarification.
Establish business context, intended users, existing workflows, and constraints through stakeholder conversations, subject matter expert interviews, product review, and requirements clarification.
02 / Define
Translate available information into a clear problem statement, prioritized needs, and workflow requirements. Make the expected experience and unresolved questions explicit.
Translate available information into a clear problem statement, prioritized needs, and workflow requirements. Make the expected experience and unresolved questions explicit.
03 / Explore
Explore information architecture, navigation, and interaction alternatives. Evaluate usability, technical feasibility, consistency, and business needs rather than committing to the first plausible layout.
Explore information architecture, navigation, and interaction alternatives. Evaluate usability, technical feasibility, consistency, and business needs rather than committing to the first plausible layout.
04 / Design
Develop wireframes, prototypes, visual design, responsive behavior, and reusable patterns. Make important decisions and trade-offs visible, especially when simplifying a complex task.
Develop wireframes, prototypes, visual design, responsive behavior, and reusable patterns. Make important decisions and trade-offs visible, especially when simplifying a complex task.
05 / Validate + refine
Review with relevant stakeholders and subject matter experts. Resolve ambiguities and usability concerns. Formal user testing is used only when the project supports it; stakeholder review is not presented as a substitute.
Review with relevant stakeholders and subject matter experts. Resolve ambiguities and usability concerns. Formal user testing is used only when the project supports it; stakeholder review is not presented as a substitute.
06 / Specify + collaborate
Prepare interaction details, component guidance, and responsive requirements. Collaborate with developers on implementation questions and review the delivered experience against the intended design.
Prepare interaction details, component guidance, and responsive requirements. Collaborate with developers on implementation questions and review the delivered experience against the intended design.
07 / Evaluate + improve
Where the project allows, review implementation, collect feedback, and identify opportunities for subsequent iterations. Distinguish available evidence from assumptions about impact.
Where the project allows, review implementation, collect feedback, and identify opportunities for subsequent iterations. Distinguish available evidence from assumptions about impact.