While I adapt my approach to fit the needs of each project, this is how I typically think through and shape a design. From initial ideas to launch.
Scroll down to learn more.
1
Discovery
2
Definition
3
Ideation
4
Prototype
5
Iterate
6
Handoff
7
Review
Step 1
Discovery
Start by listening.
I start by asking questions. Who are we designing for? What are they trying to do? What’s getting in their way? I dig into user behavior, environmental factors, and emotional signals. The goal is to uncover what’s really going on, not just what’s visible on the surface.
Key Outputs
Stakeholder and user interviews
Behavior and context mapping
Journey maps and pain point summaries
Research-backed hypotheses
Step 2
Definition
Make the problem unmistakably clear.
Once I’ve gathered context, I help distill it into something focused and actionable. What are we solving, and why now? A good definition removes ambiguity, sharpens priorities, and sets a tone for smart, efficient work. If it feels vague, we’re not ready yet.
Key Outputs
Clear problem statements
Success metrics tied to user outcomes
Feature prioritization based on impact
Shared scope and alignment
Step 3
Ideation
Explore different angles.
This is where structure meets creativity. I test different directions, keeping the user’s mindset and emotional state at the center of every concept. The goal isn’t to be clever. It’s to be relevant, intuitive, and respectful of the user’s time and attention.
Key Outputs
Sketches, flows, and exploratory layouts
Interaction concepts grounded in real context
Scenario-driven concept testing
Team workshops and decision points
Step 4
Prototype
Tangible enough to test… rigorously.
Prototypes help bring assumptions into the light. I use them to test not just whether something works, but whether it feels right. Does it guide the user clearly? Does it reduce hesitation? I pay close attention to tone, pacing, and the small moments that often carry the most weight.
Key Outputs
Interactive mid- and high-fidelity prototypes
Complete state coverage (loading, error, success)
Usability testing plans
Cross-team feedback sessions
Step 5
Iterate
Putting the results in practice.
Feedback leads to decisions. I use it to refine structure, language, and interaction patterns, adjusting for clarity, confidence, and speed. I care a lot about how the product handles uncertainty and how it supports people when things don’t go perfectly.
Key Outputs
Finalized designs and component polish
UX copy refinements
Accessibility and responsiveness checks
Updated prototypes for validation
Step 6
Handoff
Passing the baton. Strategically.
I partner closely with engineers to bring the product to life without losing design intent. That means clear specs, documentation, async support, and flexibility when tradeoffs are needed. The goal is simple: ship what we designed, without creating blockers along the way.
Key Outputs
Dev-ready design files
Component specs and interaction notes
Walkthroughs and support during build
QA support and implementation review
Step 7
Review
Reflect. Improve. Process.
After launch, I look at how the product performs—both in metrics and in moments. What confused people? Where did they drop off? What felt effortless? I gather insight to guide iteration and inform future work. Good design is never done. It's constantly improved upon to fit emerging needs.
Key Outputs
Usage data and behavior review
Structured feedback and support logs
Identified opportunities for improvement
Learnings shared with the broader team