View Single Post
Old 05-22-2016, 03:42 PM   #46
Sarlacc
/dev/null
 
Sarlacc's Avatar
 
Join Date: Jan 2013
Drives: Uphill
Location: Metric North
Posts: 2,221
Thanks: 3,489
Thanked 2,926 Times in 1,420 Posts
Mentioned: 18 Post(s)
Tagged: 14 Thread(s)
Garage
Quote:
Originally Posted by DarkPhoenix View Post
Or assigned to the product team who decides that the "documentation is in the experience" and tells the support engineers the product doesn't need documentation... nevermind said support engineers have dozens of clients asking for precise instructions on how to use it because they can't figure it out.

And then the senior support engineer (i.e. me) ends up having to spend her lunch break writing the documentation just so her team doesn't have to keep typing the same email over and over and over (because she doesn't have enough to do that's actually in her job description), only for a sales rep to complain that the documentation isn't "pretty enough".

Hire a damned tech writer already.

Or, at the very least, hire a consultant who can teach your team advanced copy/paste techniques, so they won't have to type the same email over and over
Sarlacc is offline   Reply With Quote
The Following User Says Thank You to Sarlacc For This Useful Post:
Tcoat (05-23-2016)