UX Process

Clarity before polish.

My process is built for complex problems: understand the people and operating context, frame the right problem, make the workflow visible, test early, and stay involved through implementation and iteration.

See Workflow SystemsView Product Evidence
01 · DISCOVER

Understand people and context

Stakeholder interviews, user interviews, contextual inquiry or shadowing, system/workflow audits, business constraints, technical limitations, success metrics, personas, journey maps, and service blueprints.

02 · DEFINE

Frame the right problem

Synthesize research, align scope and priorities, facilitate story mapping or whiteboarding, define use cases and scenarios, identify opportunity areas, and establish a realistic UX roadmap.

03 · DESIGN

Make the model testable

Sketch workflows and wireframes, build interactive prototypes with Figma or HTML/CSS, apply design-system patterns, collaborate with developers and BAs, and document UI behavior for handoff.

04 · TEST

Validate assumptions

Plan moderated usability tests, create task scenarios and scripts, facilitate remote or in-person sessions, analyze findings, prioritize recommendations, and iterate based on observed behavior.

05 · DELIVER & EVOLVE

Stay through implementation

Support development and QA, address edge cases, polish interactions, gather post-launch feedback, lead retrospectives, and feed reusable patterns back into the broader design system.

Operating principle

Process flexes. Evidence does not.

I do not force every project through the same ceremony. The sequence adapts to risk, ambiguity, team maturity, and what is already known. The constant is evidence: understand the workflow, make assumptions visible, test the risky parts, and preserve design intent through implementation.

What this looks like in practice
  • Workflow maps before screen polish when the system is ambiguous
  • Synthetic sandboxes when production data is confidential
  • Scenario testing for exceptions and edge cases
  • Reusable patterns instead of one-off UI decisions
  • AI used to accelerate analysis, not replace judgment
Tools & Methods

Methods selected by the problem.

Discovery & Research

Interviews, shadowing, surveys, heuristic reviews, workflow audits, stakeholder synthesis.

Design & Prototyping

Figma, whiteboarding, design systems, HTML/CSS prototypes, interaction specifications.

Validation & Delivery

Moderated usability testing, SUS when appropriate, analytics, Jira/Confluence collaboration, dev handoff, QA, pattern libraries.