You're on the right track here, but as was mentioned, this is basically impossible. My first recommendation is to use the language of the user. Tell them clearly what the problem is without resorting to technical jargon. Allow for this jargon to be accessed by opening an advanced tab or some similar system. Try to tell the user directly what they need to do to fix the problem (don't just tell them to contact their system administrator). If they need to call someone try to give them the number. Try listing any instructions in actionable bullet-points. Simple to read lists are going to be much more likely to be read than a textbox full of code dump.
The puppy error idea might work. I would love to hear more stories about success or failure here.
If are with a larger company, then talk to one of these departments for more ideas (or validation of your existing ideas):
Human Factors
User Experience
Usability
They specialize in working with problems like this, and if they have the time they should see this as an interesting problem in their domain (I know I do).
Slashdot Mirror
You're on the right track here, but as was mentioned, this is basically impossible. My first recommendation is to use the language of the user. Tell them clearly what the problem is without resorting to technical jargon. Allow for this jargon to be accessed by opening an advanced tab or some similar system. Try to tell the user directly what they need to do to fix the problem (don't just tell them to contact their system administrator). If they need to call someone try to give them the number. Try listing any instructions in actionable bullet-points. Simple to read lists are going to be much more likely to be read than a textbox full of code dump. The puppy error idea might work. I would love to hear more stories about success or failure here. If are with a larger company, then talk to one of these departments for more ideas (or validation of your existing ideas): Human Factors User Experience Usability They specialize in working with problems like this, and if they have the time they should see this as an interesting problem in their domain (I know I do).