The quality of the work you get back is set, more than by budget or timeline, by the brief you put in. A vague brief doesn’t buy freedom. It buys a studio guessing, and guessing is expensive for everyone.
What a good brief actually contains
Include these, skip the rest/
- The business decision behind the project, not ‘we need a website’, but what has to be true after it launches.
- Who it’s for, and one real person as a stand-in you can both picture.
- What success looks like, in a number you’ll actually check in six months.
- The three things that must not change, and everything that’s genuinely open.
- Examples of work you admire, and, more usefully, work you hate, and why.
A brief is a decision-making document, not a wish list. Its job is to make the hard calls early, while they’re cheap.
What to leave to the studio
The other failure mode is over-specifying, arriving with the solution already drawn and asking the studio to render it. You hired them for judgement; a brief that pre-solves the problem throws that judgement away and keeps all the risk.
Resist the urge to pre-solve/
- Specify the problem and the constraints, not the solution.
- Name one decision-maker, don’t design by committee in the brief.
- Don’t bury the real goal under fifteen ‘nice to haves’.
- Don’t hide the budget. It’s a constraint, and constraints make better work, not worse.
