Skip to content
Anchor
All posts

What engineers ask for when they ask for 'more detail'

Almost never more words. Usually one of five specific missing things.

Ilan Weiss6 min read

'Can you add more detail?' is the most misleading piece of feedback a spec receives, because the natural response is to make it longer, and length is almost never what was missing.

What is usually meant

  • The failure case — what happens when the happy path does not happen
  • The boundary — how many, how long, how often, and what happens at the limit
  • The authority — who decides this if we disagree during implementation
  • The precedent — is this consistent with how we did the same thing elsewhere
  • The reason — because a requirement whose purpose is legible can be implemented intelligently when reality differs

Why the request comes out vague

Because the gap is only visible from inside the implementation. The engineer knows something is missing before they can name it, and 'more detail' is the honest shape of that feeling. The productive answer is not to write more. It is to ask which of the five is missing.

A specification is finished when the next question is about priority, not about meaning.

ResearchRequirementsCollaboration

Stop writing PRDs without understanding the product.

Anchor reads your interviews, tickets and docs first — then writes, citing every line.