What does come first, the Client or the Project?

      "A camel is a horse designed by committee."


      Well, this is a version of the same old problem: what does come first? The Client or The Project?

      When you work in a Client-oriented scenario you basically cannot say "No" to your client. You may suggest things, you may guide him towards your ideas (if you are good enough in doing that) but if he is stubborn enough, you just can't say "No". In fact... he will pay at the end of it, so it is his decision, as long as he pays your efforts, no matter the service you provide.

      But is this really healthy as mentality? What does the Client really want as end result? He wants to solve his problems. He wants a product (or a solution or any service you provide...) that will solve his problem, that will make him happier, that will lead to his growth.

      Does he know better than you what is best for him? Maybe not, since he already has the problem he cannot solve. Maybe yes, because he knows better his business, he was already struggling with various solutions and... why not... maybe you are just not the best provider.

      My believe is that project comes first, but I tent to believe also that this will happen only in the ideal situation when all parties are looking to understand, are listening and all are looking towards same goal: to find the best solution for the problem, the best idea to fulfill the needs, etc.. not focusing on personal or private, isolated needs.

      Usually the Client is focused on suggesting and enforcing solutions that are not always the right ones. Usually the provider is focused on getting the highest profit. Both of the parties meet somewhere in the middle after climbing a mountain of compromises. Then they call this "the project" and start to execute.

      There's also the ego. Personal issues since we are all human.

      Sometimes the good thing happens. Sometimes you are the right Provider and at the sam time the Client hires you and looks at you as at a specialist, allowing you the freedom you need. Sometimes both of the parties are willing to make all efforts so the project, their "baby" will succeed.

      In software development, this (Client enforced solutions vs. proper system design) is a common problem that usually gets self-defined in the beginning of the project. You will see how the project becomes strictly a contractual agreement or becomes something alive, something with a life of it's own, growing...

      Is it the same with User-driven development? With online communities and platforms? I think so, yes. You HAVE to listen to your Client, you HAVE to rate your features, but do they always know what is better for them? Not always, (in case of custom software development - not even even frequent).

      Does the Provider "surrender" to their Client? Does the Client "surrender" to his Provider? None of the above is right. They both have to "surrender" to the Project... well.. it rarely happens.

      Do you surrender to your Client?

      Here's the inspirational link of the day:

      No! Never Surrender To Your Users, Facebook.
http://www.ngkhai.net/bizdrivenlife/writings/2009/04/13/no-never-surrender-to-your-users-facebook/

      Since you are here, read other interesting articles...

      The Problem with Problems
""Deficit thinking" sees organizations focusing on what's wrong and problems that need to be solved. In doing so, they often overlook real opportunities"
http://www.ngkhai.net/bizdrivenlife/writings/2009/04/13/the-problem-with-problems/

      Why A Blog Can Be Good For Your Business
"You can establish yourself as an expert. Blogs give you a way to reach out to clients..."
http://www.pheedcontent.com/click.phdo?i=e0ee3424bade975c2432439d089de68a

      Retaining your best people
"In spite of the obviousness of this crucial responsibility, many organizations suffer from the ‘leaking reservoir’ syndrome"
http://www.codeproject.com/KB/work/Retainingyourbestpeople.aspx


.