We once agreed on three creative routes for a cover and a genuinely clear brief for the concept. Thirty colourways later, we worked out what we'd actually missed: not the concept, not the routes, but any shared idea of when refinement should stop and sign-off should begin. Every version was a real improvement on the last. That was exactly the problem — there was no agreed point at which ‘better’ stopped being the goal and ‘finished’ took over.
Every design brief defines scope — how many concepts, what they're for, roughly when they're needed. Far fewer define the thing that actually determines how smoothly a project runs: what ‘done’ looks like, and who decides when you've got there.
Scope tells you what's being made. Expectations tell you how you'll get there together — and that second part is where good projects quietly come apart, usually without anyone doing anything wrong. A designer keeps refining because refining is what they've been asked to do. An editor keeps requesting changes because nothing has told them when to stop. Both are behaving reasonably. Neither is short of talent or judgement. The process just never defined an endpoint.
So a good brief now goes further than most. It specifies the number of concepts before anyone starts designing, not as a ceiling to be defended but as a shared understanding of the shape the process will take. It defines how those concepts get reviewed — one round of open feedback, then convergence, or feedback throughout. It's explicit about who the decision-makers actually are, which sounds unnecessary until you're on a call where three people have three different opinions, and no one present can break the tie. And it says, in advance, when refinement ends and sign-off begins.
This matters more than it sounds like it should for anyone who's watched a revision cycle stretch past where it was ever meant to go. For an art director signing off dozens of covers a season, or a designer whose approval rate and revision count are effectively being tracked as performance metrics, an open-ended process isn't just frustrating — it's the actual mechanism by which good projects go over time and budget. Not because the work got worse. Because nobody agreed what ‘finished’ meant early enough for it to mean anything.
Scope answers what we're making. Expectations answer how we'll know when we've made it. A brief that only covers the first one is only half a brief.