Saying What You Really Think: A Client's Guide to Design Reviews That Work

There is a moment familiar to nearly every architecture client. The drawings are pinned up, the model is on the table, and the architect is walking you through the scheme with evident enthusiasm. You nod. You ask a polite question or two. And somewhere in the back of your mind, a quiet voice says: I'm not sure about this.

Most clients say nothing. They worry that raising a concern will mark them as difficult, or that they lack the vocabulary to explain what bothers them. Then, weeks later, that unspoken doubt hardens into frustration, and the project suffers for it.

At our practice, we would rather hear that doubt on day one than discover it at the ribbon cutting. Design review is a conversation, not a verdict—and the clients who engage in it honestly tend to end up with buildings they love. Here is how to do it well.

Why Silence Is the Most Expensive Feedback

An architect can adapt to almost any constraint: a tight budget, a difficult site, a preservation board with strong opinions. What no one can adapt to is information withheld. When a client smiles through a presentation and signs off reluctantly, the design moves forward on a false premise, and every drawing produced afterward inherits the problem.

The correction gets more expensive at every stage. A concern voiced during schematic design might cost a day of redrawing. The same concern raised during construction documents might cost a week. Raised after framing, it can cost a change order with four zeros attached. Early candor is not rudeness—it is stewardship of your own investment.

There is also a creative cost. Some of the strongest design decisions we have made grew directly out of a client's pushback. Disagreement, handled respectfully, forces both parties to articulate what actually matters. That clarity almost always improves the work.

Distinguish the Concern From the Reaction

The most useful feedback separates what you observed from how you felt. "I hate this elevation" gives an architect nothing to work with. "The front of the house feels imposing to me—I expected something more welcoming" gives them everything.

Try framing concerns in these ways:

• "This doesn't feel like us yet." Vague but honest. A good architect will follow up with questions about what "us" means, and the conversation that follows is where the design gets better.
• "Help me understand the thinking here." This asks for the rationale behind a decision rather than challenging it outright. Often, once the reasoning is explained, the concern dissolves. Occasionally, explaining it reveals to the architect that the decision no longer holds.
• "Can we look at an alternative for this one piece?" Narrow, specific, and non-threatening. It signals that you trust the overall direction but want to test a single move.
• "I'm worried about how this will feel on a Tuesday morning in February." Grounding feedback in daily life—the commute to the kitchen, the walk from the driveway, the afternoon glare in the conference room—is something clients can do better than anyone else on the project team.

Notice what these phrases have in common: none of them are accusations, and none of them contain design vocabulary. You do not need to know the word for a reveal or a clerestory. You know how a space makes you feel, and that knowledge is the raw material of the entire enterprise.

Questions Worth Asking in Every Review

Beyond voicing concerns, sharp questions signal engagement and surface information you need. A few we wish every client would ask:

• "What are you least sure about in this scheme?" Every design has a soft spot. Asking about it invites honesty and shows where the team's attention should go next.
• "If budget forced a choice, which parts of this would you protect first?" This reveals the architect's priorities and helps you understand what the design is really about.
• "What did you consider and reject?" The alternatives behind a scheme are often as instructive as the scheme itself.
• "How will we know, once it's built, that this decision was right?" This connects abstract drawings to lived outcomes.

When You and Your Architect Genuinely Disagree

Sometimes the conversation is not about misunderstanding but real disagreement. Perhaps you want a larger great room; the architect believes the plan's proportions will suffer. Perhaps you love a material they find problematic.

Handle these moments the way you would handle a disagreement with a trusted professional in any field: state your position plainly, ask them to state theirs, and then require both sides to give reasons. "Convince me" is a perfectly respectable sentence. So is "I hear you, but I'm the one who lives here." A practice worth hiring will not collapse under that kind of pressure—it will be energized by it.

Two ground rules keep these exchanges productive. First, decide disagreements in person, never over email chains, where tone curdles and nuance dies. Second, if a disagreement persists after genuine discussion, ask the architect to show you the consequence of your position—sketch it, model it, walk you through it. Seeing the alternative usually settles the question faster than another round of argument.

The Partnership Behind the Building

Clients sometimes imagine that architects want deference, or that questioning a design insults the professional's expertise. In our experience, the opposite is true. A building designed without client pushback is a building designed against only half the brief. The site, the budget, the code, and the craft are all constraints we can study—but only the client knows what home feels like at the end of a long day, or what a lobby says to a nervous first-time visitor.

The best projects we have completed share a common history: at some point, a client told us the truth about something, kindly and clearly, and the design turned to meet it. That is not the second conversation going wrong. That is the design process working exactly as it should.