Often clients ask us to do something that we think is *really* bad for the project. What they ask is not really important here, it could be using a particular technology or specific approach to a task that on the long run will create (IMHO) issues on performance or maintainability of the code or something like that.
As professionals, it is our duty not just to "tell" it is a bad idea, but to educate the client on "why" it is a bad idea. Communicating complex ideas to non technical customers is not easy for us technical people, but like it or not, it is part of the job and helps us get the job done right... and *that* is the reason why clients are willing to paying the big bucks for.
A bit ago I was trying to explain a customer the why's of a bad idea. Still, he insisted on going for it.. Frustrated I said in a very nice tone: "The way I see it, you are asking me to hit your finger with hammer" to what I quickly followed with: "then again.. it is *your* finger and *your* hammer so say the word and I will go ahead."
No comments:
Post a Comment