> Lye is a strong word.  "Need to Know" is the better expression.

NO. There is a difference.

Lying is  telling the customer "this meets your stupid spec" when it
DOES NOT.

"Need to know" is when the customer says: "I need an EL backlight
inverter", and you tell them, "try this one, it will work great" but
you don't tell them whether its sine wave or square wave output.

> Do you believe that doctors would tell you exactly the risks involved to do a
> simple hospital surgery?

Yes.  And I'm not being stupid or stubborn in saying so- I signed the
release form, which says exactly what the risks are.  Some people
don't want to know, they don't read it.  I read it and discuss it
with the doctor.  I don't tell him where to cut, but we sure do
discuss treatment options and why he thinks this is the best way.

And if I don't like his answer I walk away.

And if I tell him I want different treatment, and he knows that's
wrong, he is OBLIGATED to refuse.

Same for electrical engineers.  We're supposed to be professionals,
too, remember?

> A doctor does not interrupt a brain surgery to discuss with the parents
> about what he is going to do next, first because parents have no
> knowledge to discuss it, second because the doctor *is* the specialist
> and he *has* the knowledge to decide based on that.

Right.  Similarly, I don't expect to stop in the middle of designing
the EL backlight inverter to discuss component values and capacitor
dielectric breakdown with the customer.  We already decided to build
the inverter, we already agreed on the spec (however vague it may
have been...)

They don't "need to know" why I choose 4.7 KOhms, and I wouldn't
bother to tell them.  But if they ask, I don't tell them, "oh yes, 10
K" if its 4.7K.

> Of course contractors will have strictly procedures, projects and
> technical specs, I am not discussing it. What I am telling you is that
> if the customer (less technically prepared) can't understand words, you
> need to show them a working prototype in the way you know it is better.

Absolutely right.  What you are talking about there is a way of
communicating what the spec should be, to convince a customer who
would otherwise overspecify.  Rapid prototypes are a great way to
decide details when the technical details are not understood by the
customer.  The business details of who pays for the development of
the prototype can be interesting, though.  (But can work, BTW)

When a customer over-specifies, you could just do it their way, when
your way is better.  I think its an even higher level of service for
the professional to see the overspecified area, and take exception to
it, and tell the customer that there is a better way.

<SOAPBOX SIZE=TALL>
Convince your customers when they are wrong, take exception to their
specs, refuse to work with them if you must, but don't lie to them!
</SOAPBOX>

Barry
------------
Barry King, Engineering Manager
NRG Systems "Measuring the Wind's Energy"
www.nrgsystems.com
Phone: 802-482-2255
FAX:   802-482-2272