How We Brief Designers Without Killing the Idea

Most briefs are written to prevent mistakes, not to invite ideas

A typical creative brief reads like a checklist of things that must not go wrong: brand colors, required elements, dimensions, deadlines. All necessary. None of it actually tells a designer what problem they're solving or why it matters to the person on the other end. So they default to solving the checklist — and checklists rarely produce anything memorable.

Replacing instructions with context

We rewrote our brief template around one question: what does the audience currently believe, and what do we need them to believe instead? Everything else — tone, format, constraints — gets framed as context for solving that shift, not as a list of boxes to tick.

It's a small reframe with a large effect. Designers stop asking "did I follow the brief correctly?" and start asking "did I solve the actual problem?" — which is a far better question to be answering.

The best ideas usually arrive sideways

Some of our strongest work has come from a designer noticing something the brief didn't ask about, because they understood the underlying problem well enough to spot an angle nobody had written down. That only happens when a brief leaves room for it. A document that explains everything tends to invite nothing.