when they say no
10 October 2013
This is one of those posts I’ve put off writing because I wasn’t sure of the reaction or my real motivation. However, my blog tagline compels me to share what we’re thinking. If you’re looking for facts, checklists or hard core information, well…you’re not going to get it today. I’m just sharing thoughts today hoping to evoke a conversation. Maybe next week I’ll put away my tissues and get back to business.
So, what do you do when they say no?
As architects in a creative field our emotions are deeply rooted in our work. I believe when going after an architectural commission, architects put more into it than mere business sense and set of unemotional numbers and proposal language. We often go after projects because we have some interest in them and we believe they could add to our portfolio. Yet when we do not receive the commission, it can feel like the client is rejecting us as opposed to declining our services. Maybe I’m alone on this.
Before we discuss this, let me acknowledge two things. One, there are scores of blogs, articles, podcasts, videos, etc. about marketing and methods of getting the project (or increasing your chances). Two, there is another related discussion about the architect saying no to a project for a whole host of reasons. However, I’m not giving advice and you can read here about one blogger exploring saying no. I’ll deal with that one sometime in the future.
In my opinion there are three main reasons why clients say no.
The first one is price
The second one is experience
The third one is chemistry
Other than hiring the next guy because his price is cheaper than yours, the last two reasons relate to a sense of trust (or lack) in the architect. It might not be that the client doesn’t trust you (or like you); it’s just that they trust (or like) another architect more. There lies the problem. How do we communicate well to a client during the interview or proposal phase? Methods can vary whether you are in a formal process for a large public project all the way down to a single family home. My practice focuses on small commercial projects and residential design, thus the slant of this post.
You’re wondering why write about this – right? You’re wondering if you should keep reading – right? You’re wondering if I’ll keep asking questions.
I do believe in the “pull oneself up from their bootstraps” mentality and the “suck it up” mindset and move on without whining. Yet ignoring that emotion or that “let down feeling” and acting like a dispassionate entrepreneur is disingenuous to being an architect. We’re the artsy type and we often wear our “hearts on our sleeves” to borrow a bad cliché. Quite frankly, I hate to lose. Despite that horrible feeling of getting a “dear john” letter (or email or call or nothing at all), there is much to learn from each situation. Nevertheless, in order to truly learn from the situation, it would really help if the client would give honest feedback to what led to their decision. Sometimes you learn there is nothing you could have done. Often you find out not getting the project was a blessing in disguise. In many cases in my practice, I found out years later the project never happened.
I’m not proposing answers at this point and perhaps I am venting and you’d rather read about solutions than merely discussing feelings. I believe acknowledging the feeling along with inviting a conversation is critical in developing improved proposal/interviewing skills. Self-reflection and critique is often painful, but a necessary part of being an architect. I am curious to your thoughts.
photos are from multiple photostreams on Flickr (used under the Creative Common License)