The intent brief
A reusable framework for getting the real why on paper before anyone opens a tool.
- Guide
- June 2026
- 7 min read
The Intent Brief is a short, structured document that forces the real reason for a project into the open before any design begins. It has five parts: the stated request, the intent behind it, the audience and the feeling, the constraints, and the one sentence everything will be judged against.
Every weak project we have seen started the same way: a crystal-clear deliverable sitting on top of a fuzzy reason. The team knew exactly what to make and never quite agreed on why. The Intent Brief is how we fix the order. Before anyone opens a tool, we write down the why, in a form short enough that nobody can hide behind it.
The five parts
- The request, as stated. The literal thing that was asked for: a site, a logo, a feature. Write it plainly so it stops masquerading as the goal.
- The intent underneath it. The real reason: a market to enter, a perception to change, a decision to make easier. Ask why until the room gets slightly uncomfortable.
- Who it is for, and what they should feel. One audience, one feeling. If you list five of each, you have not chosen yet.
- The constraints. The real ones: budget, timeline, technical limits, things that cannot change. Constraints are not the enemy of the work, they are its edges.
- The one-sentence test. A single line that any later decision can be measured against. If you cannot write it, you are not ready to make anything.
If you cannot write the intent in one sentence, you are not ready to make anything yet.
How to run it
It takes about an hour, not a week. We draft it live with the client, because the act of answering the questions out loud is where the real intent surfaces. The deliverable is one page. The most important line is the one-sentence test, and the client signs off on it. That signature is the quiet hinge of the whole engagement: from here on, the work is measured against a sentence everyone agreed to, not against whoever has the strongest opinion in the review.
What it looks like, filled in
A framework is easy to nod at and hard to use, so here is the shape of a real one, for a B2B fintech that arrived asking for a website redesign. The names are changed and the structure is intact.
- Request, as stated: redesign the marketing site.
- Intent underneath: stop losing enterprise deals at the first impression. The current site reads like a seed-stage startup, and buyers with real budgets do not trust it with their money.
- Who it is for, and the feeling: a risk-averse finance lead at a 500-person company. They should feel that this is safe, proven, and adult, not clever.
- Constraints: ship in eight weeks, keep the existing CMS, no logo rebrand yet.
- One-sentence test: every choice should make a cautious enterprise buyer trust us more, not admire us more.
Look at what that last line does. It settles a dozen arguments before they start. A bolder hero, a flashier animation, a clever headline: each one now has a clear answer. Does it build trust with a cautious buyer, or does it just look impressive to us? The sentence decides, not the loudest voice in the review. That is the whole point of writing it down before anyone falls in love with a pixel.
What it changes downstream
Once the intent is explicit, design stops being a negotiation of taste. Every option has something concrete to be judged against, so reviews get faster and calmer. You are no longer asking whether someone likes it. You are asking whether it serves the sentence you all signed. That is a question with an answer.
The failure mode it prevents
The most expensive thing in this field is beautiful work aimed at the wrong target. It passes every internal review, ships, and quietly fails, because nobody checked the why against reality before pouring craft into the how. The Intent Brief is cheap insurance against the most costly mistake we know: building the wrong thing well.
It is the brief behind the brief, written down and signed. An hour at the start that saves the project at the end. Get the intent on paper first, and the form has something true to follow.
Asked & answered
A short, structured document that captures the real reason behind a project before any design starts. It records the stated request, the intent underneath it, the audience and the feeling, the constraints, and the single sentence the work will be judged against.
A normal brief usually describes the deliverable. An intent brief forces out the why beneath the deliverable, so every later decision has a fixed reference to be measured against instead of being argued on taste.
We draft it with the client in about an hour, and the client signs off on the one-sentence test. That signature is what makes later reviews objective rather than a contest of opinions.