39. The Client

What the client wants.

This post is part of a series looking at Michael Sorkin’s list of 250 things every architect should know.

“There is a secret that all attentive architects know: Don’t give your client what they ask for, give them what they need.” – Bob Borson, Designing for Others, (Life of an Architect blog)

“First impressions are important here, as you are evaluating whether you and your potential architect have a good rapport… This is probably the most intangible—and important—part of the entire process. Assess whether the architect listens to your needs and confirms that he or she understands them.” – Melissa Dalton, What to Expect When Working With an Architect (Curbed.com)

Part of being an architect is being a therapist, cultivating a relationship with a client in order to understand their situation and their needs. Sometimes this process is very direct, with a questionnaire or an interview. Sometimes this process entails more fluid conversations, requiring reading between the lines, understanding what is left unsaid as much as what is spoken. This is a skill that is not often taught in architecture school, and it is rarely taught to young architects in firms. In the professional world clients often interact directly with firm principals or senior architects, rarely with less experience architects still learning the trade.