The purpose of technical communication is to get the right information to the users to help them do the right thing and do the thing right; quickly and easily.
As technical writers, how do we ensure that the content we create is helping users do this?
Well, let us look at some characteristics of effective technical content.
- Relevant. Give users exactly the information they are looking for. For example, if the user is trying to complete a task just provide the steps with any pre- and post-requisites. Do not include explanation of the concept.
Similarly, if the user wants information that explains the overall process, given them a process flow rather than detailed step-by-step instructions.
- Concise. Users refer technical documents as and when they need information to achieve some result; be it completing a task or making a decision. So we should help them reach their goal quickly by presenting information that is to the point, and complete.
Note: Keeping it short and simple does not mean sacrificing information.
- Accurate. The information must be precise, unambiguous, and correct. You don’t want the users to wonder what something meant, get the wrong idea, or do something wrong.
- Well-Structured. The information should have a logical flow that helps users understand it quickly. Complete the puzzle for the user; don’t ask the user to put the pieces together.
- Accessible. Users should be able to locate and access the information they are looking for quickly and easily. This is why technical documents have headings, Table of Contents, Index, cross-references, links, and more.
When was the last time you read a user manual from cover to cover?
- Well-Illustrated. The adage of a picture being worth a thousand words is very relevant to technical writing. Use illustrations, screen shots, tables, icons and similar graphic elements where possible.
Pingback:Effective Technical Writing Skills: A Must for All Techies « ibruk Consulting
Pingback:The Importance of Writing Precisely « ibruk Consulting
Hi,
Can the ‘Predictable’ be called ‘Consistent’. I’d say, I want the document ‘consistent’ and not predictable. Apart from that the article is good. Thanks for sharing.
Hi Keerthi,
Consistency leads to predictability for the reader 🙂
Pingback:Mumbai: Certificate Course in Technical Writing « ibruk Consulting
Pingback:Consistency: Using Style Guides « ibruk Consulting
Pingback:Technical Writing: The “Unicorn Skill” for Aspiring Software Engineers – EAR Tech Hub
Pingback:Technical Writing: The “Unicorn Skill” for Aspiring Software Engineers – E.A.R PDX