I use research throughout the process, from understanding the problem early on to testing ideas and informing product decisions.
Define what the team needs to learn and what decisions the work should support.
Select methods that match the problem, constraints, and level of uncertainty.
Turn raw inputs into patterns teams can understand and act on.
Translate research into direction that shapes product, design, and tradeoffs.
My research work spans both discovery and validation, depending on the decision at hand.
I choose methods based on the decision at hand, not the process checklist.
Research matters when it changes what the team does. I use findings to shape flows, information architecture, interaction models, priorities, and sometimes the problem definition itself.
At its best, research becomes a shared reference point that grounds discussions across product, design, engineering, and marketing, ensuring findings influence outcomes, not just artifacts.
I am most effective when research is used to:
In these environments, research helps the team make a better-informed call and keep moving.