Talk it through with Aurelius
Library›Aurelius›The problem
Aurelius · Work & Leadership
Knowledge + Guidance

Why can't I separate what users say from what they need?

You run the interview well. You ask the questions, you get answers, and the answers feel solid because they are concrete — a sentence you can write down and hand to someone else. That is the trap. The sentence feels like the destination because it is easy to hold. But the user is not reporting their need. They are reporting their best guess at a fix, built from whatever they happened to be looking at when you asked. Their words are a symptom. The need is the task they were trying to finish underneath those words — and they rarely say it plainly, because they are not required to know it themselves. That is your job, not theirs. This is not a trick you learn once and keep. It is a habit you either practice on every interview or lose. Choose to practice it on the next one.

◆ How this problem reads on the two dials
GuidanceKnowledge
Coaching
More to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The gap between stated request and underlying need is a teachable distinction with a method, but it only becomes real through repeated practice on actual transcripts, so guidance carries nearly equal weight.
How the two dials adapt to you →
What’s really going on

A user's words are a guess at a fix, not the need itself. Write down the exact sentence they gave you. Then ask: what task were they stuck on when they said it? That task is the need. Train yourself to chase the task, not the quote.

🔒 What you’ll build togetherUnlock by starting
A moveAfter every interview, write the user's exact words in one column — no paraphrasing.
A moveIn a second column, write the task they were doing right before they said those words.
A moveAsk yourself: what happens if I do nothing about this request? The answer shows you the real stake.
A moveState the need back to the user in one plain sentence and watch whether they correct you.
A moveDiscard any requirement not anchored to a task you actually watched or heard described in detail.

What changes unlock by starting

  • You stop designing solutions straight from quotes.
  • You can state each user's real task in one sentence, without their help.
  • Your discovery notes separate 'said' from 'needed' as a habit, not an afterthought.
  • You notice when you are building for the loudest voice instead of the real one.
One object, two jobs: a public answer to a real problem, and — the moment you start the chat — Aurelius’s live plan for your version of it.