Research is not collecting answers. It’s learning how people think.
When users describe a problem, they usually talk about the symptoms — not the cause. They’ll say “this is confusing,” but what they often mean is “this doesn’t match how I expected it to work.” Good research is noticing that gap.
The smallest moments reveal the biggest friction.
I’ve learned to watch for micro-signals: a pause before clicking, scanning the same area twice, switching between two tabs repeatedly, or asking the same question in a different way. Those tiny moments tell you where the experience is breaking.
Assumptions are everywhere (and research brings you back to reality).
Teams often build features based on internal logic — what makes sense to the product, the org, or the roadmap. Users don’t care about the structure behind the scenes. They care about finishing the job. Research is the fastest way to align the product with real-world behavior.
Users don’t always want “more features.” They want less effort.
A lot of “feature requests” are actually requests for clarity. Sometimes the right solution is not adding something — it’s removing steps, making labels obvious, or guiding users through decisions.
Good research builds empathy. Great research builds judgment.
Empathy helps you understand. Judgment helps you decide. Over time, after seeing patterns across users and workflows, you start predicting friction before it happens. Not guessing — recognizing.
How I keep research practical
- Start with the job: “What are you trying to get done today?”
- Look for workarounds: shortcuts and manual steps reveal product gaps.
- Listen for uncertainty: “I think…” or “maybe…” usually points to unclear UI.
- Validate with behavior: what people do matters more than what they say.
- Map the workflow: the pain is often between steps, not inside one screen.
Closing thought
Research stops being something you do at the beginning. It becomes how you see products: where people hesitate, where trust breaks, where effort increases. Once you start noticing those signals, you can’t unsee them — and your design decisions become sharper.