Jefferson McClure added a thought-provoking article link on WriterRiver.com titled "Myths of Technical Writing." The article is by Bob Doyle and appears on the dita.xml.org wiki site here. In the article, Doyle and other wiki contributors mention 4 myths about technical writing:
You'll have to read the original for the details. The debunking of these myths is supposed to help you embrace a structured authoring methodology like DITA. The myths are genuinely insightful, and it got me thinking about myths in a larger sense.
In part, I'm reflecting on myths because I was recently invited to speak to students at a professional writing conference at BYU Idaho in the fall with the topic, "Three Myths About Technical Writers."
Apparently, many students pursing English degrees assume technical writers have "sold out." They think technical writing is a "fallback" career. It's something you can do if you're starving and don't have any other options. Oh, the financial naivete and idealism ...
I'm not sure what will convince people immersed in Charles Dickens and Edgar Allen Poe and Chaucer and Emily Dickinson, who are writing about deconstructionism and feminism and the intersection of Shakespearian influences on postmodern authors, etc., that technical writing is more than just "press this button here to program your VCR..."
It will be a challenge, but one worth taking. When I was a student at BYU, I held these same biases against technical writing. I acquired the myths from one presentation by a teacher who represented the English faculty on technical writing. In a nutshell, compared to the other English professors, she was the most boring of any I've ever met -- by a long shot. She talked about formatting phone books. I whispered a silent vow to myself that I would never, never become like her. While she spoke of layout and design for banal texts, other professors ignited us with literary ideas.
I now have a personal vow to make technical writing look like one of the most appealing careers one could possibly pursue.
In addition to myths about technical writing as a sellout and fallback career, I can think of at least 10 other commonly held myths surrounding the field of technical communication. I offer them below.
Totally untrue. Most tech writers spend about 10% of their time writing. The rest of their time they spend learning applications, noting bugs, providing usability feedback, structuring their content, setting up styles for their help files, troubleshooting their tools, strategizing help deliverables, training new users, formatting and laying out their content, updating existing content, meeting with project team members, and occasionally playing ping pong.
Don't believe this for an instant. You're surrounded by technology -- your iPod, computer, DVD player, microwave, cell phone, BlackBerry, and everything else. Download a trial version of some help authoring tool, or even just open up Microsoft Word. Write instructions for something. Find an open source application with poor instructions and rewrite them. You don't have to create an entire user manual. Just give your potential employer some evidence of your capability.
This myth is turning into my pet peeve. How many bios have you seen that begin, "Joe has 15 years of experience ..." or "Kate has over 20 years of experience as a technical writer...." Experience means nothing unless learning is taking place. I can go to my same job for 15 years, do the exact same tasks, use the exact same tools, never taking any creative risks or moving into new territory, just doing what I'm told, or what I've read, for my entire life. The pace of learning can be compressed into a very short time period, or it can drawn out over a life time. The time (years of experience) does not matter as much as the learning that takes place. (See this related post, MySQL CEO Says, "It is dangerous to hire someone with too much experience.")
When I hear this, I cringe. The discussion always comes up among non-bloggers who think blogs are a wart you need to hide. Sure if you have an embarrassing MySpace page where you mix profanity with vulgarity and other shady content, that's a site you need to obliterate. But a professional blog demonstrating your knowledge of technical communication can be a powerful tool for getting an edge on other job candidates. It can also serve as a tool for professional development and keep you enthusiastic about your career.
Many academics started out as technical writers and worked for years doing the same things we did. Are we practitioners so vain that we think the industry is rapidly changing from year to year, so much so that intelligent people who spend years immersed in texts, studies, journals, and experiments have no idea what our jobs involve? Academics may not be totally fluent with the latest tools, but that doesn't mean they're disconnected with technical writing practices and challenges. (See this related post, "Reflections on Allison Reynold's Talk on Job Skills for the Workplace.")
All writing has voice. You don't have to remove all sense of humanity from your writing. A writer who uses contractions, moves toward conversational style, and truly has voice will provide a better experience for the frustrated user who seeks human help rather than cold robotic formalese. The talk that changed me forever was this keynote by Kathy Sierra at SXSW, where she explains the need for human qualities in help material when users, in desperate frustration, finally click the help button. If you want to sound like a robot, eliminate all contractions from your writing. What tone do you think users respond better to?
Here we see yet another wrong idea that will only put up roadblocks for worthwhile help. Joe Sokohl clarified this principle at Doc Train West 2008, calling it the Kobayashi Maru principle (a reference from Star Trek). He says you have to throw aside the idea that you can't contact users. Without this contact and the information you can gather from users, you're hopelessly doomed to write instructional material they don't want.
When you learn to structure your content with DITA, you can magically transform all your content into every format your users need. NOT. The type of instructions you write for a one page quick reference guide varies from the kind of style you need for an iPhone or for a long manual. While I agree that you can single source online help to a software manual, the idea gets taken too far. (See this related post by Gordon McLean, "DITA Is Not the Answer.")
Actually, when you become so tech savvy that you can't imagine users not understanding how to disable a popup blocker or not knowing how to do a simple task, when you are stunned at users who double-click when they should single-click, or who single-click when they should double-click, at this point, you lose some ability to write for the lowest common denominator. It's not such a bad thing if you're technically challenged. So are most of your users! You'll be on a level playing field and will probably write a help manual that actually speaks their language. (See this related post, "The Curse of Knowledge -- The More You Know, the Worse You Become at Communicating that Knowledge.")
Get new posts delivered straight to your inbox.
I'm a technical writer based in the California San Francisco Bay area. Topics I write about on this blog include technical writing, authoring and publishing tools, API documentation, tech comm trends, visual communication, technical writing career advice, information architecture and findability, developer documentation, and more. If you're a professional or aspiring technical writer, be sure to subscribe to email updates using the form above. You can learn more about me here. You can also contact me with questions.