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

Why do we keep building before we know anyone wants it?

Your team agrees the idea is good. That agreement is not evidence. It is comfort dressed as consensus. You built together, argued together, shipped together. None of that proves a stranger wants what you made. This is not a planning problem. It is a courage problem. Asking a stranger 'would you pay for this' risks a no. Building in a room with people who already like you risks nothing. So you choose the safer work and call it progress. What is in your power is small and exact. Talk to someone who is not on your team, before you build the next thing. Do it this week. Not the whole plan — one conversation.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
Some to learn
1:1 with AureliusWith others (a Pod)
Some one-to-one
Practise with peers
The core failure is a habit of avoidance, not a gap in method, so most of the work is behavioral practice, with a smaller share of teaching on how to test an idea cheaply.
How the two dials adapt to you →
What’s really going on

You build because building feels like progress. Asking feels like weakness. Reverse the order. Before you write one line of code, get one stranger to say yes to the problem. Choose the question over the tool. That is the whole fix.

🔒 What you’ll build togetherUnlock by starting
A moveBefore the next build, assign one teammate to talk to five people outside the group — this week, not after launch.
A moveWrite down the assumption you are most afraid to test. Test that one first, not the easy one.
A moveReplace one team meeting with a call to a stranger. If you cannot get one, that itself is the answer.
A moveSet a rule: no code, no design, until someone outside the room has said yes to the problem out loud.
A moveWhen someone says 'we already know people want this,' ask them: who, exactly, and when did they say so.
PractiseThe Stranger Test · a Pod of 4 · 30 min

What changes unlock by starting

  • You catch a bad idea before it costs you months, not after.
  • Your team argues less about opinions and more about what people actually said.
  • You build fewer things, but more of them get used.
  • You stop mistaking your own excitement for someone else's need.

Related problems

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.