I sit in on the developers' meetings here because they sometimes need some input on how our customers use the program.
We were hashing out a new feature and trying to figure out the various ways customers could fark things up misusing it.
Someone kiddingly proposed putting up a useless error message. "[Program] is going to crash momentarily. Please don't do that again."
The only button would be "OK."
Another person proposed we put a "Why?" button as well. When they click the "Why" button the appropriate page from the user's manual would appear on the screen with a polite suggestion they read it.
We were hashing out a new feature and trying to figure out the various ways customers could fark things up misusing it.
Someone kiddingly proposed putting up a useless error message. "[Program] is going to crash momentarily. Please don't do that again."
The only button would be "OK."
Another person proposed we put a "Why?" button as well. When they click the "Why" button the appropriate page from the user's manual would appear on the screen with a polite suggestion they read it.

Comment