Finer DesignStudio
CollaborateStart a projectStart
All insights

Strategy14 Oct 20262 min read

What a brief needs to prove before anyone starts drawing

Most briefs describe what a client wants built. Fewer test whether building it is the right answer at all — notes on the question that should come first.

Most briefs arrive as a list of things to build: a floor area, a number of rooms, a budget, a date. That list is useful. It is also, very often, an answer to a question nobody has written down.

Before we draw anything, we try to find that question. Not to second-guess the client, who usually knows their situation far better than we do, but because a building, a product or a plan is an expensive way to find out you solved the wrong problem.

Three things worth proving first

The first is the need itself. What is happening now that should not be, or not happening that should? A request for more office space can be a request for more desks, or a sign that the existing space works badly. Those lead to very different projects.

The second is the measure. If the project succeeds, what will be different in a year, and how would anyone know? A brief that cannot name its own outcome tends to get judged on the renders instead.

The third is the constraint that actually binds. Every brief lists constraints; usually only one or two of them decide the shape of the answer. It might be the site, the money, the programme, or the people who will run the place afterwards. Finding which one matters most, early, saves a great deal of redrawing later.

Why it is worth the time

This stage can feel slow from the client's side of the table. There are no drawings to look at, just questions and conversations. But it is the cheapest point in the whole project to change direction. A changed assumption costs an afternoon now; the same change after approvals can cost months.

It also makes the later work faster. When everyone agrees on what the project is for, design reviews stop being arguments about taste and become checks against a shared goal. Decisions get easier to make, and easier to defend.

What we ask for

In practice we ask for very little at the start: an honest account of why the project exists, who it is for, and what would make it a disappointment. Sketches, site photos and half-formed ideas all help. The brief that comes out of those conversations is usually shorter than the one that went in, and much clearer about what it is trying to prove.

Studio Notes