HB Thompson Group Project Definition · Architecture · Project Build
Architecture

How Does an Architect Turn Project Definition Into Design?

Henry B. Thompson, Architect

A common picture of architecture goes like this: the client describes the rooms they want, and the architect draws them. In practice, the list of rooms is one of the less difficult parts. The real work is deciding how everything a project has to respond to fits together into a single, coherent thing.

Definition tells the architect what to answer. Design is the answer.

Project Definition establishes what the project needs to accomplish. Defining Place establishes what the architecture should respond to. Architecture is the act of bringing those conditions together into form.

That's the part of the process that's easy to underestimate from the outside. Once a project has been defined, and the thinking about place is in view, there is still a large gap between knowing what a project must respond to and knowing what architectural form that response should take. Crossing that gap is a matter of professional judgment.

Many inputs, one response

People Place Investment Performance Regulation Structure Light Material Priorities A coherent architectural response

Nine kinds of input, each legitimate, each pulling in a slightly different direction.

Each of these is a real and reasonable demand. The people who will use the house have needs. The place has conditions. The project has an investment it can responsibly carry, performance it needs to achieve, regulation it has to satisfy, a structure that has to stand up, light it must work with, materials it will be made of, and priorities that decide what wins when they compete.

No input is the whole answer. And they rarely agree: the best light may not fall where the structure is most efficient, and the room the family wants most may be the one the project investment can least afford.

Interpretation, not translation

Translation would mean converting a client's words directly into drawings. Interpretation means working out what all the inputs imply together, and where they conflict. It tends to involve three kinds of judgment:

Weighing
Deciding which input matters most when they conflict, guided by the priorities the project has established. This is the same decision hierarchy described in What Happens When Everything in Your Project Feels Important?
Reconciling
Finding responses that satisfy more than one input at once, so that a single decision about where a window goes can serve light, view, structure and cost together rather than treating each as a separate problem.
Organizing
Finding a simple underlying logic — how the house sits, how it's entered, how its rooms relate to light and land — that makes many separate decisions feel like one.

Architecture isn't translating a list of rooms into drawings. It's making many demands into one coherent response.

Testing more than one answer

Good judgment isn't a single flash of insight. It usually means exploring more than one possible response and testing each against what the project has defined, including cost, structure and regulation, while those decisions are still information and not yet construction. That's also what lets an owner participate in the decisions that matter, because the alternatives and their consequences can actually be seen.

It's a different activity from the groundwork described in What Does an Architect Actually Do Before Drawing the Design? That work establishes the conditions. This is where they're brought together.

What coherence feels like

When it works, the many decisions in a house feel related: the way you arrive, where the light falls, why a room sits where it does, how the structure shows or hides itself. The decisions reinforce one another, and the place feels as though it belongs together. When that underlying logic is missing, the disconnection can often be felt even by someone who couldn't explain exactly what's wrong.

Asking to see the reasoning

One practical way for an owner to understand an architect's judgment is to ask for the reasoning behind a design: why this form and not another, and whether each major decision can be traced back to something the project defined, such as a need, a condition of the place, or a priority. A design that can explain itself that way has usually done the interpretive work. One that can't may be an attractive answer to a question nobody fully asked.

Want to talk through how your project's conditions could come together?

Discuss Your Project