My design process
As a hiring manager, when I ask designers what their process is, I get the same answer. First, I start by understanding the problem through research. I define the problem by analyzing research, data, and insights, and then collaborate with my partners to ideate and diverge on a wide range of opportunity statements. I then converge on a single approach that is the optimal solution to this problem. I design the experience with UX flows and UI prototypes. Lastly, I work closely with my partner and the engineering team to deliver a collaborative handoff of design and specs. Easy peasy..And to be fair, I, too, have been faulty in explaining this process.
What most designs show and explain. A linear convergence and divergence process.
What a real design process looks like. A non-linear loop.
The truth is, it's not really a process, but a loose framework. When people refer to a process, it feels so rigid, but really, it's not. I found it best to describe my design thinking process in 4 words.
Breaking down my process
01
Flexible
My approach adapts to the problem, the team, and the constraints. Some projects start with deep research; others begin with a prototype to test assumptions quickly. I’m comfortable moving between discovery, definition, and delivery as needed, rather than forcing work through a rigid sequence. Flexibility allows the team to respond to new information, shifting priorities, and real-world constraints without losing momentum.
02
Quantitative
Design decisions are grounded in data as much as craft. I use qualitative research to understand why users behave the way they do, and quantitative signals to validate where to focus and what to prioritize. Metrics, experiments, and outcomes inform direction, helping ensure design work drives measurable impact, not just polished experiences.
03
Iterative
I treat design as a series of learning loops, not a single moment of clarity. Early concepts are intentionally lightweight, designed to be tested, challenged, and improved through feedback from users, partners, and engineering. Iteration reduces risk, surfaces better solutions over time, and keeps the team aligned as understanding evolves.
04
Outcome
I design toward outcomes, not outputs. Every decision is tied back to a clear user need and a business goal, whether that’s increasing adoption, reducing friction, or enabling scale. Shipping designs doesn’t define success, but by the impact those designs have once they’re in customers' hands.
Bonus word….yes, it's my portfolio, I get a bonus word 😀
05
Scrappy
When needed, I move fast with imperfect inputs. Scrappiness means knowing when high fidelity matters, and when speed, alignment, or validation is more important. I’m comfortable testing ideas with rough prototypes, lightweight research, or partial data to unlock learning early, then investing deeper as confidence grows.