Can technical writing suck less?
I currently have the prospect of writing a considerable amount of technical documentation (describing interactions with an extremely complex online service). I consider myself a reasonably proficient creative writer but that never seems to do me any good when writing tech docs. The problem, of course, is the dryness. You can't explore the feelings and emotions of the Chromecast when it betrays the TV. It has to be 1. plug in 2. connect 3. watch. There is the very (extremely) informal approach to documentation that a lot of consumer goods acquire but I often find those a little cringeworthy. So is there a way to write technical documentation that doesn't put you to sleep, but also treat the reader like a three year old. Is there a way to write 1. plug in 2. connect 3. watch. that the reader can feel engaged by. Is it possible to marry technical writing and creative writing successfully. I would be very curious to see any examples that you think might have solved this problem.