"That's not what I asked for" is almost never a skill problem — it's a briefing problem. A brief that describes outcomes instead of specifics leaves room for the builder to fill in the gaps with their own assumptions, which are rarely yours.
What a real brief includes
- Specific screens and actions — not "manage orders," but the actual list, filters, and buttons a user sees.
- What "done" looks like — a concrete definition, not a feeling.
- What's explicitly out of scope — as important as what's in, and the main thing verbal briefs skip.
- Priority order — if time runs short, what gets cut first, decided in advance rather than in a heated conversation later.
Why this is also what makes a guarantee possible
A guarantee only means something if there's a written scope to measure a deliverable against — which is exactly why we write one before every engagement starts, down to the $200 Starter Sprint.