top of page

The Cost of Committing Before You Know Enough

  • Writer: Bart Kolosowski
    Bart Kolosowski
  • Feb 16
  • 5 min read

In the world of high-end residential development, there is a pervasive myth that progress is synonymous with speed. We measure the health of a project by how quickly the drawings are produced, how fast the planning application is submitted, and how soon we can get a spade in the ground.


But there is a hidden friction in this rush to progress. Projects rarely get into trouble because the design is moving forward, they get into trouble because design decisions are treated as final before the right people have had the chance to test them together.


When we lock in solutions before we truly understand their implications, we aren’t just making progress, we are accumulating design debt that must eventually be paid back in the form of compromises, delays, and unexpected costs.


THE ILLUSION OF PROGRESS: WHEN OPTIONALITY VANISHES

Typically, a project arrives on a specialist’s desk with a largely fixed architectural solution. The structural design is well progressed, the internal layouts are set, and the key assumptions are already baked into the DNA of the building.


At this stage, the fundamental question has shifted. We are no longer asking, “what is the best way to achieve the client’s vision?”  Instead, we are asking, “How do we make this specific design work?”


By the time the conversation reaches this point, optionality is gone. The project has hardened. If a Quantity Surveyor (QS) or a specialist consultant identifies a more efficient way to frame a floor or a more cost-effective method of waterproofing a basement, it is often too late to implement it without causing a cascade of redesigns. The cost of changing a line on a page during the concept stage is pennies, the cost of changing a steel beam that has already been coordinated with the HVAC system is thousands.


TESTING SOLUTIONS, NOT JUST PRICING THEM

The traditional sequence of residential design often follows a linear, siloed path: architecture first, then structure, then cost, and finally, specialist systems. The problem with this relay race approach is that the person holding the baton at the end is forced to run in whatever direction the previous person chose, whether it’s the most efficient route or not.

When a QS and key consultants are involved earlier, the dynamic shifts from reporting on a design to stress-testing it.

Early involvement allows for a constructive challenge of assumptions. Often, relatively modest changes in construction methodology, sequencing, or the approach to specification can deliver the exact same aesthetic and functional outcome for the client, but with significantly lower risk and better value for money.


This isn’t about redesigning or value engineering (which is often just a euphemism for cutting quality late in the day). It’s about ensuring that a decision is only made final once its buildability and financial implications have been validated by the people who will actually have to deliver it.

 

THE PROBLEM OF DISCONNECTED PROGRESS

Coordination is often the first casualty of project pressure. Architectural and structural designs frequently move ahead at pace because they have to hit planning deadlines or building control milestones.


Meanwhile, secondary design elements, lighting, AV, automated blinds, and specialist climate systems, are deferred. They are seen as extras or finishing touches that can be figured out later.


In reality, these elements are anything but secondary. They materially affect the thickness of ceiling voids, the routing of services through structural members, and the spatial coordination of the entire home. When these specialists are finally brought into the conversation, they find themselves in a straight jacket. They are forced to work around fixed structural decisions rather than helping to shape them.


The result isn't just a higher bill for the specialist installation, it’s a series of compromises that affect the final performance of the house. You end up with lowered ceilings, awkward bulkheads, or compromised acoustics, not because of incompetence, but because of disconnected progress.


THE ROLE OF THE BRIEF: CREATING PRODUCTIVE CLARITY

It is a common misconception that you need a perfect or 100-page brief before you can start collaborating. In fact, waiting for perfection is just another way of delaying the right conversations.


Early collaboration only requires enough clarity to know:

  1. What the project is trying to achieve (the core objectives).

  2. What the realistic budget envelope is.

  3. Which specialist disciplines will materially influence the outcome.


The brief’s job is to provide enough of a baseline so that when consultants sit in a room together, their thinking is focused. Without this baseline, early involvement becomes an academic exercise rather than a productive stress test.

A good brief defines the what so the collective expertise of the team can figure out the how.

THE SITE IS NOT A DESIGN STUDIO

There is a powerful, almost magnetic pull toward starting on-site as early as possible. There is a belief that moving earth is the only way to ensure a project finishes on time.


However, when unresolved design decisions move onto the site, the site becomes the place where the design is finished. This is the most expensive design studio in the world. When a contractor is standing there waiting for a detail to be resolved, or when a specialist system won't fit into a pre-cast void, the project slows to a crawl.


Spending more time aligning decisions and knowing enough before the contract is signed almost always leads to a faster overall delivery. A project that pauses to think in month three will almost always finish ahead of a project that rushed into month six with unanswered questions.


A REFRAME: WHEN IS A DECISION "FINAL"?

To avoid the trap of premature commitment, we need to change how we view the design process.


Design is not a series of checkboxes to be ticked off as quickly as possible. It is a process of gathering enough information to make an informed commitment. A decision should only be treated as final once:

  • The right disciplines have had a chance to contribute.

  • The structural and financial implications are understood.

  • Viable alternatives have been explored and discounted.


The early stages of a project should be used to create optionality and understanding, not to remove them. By keeping the design liquid for just a little longer and ensuring the right people are in the room while it is, we protect the project from the friction that usually bogs it down later.

Projects don’t struggle because there are too many cooks or too many consultants involved early on. They struggle because the right people are involved too late, after the decisions have already hardened and the path has been set.

The cost of committing before you know enough isn't just a line item on a budget. It is paid in the frustration of redesigns, the stress of mid-build delays, and the lingering sense of what if regarding the project’s lost potential.


Real progress isn't just about moving forward, it’s about moving forward with the certainty that you’re headed in the right direction.

Comments


bottom of page