Everyone wants to get to the making. The brief — the boring document that says what the problem actually is — gets rushed, because it doesn’t feel like real work. That instinct is exactly backwards. A precise brief makes everything after it easier, and a vague one guarantees expensive thrashing no amount of craft can fix. The brief is the hardest part precisely because it’s the part where you have to decide, and everything downstream is just execution of that decision.
Execution is downstream of definition
Here’s the uncomfortable truth: most projects that go wrong didn’t go wrong in the making. They went wrong in the brief — the problem was never actually defined, so every later decision had nothing solid to check against. When there’s no clear problem, “is this good?” has no answer, and teams thrash forever producing competent work that solves the wrong thing.
| A weak brief | A strong brief |
|---|---|
| “Make it modern and clean” | “Help this specific person do this specific thing” |
| No way to tell if a decision is right | Every decision has something to check against |
| Thrashing dressed up as iteration | Iteration that actually converges |
| The problem gets defined by accident, late | The problem is decided up front, on purpose |
| Craft can’t save it | Craft finally has a target |
Why it’s the hardest part
Defining the problem is hard because it forces commitment. A vague brief keeps every option open, which feels safe and is actually paralysis. A sharp brief closes doors — it says this problem, for this person, and not the other twenty you could have chased. That closing is uncomfortable, which is why people avoid it and rush to the making, where the work at least feels like progress. But a beautiful solution to an undefined problem is just expensive decoration.
The same discipline shows up anywhere you’re forced to be precise up front. Defining a data schema makes you decide what a thing actually is before you can store it — I wrote about that in What a JSON File Can Teach You About Discipline — and a brief is the same act aimed at a whole project. Get it right and the making becomes almost mechanical. Get it wrong and no amount of making will rescue it.
How to Proceed
- Before starting your next project, write the brief in one sentence: help who do what. If you can't, you're not ready to make anything yet.
- Delete every vague word ("modern," "clean," "engaging"). Replace each with something you could actually check a decision against.
- Notice the urge to skip ahead to the making. That urge is the trap — the discomfort of the brief is the work, not a delay to it.
- Close some doors on purpose. A brief that keeps every option open hasn't decided anything, which means it hasn't helped.
- When work feels like thrashing, stop and re-read the brief. Nine times in ten, the thrash is a definition problem wearing an execution costume.