The Myth of the ‘Perfect Brief’
- Bart Kolosowski
- Jan 19
- 4 min read
Updated: Feb 16
If you have ever been involved in a residential renovation or a new build, you’ve likely experienced that strange, drifting sensation where the project you are discussing in month twelve feels fundamentally different from the one you imagined in month one.
Usually, when a project starts to bloat, when the design becomes more complex, the timeline stretches, and the budget begins to feel like a work of fiction, we blame "changing our minds." We tell ourselves that the brief just wasn't "perfect" yet.
But the reality is more structural than that. The problem with residential projects isn’t that briefs aren't perfect, it’s that many projects start with no meaningful brief at all. Or, perhaps more accurately, they start with a brief that is informal, optimistic, and entirely disconnected from financial reality.
We explored this exact problem in more depth in Episode 1 of The Home Project Podcast, where Tina Patel and I talk through why so many residential projects start misaligned before a single drawing is produced. https://www.thehomeproject.co.uk
THE HANDSHAKE AND THE PINTEREST BOARD
On many small to medium residential projects, the "briefing" process is dangerously conversational. For example, a client appoints an architect based on a handful of loose ideas, a collection of inspiration images, and a set of unverified assumptions about what things cost and how long they take.
The architect, eager to begin, prices their fees based on an assumed scope and a perceived level of complexity. They look at the house, hear the client’s aspirations, and provide a fee proposal.
The issue? Neither side has properly tested the foundations of that agreement.
This creates a structural misalignment from day one. The client thinks they have bought a specific outcome, the architect has priced for a specific amount of work. Because these two things haven't been explicitly reconciled against a hard budget constraint, the project begins its life on a fault line.
WHEN "SIMPLE" BECOMES BESPOKE
In the absence of a formal, written baseline, the design process becomes a series of additive decisions.
Without a reference point to look back at, scope quietly expands. What started as a "simple extension" gradually evolves into a bespoke architectural intervention.
This evolution happens in small, reasonable increments. A larger window here, a more complex roof detail there. Because there is no "Version 1.0" of the brief to compare these changes against, the "simple" project slowly transforms into something far more demanding.
If a budget was discussed in those early meetings, it is often treated as a fixed belief, a hopeful number, rather than a tested constraint. It isn't sense-checked against the growing scope, and it certainly isn't revisited every time a new design feature is added.
By the time the project reaches a stage where costs are properly tested, usually at tender the design is "emotionally locked." The client is in love with the scheme, the architect has spent their fee designing it, and there is no practical way to rewind the clock to what was originally agreed.
THE COST OF SUBJECTIVITY
This is how projects bloat, and it is how the relationship between client and consultant begins to fray.
Architects find themselves absorbing hours of unpaid redesign work to try and bring a project back into budget. Clients feel misled, wondering how a project that "seemed fine" suddenly became unaffordable.
The tragedy is that, usually, no one has acted in bad faith. The architect wasn't trying to over-design, the client wasn't trying to over-spend. They simply lacked a baseline.
A brief’s real purpose is not to be a rigid set of instructions that can never change. Its purpose is to:
Define exactly what the architect is being appointed to do.
Align that scope with a realistic, market-tested budget range.
Create a baseline that can be referred to as decisions evolve.
Without that baseline, every conversation about money or time becomes subjective and emotional. Instead of saying, "This change moves us away from our agreed baseline of X," the conversation becomes a retrospective argument about what was "implied" or "understood" at the start.
PATTERNS, NOT THEORY
In our podcast discussion, Tina and I noted that this isn't a theoretical problem, it is a pattern we see repeatedly across the industry. It’s the "silent killer" of residential architecture.
When you start without a formal brief that links scope to budget, you aren't just being "flexible" or "creative." You are essentially starting a journey without a map, assuming that you’ll figure out the destination and the fuel costs somewhere along the way.
The "Perfect Brief" is a myth because residential projects are, by nature, a process of discovery. You find out what you really want through the design process. However, that evolution needs a reference point. It needs a "Brief 1.0" that everyone signed up to, one that was explicit, aligned, and real.
REFRAMING THE START
Residential projects don’t unravel because the requirements change. They unravel because there was nothing solid to change from.
If your project feels like it is drifting, or if the costs are starting to feel disconnected from the drawings, don't look at the latest set of plans. Look back at the beginning. If you find that the project started on a handshake and a dream, without a formal alignment of scope and budget, you’ve found the root of the problem.
A brief doesn’t need to be a hundred-page document. It doesn't need to be perfect. But it does need to be a clear, written agreement that acknowledges the reality of the budget.
Without that, you aren't managing a project; you're just waiting for the misalignment to become expensive.
Comments