What I Decide Before an Architect Draws the First Plan

A development can look convincing in a rendering before anyone has resolved what it should feel like to live there. The image shows a finished home. It rarely reveals the decisions that will matter most to its owner: what happens on the neighboring parcel, where vehicles arrive, which rooms overlook one another, or whether the terrace is comfortable when the sun moves.

Those are the questions I want in the conversation before the first plan becomes something everyone feels obliged to defend.

Start With What Must Stay

At The Summit on Blue Mountain, we chose nine villas across approximately ten acres. That decision reflects a priority I have written about before: protecting the qualities that make the land worth developing.

A useful brief starts by identifying those qualities. A view corridor may deserve protection. A change in elevation may offer a way to separate homes. Existing vegetation may contribute more to the experience of arrival than something planted later.

The point is to make those priorities explicit. “Respect the site” sounds agreeable in a meeting, but it leaves too much unresolved. Which part of the site? What should remain visible? Where should development stop?

An architect can respond to a clear constraint. A vague aspiration is harder to draw.

Describe an Ordinary Day

A home needs to work through the unremarkable parts of ownership. Guests arrive with luggage. Groceries move from a vehicle to a kitchen. Someone wants to read while others entertain. Maintenance needs to happen while the house is occupied.

I want a development brief to describe those situations alongside its ambitions for architecture.

That does not mean prescribing every room before the architect begins. It means explaining the relationships that matter. The route for servicing a home should be considered alongside the route that makes an arrival memorable. A generous entertaining area should leave room for someone to withdraw.

Give the Team a Hierarchy

Every project contains competing priorities. More glazing may improve a view while making shade harder to resolve. A different building position may simplify access while reducing separation from a neighbor.

The brief should help the team evaluate those choices. If privacy is a defining promise, it needs to carry weight when another option appears cheaper or more visually dramatic.

Without a hierarchy, decisions can drift toward whichever issue is most urgent that week. Over time, the project becomes a collection of individually reasonable compromises.

Let the Economics Test the Brief

Financial discipline belongs in this process from the beginning. A project must be buildable and economically workable.

I see the brief as a way to make that testing more honest. When a proposal requires sacrificing the very qualities that justify it, the team needs to confront that conflict while alternatives remain available.

A good early brief leaves plenty of room for architectural invention. It also gives everyone a common understanding of what success means.

By the time the first plan reaches the table, I want us to know what we are trying to protect, how the place should function, and which compromises would change its character. The drawing can then advance the conversation instead of having to invent it.