top of page
Scope problem
Monitor & ITERATE

Design Approach

Lean UX framework

Scope the problem

Before jumping into solutions, we'll cross-compare data from previous resources:

  • Past research documentation

  • Customer surveys

  • Heat maps, user-behavior recordings

  • Analytics, funnel behavior

  • Interviews with stakeholders who have regular customer contact, Subject Matter Experts (SMEs) and, of course, the customers themselves

Brainstorm & sketch

Hypothesis Statement

During the exploration and planning stages, we'll collect user stories and quotes gathered from the research stage to create applicable elements to present in a research report. Some of these story-telling elements include: 

  • Personas or Jobs-To-Be-Done

  • Customer and/or user journey

  • Information architecture & UX flows

At this stage, we use the low-fidelity wireframes to discuss the concept with Product Managers and Developers and Clients.

Mockups & Prototypes

In collaboration with Product Managers, we define hypotheses to communicate the user needs and product problems to C-levels on what we are trying to accomplish and why.

ux flowchart

Designing solutions

After collecting feedback from stakeholders like Product Managers, Designers, Developers and cross-functional partners in other departments, UX creates scenarios, tasks and experiences for usability testing.


By gathering insights early and often, we're able to keep ourselves honest when designing solutions –we understand the product expectations better, and create alignment within the team.

Depending on how mature the solution is, we use one of these methods to conduct usability testing.

  • Generative / exploratory testing​

  • Comparison testing​

  • Assessment / acceptance testing​

  • Evaluative testing

Feedback Loop

Implement & validate

Prior to implementation and after, we collaborate with the Product Manager to define the metrics we'll track in order to define the success or failure of a solution.


If applicable, we also align on the research strategy for acceptance testing. Then, follow-up sessions are scheduled to write scripts/surveys in order to understand why the solution(s) were accepted by the users.


To validate a solution, myself and the Product Manager will monitor applicable data like funnel behavior, clicks, page views and feature performance via A/B testing etc.


To understand why a solution out performed others, we look at...

  • Usage data across the customer journey

  • Customer surveys

  • Interviews with stakeholders who have regular customer contact, Subject Matter Experts (SMEs) and, of course, the customers themselves

bottom of page