"User-centered design" is in almost every job description and design principles deck I’ve read in the last ten years. Nobody argues against it, and nobody defines it. At this point it means about as much as "we care about quality".
It used to mean something quite radical. When Don Norman and others were pushing it in the 80s, products were built around what was technically elegant, and people were expected to adapt. Saying "study people first and design around how they think" was a real fight.
Then it turned into a checklist, and these days it’s mostly something you tick before doing what you were already going to do.
Research often validates decisions that were already madeWhat user-centered design claims to do, and what often happens instead
As described
Research informs decisionsInsights gathered before direction is set
Users define the briefProblems found by watching people
Findings change plansContradictory data prompts scope revision
Validation is genuineTesting can kill a direction
As practised
Research validates decisionsDirection already chosen: evidence assembled afterward
Brief defines the researchQuestions written to support a predetermined answer
Findings confirm the roadmapContradictory data deprioritised or reframed
Validation is theatreTesting confirms what the team already believed
Designers often arrive after the strategy is set and get asked to validate it, so this is about timing more than character.
The uncomfortable part is how often research is used to confirm decisions instead of challenge them. It gets commissioned after the direction is set, and designers are brought in to validate rather than question.
The version worth keeping is a simple question: what did we change because of what we learned? If the wireframes were finished before the interviews happened, the honest answer is nothing, and the research was decoration.
Do
Each finding names what it changed
Study
Expense approvals, 8 interviews with finance managers
Readout
10 March 2025
Wireframes signed off
21 March 2025
Managers approve on their phone between meetingsHeard from 6 of 8Outcome: Changed
Nobody opens the policy panelHeard from 7 of 8Outcome: Changed
Approving in bulk feels riskyHeard from 5 of 8Outcome: Changed
A few want a weekly summary emailHeard from 2 of 8Outcome: Unchanged
Press What changed? on a finding to see its decision record.
Before
Approve and Reject sat below the receipt images.
After
They stay fixed at the top of the phone layout.
Decided
12 March 2025, design and product
Before
Spending limits were in a separate policy panel.
After
The limit shows next to any amount that goes over it.
Decided
12 March 2025, design and product
Before
Approve all ran straight away.
After
Approve all shows the total and the number of claims before you confirm.
Decided
13 March 2025, design and engineering
Outcome
Unchanged
Why
Two of eight asked, and both already export a weekly report.
Revisit
After launch, if more people ask.
Watch it run, then press What changed? on any finding.
Illustrative example
Don’t
The research decorates a finished direction
Study
Expense approvals, 8 interviews with finance managers
Readout
24 March 2025
Wireframes signed off
14 March 2025
Mobile matters14 notes
Trust and transparency11 notes
Efficiency is key9 notes
Policy pain points8 notes
Press What changed? on a finding to see its decision record.
Decision
No decision is linked to this theme.
Readout
24 March 2025
Signed off
14 March 2025, 10 days earlier
Decision
No decision is linked to this theme.
Readout
24 March 2025
Signed off
14 March 2025, 10 days earlier
Decision
No decision is linked to this theme.
Readout
24 March 2025
Signed off
14 March 2025, 10 days earlier
Decision
No decision is linked to this theme.
Readout
24 March 2025
Signed off
14 March 2025, 10 days earlier
Watch it run, then press What changed? on any finding.
Illustrative example
Most research artifacts change very littleWhat each one produces, and what it actually changes
User interviews
Quotes that support the briefUsually nothing. They illustrate a deck
Personas
Posters on a wall, slides in a deckRarely consulted when actual decisions are made
Usability tests
A reel of users clicking through screensMinor wording fixes, rarely touches structure
Journey maps
A comprehensive emotional arc across touchpointsShared once, then lives in a Figma file nobody opens
What I’d want to know is what went differently because the research happened.
You can see this in portfolios too. Lots of them show the personas and the affinity maps. Very few show a decision that went differently because a real person said something inconvenient. That’s the bit I’d want to read.
Tamara Milakovic is a senior product designer specialising in B2B SaaS, design systems, and the decisions upstream of the brief.
References
Norman, D. & Draper, S. (Eds.) (1986). User Centered System Design: New Perspectives on Human-Computer Interaction. Lawrence Erlbaum Associates.