User research is the discipline of being humble about your own assumptions. Interviews, diaries, observation, surveys — methods for replacing what you imagine with what you have actually seen.
In plain language
In product and design, this term is part of the language teams use to plan, sketch, and refine what users actually see. User research is the discipline of being humble about your own assumptions. Interviews, diaries, observation, surveys — methods for replacing what you imagine with what you have actually seen. If you are new to the field, the simplest mental model is this: talking to and observing the people you build for. Read it once with that frame in mind, then come back and read it again — that is usually enough for the rest of the entry to make sense.
An everyday picture
Think of User Research as a small habit a team agrees to keep. The single act is tiny; the value comes from everyone doing it the same way, the same week, every week.
Where it shows up
User Research sits inside the everyday rhythm of building software: planning, reviews, the small decisions that pile up between releases. Done well, it shows up as a calmer week; done badly, it shows up as rework.
A small example
Imagine the scene above. The role User Research plays is the one its blurb describes — Talking to and observing the people you build for. When a new app feels obvious the first time you use it, ideas like this are part of why nothing got in your way.
Common misunderstanding
One line to take with you
User Research is a habit. The first time costs the most; every time after that is mostly muscle memory.