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

Why do teams still build the wrong thing from my spec?

You wrote it clearly. You checked it twice. Still the team built something else. So you decide the spec needs more detail — more diagrams, more edge cases spelled out. This is the wrong lesson to learn. A document cannot ask a question. It cannot see confusion on a face. It cannot notice when someone nods without understanding. You are asking paper to do a person's job. The fix is not a better spec. It is a conversation you keep avoiding — one that belongs before the building starts, not after it fails.

◆ How this problem reads on the two dials
GuidanceKnowledge
More coaching
A little to learn
1:1 with AureliusWith others (a Pod)
Mostly you & the coach
A little with peers
The reframe is quick to state; the real work is building a habit of conversation, which only practice can teach.
How the two dials adapt to you →
What’s really going on

You choose to trust a document over a conversation, and then wonder why the team built the wrong thing. A spec cannot ask a question or read a face. Sit with one person, have them explain it back to you, and fix what confuses them now — before anyone writes code.

🔒 What you’ll build togetherUnlock by starting
A moveBefore you send the spec, sit with one engineer and walk through it line by line. Watch their face, not just their nod.
A moveAsk them to explain back to you, in their own words, what they will build. Their words will show you the gap — yours won't.
A moveFind the sentence in your spec you trust least. Say it out loud to someone else. If it sounds strange, rewrite it now.
A moveCheck in at the halfway point of building, not at the end. Correction is cheap early. It is expensive late.
A moveStop hiding behind 'they should have read it.' Choose to confirm understanding instead of assuming it.

What changes unlock by starting

  • You catch misunderstandings before anyone writes code, not after.
  • The team builds closer to what you meant on the first try.
  • You spend less time lengthening specs and more time confirming understanding.
  • You build the habit of checking comprehension, not just handing over documents.

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.