Post History
The typical user of technical communication is in a hurry and in a bad mood. They were working along trying to get a job done so they could go home and have supper with the kids then something brok...
Answer
#4: Attribution notice removed
by
System
·
2020-01-03T20:41:56Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/33525 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#3: Attribution notice added
by
System
·
2019-12-08T08:03:10Z (over 4 years ago)
Source: https://writers.stackexchange.com/a/33525 License name: CC BY-SA 3.0 License URL: https://creativecommons.org/licenses/by-sa/3.0/
#2: Initial revision
by
System
·
2019-12-08T08:03:10Z (over 4 years ago)
The typical user of technical communication is in a hurry and in a bad mood. They were working along trying to get a job done so they could go home and have supper with the kids then something broke or refused to work the way they thought it should, or a part would not go on properly, or a bug appeared out of nowhere, or the whole system quit working and blue smoke started pouring out. They are not in the mood for a joke. We should think of technical communication like a pitstop. It is a time to get the user what they need to continue as efficiently and with as little drama as possible. There is no time in a pitstop to tell the one about the dentist and farmer's daughter. That is why there is no humor in most technical communication and why there should not be. Humor in learning materials is another matter. Some like it. Some despise it. If you are selling a Dummies book, you can appeal just to those who like it and let the people who don't buy an O'Reilly book. But if this is your corporate training, you probably do not want to turn off half your audience.
#1: Imported from external source
by
System
·
2018-01-23T20:01:30Z (over 6 years ago)
Original score: 31