Arrive Empty-Handed: The Case for Clients Who Haven't Figured It Out Yet

A common confession opens many first meetings with an architect. Clients apologize before they sit down: We don't really know what we want. We're not creative people. We have a folder of saved photos, but nothing coherent.

There is a persistent myth in American culture that hiring an architect requires arriving with a defined vision — a Pinterest board, a binder of magazine clippings, a sketch on a napkin. It is a myth worth dismantling, because it keeps people out of a process designed precisely for them.

The Architect Is Not a Stenographer

If a client arrived with every decision already made, an architect's job would shrink to drafting — a technical translation of instructions. That is not design. Design begins in the space between what a client says and what a client actually needs.

Consider how a typical first conversation actually unfolds. A couple says they want "an open floor plan." But the architect's real work is asking why. Is it because they entertain often, or because they want to watch children while cooking, or because the previous house felt dark and airless? Each answer leads to a materially different solution — and only one of them involves tearing down walls. The stated request is rarely the true requirement. Good architecture is the discipline of finding the difference.

This is why a half-formed idea is not a liability. It is raw material. An architect trained in listening can extract, test, and translate the fragments — the way you linger in a particular corner of a friend's kitchen, the hotel lobby you never wanted to leave, the complaint you make about your current home without realizing it's actually a wish.

Why Vague Clients Sometimes Build the Best Buildings

There is an irony in residential and small commercial practice: the clients who arrive with the most prescriptive visions often get the most conventional results, because they have pre-solved every problem with borrowed imagery. Their home becomes a collage of other people's answers.

Clients who come with needs rather than images leave room for the site, the light, and the program to shape something specific to them. A retailer in the Midwest who said only "I want people to feel welcome before they reach the door" ended up with a building unlike anything in the folder of references they'd originally brought — and far better than anything in it. That openness is not passivity. It is trust placed in a process.

None of this means clients should be blank slates. It means the preparation that matters is not visual. It is personal.

What to Know Before You Call: Needs Versus Wants

You do not need to know what you want your building to look like. You do need to know — or be willing to discover — how you live and work. Before engaging an architect, spend a few weeks paying attention to the following:

• Friction points. Where does your current space fight you? The hallway that becomes a bottleneck every morning, the office where no one can hear a phone call, the kitchen where two people cannot pass each other.
• Moments worth keeping. Where do you naturally gravitate? The spot with the afternoon light, the table where everyone ends up anyway.
• Non-negotiables versus preferences. Distinguish between what you truly require — a ground-floor bedroom for an aging parent, secure storage for a business — and what you would merely like. The first category shapes the design; the second enriches it.
• Time horizon. Will this building serve you in ten years? Twenty? A family with teenagers and a couple planning to age in place need very different architecture from the same square footage.

Write these observations down in plain language. "Mornings are chaotic and we're always in each other's way" is more valuable to an architect than forty photos of white kitchens. Describe your life, not your dream house. The dream house is the architect's job.

A Partnership, Not a Test

The design process is structured precisely so that clients never need to have everything figured out. Schematic design exists to test ideas cheaply, in pencil, before they cost anything. Design reviews are opportunities to react — and reactions, even negative ones, are information. A client who says "this doesn't feel right, but I can't say why" has given the architect something useful. The next conversation will find out why.

The best projects are rarely the ones where the client arrived finished. They are the ones where client and architect discovered, together, something neither could have articulated alone. That discovery is the point of hiring an architect in the first place.

So if you are waiting to hire an architect until you know what you want, consider this: knowing what you want is what the process is for. Arrive with your life, your frustrations, and your hopes. Bring the folder of saved photos if you like — it tells us something, even if only what to push against. Then let the work of figuring it out begin.