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

Why do my questions never get me the real requirements?

You ask. They answer. You build. It is wrong. This has happened before, and you still do not know why your questions keep missing the real thing underneath. Here is the honest answer: most people cannot tell you what they need in words. They can only react to something concrete in front of them. An open question gives them nothing to react to, so they give you a vague answer, and you accept it because asking a third time feels like an insult to their intelligence or yours. This is not a knowledge gap. You know how to ask questions. What you lack is the will to turn a question into a claim — to say "I think you need this" and risk being wrong in front of them. That risk is the whole job.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The person already knows how to ask questions; what they need is practice replacing open questions with testable claims, which is a behavior to drill, not a concept to learn.
How the two dials adapt to you →
What’s really going on

You are not short on questions. You are short on nerve. Open questions let people stay vague, and you accept the vague answer because pressing further feels rude. Stop asking what they need. Tell them what you think they need, and make them correct you. Correction reveals the truth that politeness hides.

🔒 What you’ll build togetherUnlock by starting
A moveBefore your next conversation, write one sentence stating what you think they need. Bring that sentence, not a question.
A moveReplace 'What do you need?' with 'I will build X so it does Y — tell me where that is wrong.'
A moveAsk for an example of the finished thing. A description hides disagreement; an example exposes it.
A moveWhen someone says 'it depends,' do not nod. Ask 'depends on what, exactly' and wait for a specific answer.
A moveAfter each conversation, name the one assumption you trust least. Go test that assumption before you build anything.

What changes unlock by starting

  • You stop discovering missing requirements after the work is done instead of before.
  • Your conversations get shorter, because you lead with a guess instead of an open question.
  • People correct you faster and more honestly, because disagreeing with a claim is easier than inventing an answer.
  • You build the wrong thing less often, and you notice sooner when you have.
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.