My Process
Lo-Fi to Hi-Fi
Make Better Decisions, Reduce Risk, and Deliver the Best Possible Outcome
Great design is not about jumping to the first solution. It is about reducing uncertainty and making informed decisions at every stage. My process follows five flexible phases: understand the problem, turn research into direction, explore possible solutions, create the experience, and improve it through testing and observation.
Throughout the process, I collaborate with product partners, designers, developers, and other stakeholders to determine how we might best balance user needs, business goals, and technical realities. The process can guide a new product, feature, or redesign, while scaling to fit the time and resources available
Not every project requires every phase at full depth. Sometimes there is time for extensive research, exploration, and testing. Other times, the available time or budget calls for experience, informed judgment, and a well-aimed shot from the hip. The goal is to apply the right amount of process to meet the project’s needs.
1. Research
Fully Understanding the Problem
Exceptional user experiences begin with a shared understanding of business goals, user needs, and technical realities. During this phase, I gather what is known, investigate what is not, and challenge assumptions to fully understand the problem before trying to solve it.
Considerations
- What are we building—and why?
- Who are we building it for?
- What do users need, want, and expect?
- Who are the subject-matter experts?
- What can we learn from competitors and similar products?
Potential Deliverables
Collaboration
Research Alignment
The team reviews what we’ve learned, challenges assumptions, and fills in important gaps. The goal is to build a shared understanding of the problem, the user's wants and needs, business goals, and any known constraints.
Key Collaborators
- Product
- Design
- Engineering
Alignment
- User and Business Needs
- Desired Outcome
- Technical Platform
2. Assimilate
Turn Research Into Direction
When an experience feels clear and intuitive, it is rarely a coincidence. During this phase, I turn discovery into direction by establishing the UX strategy, defining the product’s scope, organizing its information and functionality, and mapping the paths users will take through the experience.
Considerations
- What belongs within the project’s scope?
- What information and functionality do users need?
- How should information be organized and prioritized?
- What requirements, and constraints exist?
Potential Deliverables
Collaboration
Strategy Alignment
Together, we turn what we’ve learned into a focused “How might we best?” challenge. We decide what matters most, what belongs within the project’s scope, and which direction best balances user, business, and technical needs.
Key Collaborators
- Product
- Design
- Engineering
Alignment
- Problem Statement
- Product Priorities
- Scope
- Bandwidth
3. Ideate
Everything Starts With a Sketch
This is where strategy begins to take shape. I explore a wide range of ideas quickly, focusing on structure, hierarchy, content, and interaction before visual polish. The goal is quantity over perfection: encourage ambitious ideas, build on the thinking of others, gather feedback early, and stay unattached to any single solution.
Considerations
- What outcome are we designing for?
- Which patterns will feel familiar to users?
- How many approaches can we explore?
- Can we deliver more value with less complexity?
Potential Deliverables
Collaboration
Design Prep
Before investing in detailed visual design, as a team we compare the strongest concepts, review key interactions, and gather feedback. This helps confirm that the proposed solution is useful, understandable, and technically feasible.
Key Collaborators
- Product
- Design
- Engineering
Alignment
- Functionality
- Content Requirements
- Technical Feasibility
4. Create
Where the Experience Comes to Life
I turn the selected direction into polished interfaces that bring together visual hierarchy, content, brand, accessibility, and responsive behavior.
Great interfaces do more than look good. They communicate what is happening, what has changed, and what users can do next. I define the feedback, states, transitions, confirmations, and errors that make each interaction feel deliberate and predictable.
Considerations
- Is the interface clear, consistent, and on-brand?
- Does the visual hierarchy guide users effectively?
- Does every action provide meaningful feedback?
- Is the experience responsive and accessible?
Potential Deliverables
Collaboration
Build Prep
Before development begins, design and engineering review the final screens, interactions, responsive behavior, design-system updates, assets, and specifications. The goal is to answer open questions and give developers what they need to build with confidence.
Key Collaborators
- Product
- Design
- Engineering
- QA
Alignment
- High-Fidelity Designs and Prototypes
- Design System Additions
- Assets and Specifications
5. Test, Observe, Refine
Design Is Never Really Done
A design can look right and still miss the mark. Testing and observation show how well it works for real users, where they struggle, and what needs to be clarified, corrected, or improved.
I use those findings to refine the design, verify the implementation, and prioritize future improvements in collaboration with product and engineering.
Considerations
- Can users complete key tasks successfully?
- Does the final product match the intent?
- What should be improved now or explored later?
Potential Deliverables
Collaboration
Launch Review
Before release, the team reviews the completed experience, testing results, and any remaining issues. Together, we decide what must be addressed now, what can follow later, and utimately whether the product or feature is ready to launch.
Key Collaborators
- Product
- Design
- Engineering
- QA
Alignment
- User Testing Findings
- Required Design Revisions
- Future Improvements and Features