> My experience...you have to explain the consequences in
> layman's terms (no
> "geek talk", and yes, I am a computer geek). If you can, instead of
> explaining why the software won't work given the requirement, and a
> real-life example that the customer can relate to and understand...for
> example, it's like trying to tie my shoes when I'm not allowed to have
> shoe-laces (I wouldn't use that one). A good analogy can
> sometimes go alot further that a brilliant explanation.
Nope. I prefer something like:
I can do it my way. It'll cost you $1 and I can do it
in 15 minutes.
I can do it your way. It'll cost you $1000, will take
a week and it still won't work the way you want.
What should I do?
I usually get to do what I want to do...
-TPP
-----------------------------------------
This email may contain confidential and privileged material for the sole use of the
intended recipient(s). Any review, use, retention, distribution or disclosure by
others is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data corruption, interception,
tampering, unauthorized amendment and viruses. We only send and receive emails on the
basis that we are not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
