Video has not killed the tech comm star
Ellis Pratt of Cherryleaf asks: How important is video to technical authors?
Graham argues you cannot afford to ignore video.
Author: Alan Pringle
Contemplating the tablet in tech comm
Ebooks and tablets are helping people read more than they did before: in a recent survey, 66 percent of portable device owners said they were reading more.
That statistic should prompt all technical communicators to think about if—and how—ebooks and other tablet-compatible formats (including apps) fit into their content delivery.
Social media: marketing in every message
Social media has transformed the work of technical communicators, but we’re far from alone in feeling its impact:
Writers can make good publishers
Earlier this week, Richard Curtis at e-reads asked Do Authors Make Good Publishers?, and he answers the question emphatically in the first paragraph of his post:
The answer is No.
Failure to communicate: fatal to projects (and political parties)
Over the weekend, I was catching up with a friend I hadn’t seen since the mid-term elections here in the US. While hashing out what the election results meant, my friend said that he felt that history would be kinder to the accomplishments of Congress than the electorate was.
Distilling 20 years of tech comm into eight words of advice
Last month marked my 20th year working in technical communication. (Please send all congratulatory pastries and chocolates to Scriptorium’s offices. Thank you!)
Retail therapy for tech comm (and I don’t mean shopping)
“She’s stupid.”
That’s what a shopper recently said about a coworker’s daughter, who is working a part-time retail job.
Interview with a vampire: interviewing to find processes that drain efficiency
When you’re considering an overhaul of your publishing workflow, you may find yourself becoming a metaphorical version of Van Helsing, the vampire-hunting character from Bram Stoker’s Dracula (and the many, many movies based on the Dracula story). You need to find all the efficiency-draining aspects of your current process and eliminate them.
Some Friday fun: tech writing in movies
Here’s a movie montage I found on YouTube featuring scenes of characters either offering or reading procedures:
Enjoy!
Cardinal sin of blog (and technical) writing: making the reader feel stupid
Want to get me riled up? You can easily achieve that by making me feel stupid while reading your blog.
I read a lot of blogs about technology, and I’ll admit that I’m on the periphery of some of these blogs’ intended audiences. That being said, there is no excuse for starting a blog entry like this:
Everyone’s heard of Gordon Moore’s famous Law, but not everyone has noticed how what he said has gradually morphed into a marketing message so misleading I’m surprised Intel doesn’t require people to play the company jingle just for mentioning it.
Well, I must not be part of the “everyone” collective because I had to think long and hard about “Gordon Moore’s famous law,” and I drew a blank. (Here’s a link for those like me who can’t remember or don’t know what Moore’s Law is.)
Making a broad generalization such as “everyone knows x” is always dangerous. This is true in blog writing as well as in technical writing. In our style guide, we have a rule that writers should “not use simple or simply to describe a feature or step.” By labeling something as simple, it’s guaranteed you will offend someone who doesn’t understand the concept. For example, while editing one of our white papers about the DITA Open Toolkit, I saw the word “simply” and took great delight in striking through it. From where I stand, there is little that is “simple” about the toolkit, particularly when you’re talking about configuring output.
Don’t get me wrong: I’m not saying that a blog entry, white paper, or user manual about very technical subjects has to explain every little thing. You need to address the audience at the correct level, which can be a delicate balancing act with highly technical content: overexplaining can also offend the reader. For example, in a user manual, it’s probably wise to explain up front the prerequisite knowledge. Also consider offering resources where the reader can get that knowledge: that way, you get around explaining concepts but still offer assistance to readers who need it.
In the case of online content and blog entries, you can link to definitions of terms and concepts: readers who need help can click the links to get a quick refresher course on the information, and those who don’t can keep on reading. The author of the blog post in question could have inserted a link to Moore’s Law. Granted, he does define the law in the second paragraph, but he lost me with the “everyone has heard” bit at the start.
That “everyone has heard” assumption brings me back to my primary point: don’t make your readers feel stupid, particularly by making sweeping assumptions about what “everyone” knows or by labeling something as “simple.” Insulted readers move on—and may never come back.
