Top ten qualities of a successful technical writer
Which qualities make a successful technical writer?
I believe they are the same qualities that make a successful journalist. Both journalists and technical writers are non-fiction writers and non-fiction writing demands a different skill set than fiction writing.
After more than 20 years in this business, here are my top ten qualities of a successful technical writer:
#1. Excellent writing ability – This one is so obvious, I almost didn’t mention it. If you can’t write a page of logical, concise instructions, even if you have all the other qualities, you will never be a successful technical writer. Contrary to popular belief, most people can’t write. Companies who routinely hire writers and editors tell me that 90% of applicants fail the writing test. This is also what I discovered as a hiring manager giving writing tests to applicants. Actively choose to be a technical writer because you love writing and you do it well. The best writers are those who have loved and practiced the craft of writing and editing their entire lives.
#2. Customer-focused – You must be focused like a laser on customers. What do they need, want, and expect? A good technical writer is the best advocate the customer has. Gather customer feedback on your content, then refine it relentlessly to continuously improve the customer experience.
#3. Curious – You must be curious and love learning new things. If you are lazy or too embarrassed to ask questions and learn how a new product works, you won’t be a good technical writer.
#4. Organized – Organization should come naturally to you and you should enjoy doing it, because technical writing is all about researching, culling, and organizing facts. You need the ability to put all steps in a process in the correct order and ruthlessly discard irrelevant facts that don’t fit in. For example, if you are writing instructions on how to install software, don’t include a history of the project or who developed the software.
#5. Action-oriented – You don’t wait for someone to hand you tasks; you plan projects, anticipate roadblocks, and resolve problems without being told. Without being directed, you must be responsible and take ownership of the content, ensure it meets the customer’s needs, and keep it current and reliable.
#6. Simple – You need to be able to cut through the jargon of engineers and other subject matter experts and translate their explanations into clear, concise terms that a non-expert can understand. My motto is: “If I don’t understand, the customer won’t understand.” Sometimes you will be mocked for doing this, but your customers will appreciate it. You should use as few words as possible to convey the information. Remember, simple is elegant!
#7. Humble – Don’t be afraid to say, “What does that mean?” or “Can you show me?” every day if necessary. Don’t worry that you are the stupidest person in the room. The truth is, the person who never learns anything new is the stupidest person in the room—and that won’t be you! When someone uses an acronym, ask the meaning. Often the person using the acronym doesn’t even know; and if that happens, look it up online. Chances are, other people in the room didn’t understand the acronym or explanation just given by that expert either.
#8. Tenacious – You must have the ability to grab hold of a problem or topic—like a bulldog—and not let go until you have the answer. If an engineer does not have time to give you that product demo today, ask if he will show you tomorrow. Then put it on your calendar and follow up every few days until you get the demo.
#9. Meticulous – If you are a “big picture” person and don’t care that much about accuracy and attention to detail, you won’t make a good technical writer. If you say, “I can’t edit or proofread my own work,” you won’t make a good technical writer. The person who researches and writes the piece is often the same person who edits and proofreads the piece. Many times, the only person checking what you write is the subject matter expert, who cares about technical accuracy, but cannot correct writing style, format, layout, spelling, grammar, and punctuation. If you don’t care about semicolons and fonts, find another career. If no one has ever described you as “obsessive” or “picky,” find another career. A slap dash approach to writing won’t do. Always do the best you can in the time available.
#10. Team player who can work independently – Last, but definitely not least—you must be able to collaborate with subject matter experts—engineers, software developers, project managers, and technicians—to gather information, accept feedback, and improve your content. Then you must also be able to shift gears and work independently to finish writing the content in time to meet the deadline. For more insight, check out Technical writers: solitary creatures or team players?
