14.01.2010 Blog Simon Fraser 1 Comment

Should we say No.

Introduction
As we are faced with projects or work from clients we are always asked the most obscure questions and queries, and I know as soon as I’m asked something obscure I try to picture it and then come up with a probability for it being difficult.  But even if its the hardest thing to date I’ve been asked I still say yes I can do that, mind you I will voice my option to the client and will tell them it could be a difficult task or could be time consuming in the build or design process, and  probably will bring the overall project cost up.

Theory
Having worked with small business where bothering the client or not being able to deliver will no doubt lose you the business, it has been taught to me that you “Always say yes”, this at times can be a bad idea, all you have to do is watch the film Yes Man to see a representation of this.
But is saying No to a clients project requests something we can or should do as designers or developers, If we have a problem should be not just voice our opinion and offer alternative solutions.  After all we are the professionals that our client has come to see because this is what we do, if we are offering alternative solutions to problems should they not take that solution and try to weigh the merits and decide what is best for them.  Even after we have offered several maybe easier solutions and the client decides they want it done their way should we not simply say okay, after all this is their project too and the client might just know what they are looking for.

http://fukung.net/v/184/software-project.jpg
What the Client Wants

Your Opinions
What are your opinions on the matter, are you more likely to say No, thats probably not possible or are you more like me and say yes that can be done and go away and work on it?

One Response to “Should we say No.”

  1. duckbox says:
    January 14, 2010 at 21:09

    Quite a nice theory, and sound on many levels. You are quite right, we DO have an option of saying no, in the right circumstances, wherever we would deem a project route of being absolutely, catastrophically immoral as a designer / developer. I always find the best solution to be list possible routes, labeling the pro’s and con’s of each, and voicing my own opinion of what I deem is in the clients best interests, and ask, their opinion of what they believe is the best option.

    But particularly at the end of the day, the client is paying you. You’ll build exactly what he wants or what they believe they need. We are like anyone else, bills to pay, mouths to feed.

    Yet, questionable on the other end of the spectrum, you would not argue with a builder of how you want your bricks laid?

Leave a Reply