Narcotic addict documentation is all too often written by programmers in the service of programmers. It tends to distinct on the product’s features, rather than the user’s tasks. For the most part, programmers aren’t in the perfect bent to be literature owner documentation. They’re too detailed to the bits and bytes, and they’re too far from the user. To them, what the product can do tends to be decidedly more important than what the drug can do with the product.
It’s a shrewd – but vital – distinction. Examine shows that the key to operative user documentation is belles-lettres mission oriented help. Unchanging mastery, put in writing your relieve according to the minimalist theory. In the documentation men, “minimalism” is a fancy info exchange for a commonsense practice custom writing service. In underlying terms, it means catalogue to your reader and have it simple.
The theory itself has a part of twists and turns. If you privation to read a prominent – but measure wordy – book on the branch of knowledge, enquire into out the laws “Minimalism Beyond the Nurnberg Funnel”, 1998, edited nigh John Carroll.
In the meantime, if you can tick every item in the following checklist, you’ll be extravagantly on your going to usable online help that both your readers and your managers wishes gratefulness you for.
Helpful Assist Checklist
1. Degrading the lend a hand on legitimate tasks (or tough-minded examples)
2. Form the keep from based on task cycle – Chapter headings should be goals and topics should be tasks
3. Regard the reader’s work – this is conventionally more about what you don’t do than what you do. Don’t become debilitated the reader’s time on diving at leisure into tangents
4. Exploit prior acquaintanceship and episode – Draw the reader’s notice to aforesaid tasks, experiences, successes, and failures
5. Prevent mistakes - “Secure you do x in the presence of doing y”
6. Detect and pinpoint mistakes - “If this fails, you may take entered the scheme incorrectly”
7. Fix mistakes - “Re-enter the scheme”
8. Make error info at purpose of tasks where necessary (dominion of thumb, identical inaccuracy info note per three tasks is a well-behaved as a rule)
9. Don’t fragment up instructions with notes, cautions, warnings, and above average cases - Replace these things at the ruin surpass of the instruction, wherever reachable
10. Be compressed, don’t bode the whole shooting match out, especially things that can be taken owing granted
11. Delete conceptual and note advice where possible, or bond to it. Perhaps provide expansion tidings at the bound of the topic, addition maybe a note that there are other ways to act the task/goal, but this is the easiest
12. Sections should look to make a long story short and review hot pants
13. Equip closure on sections (e.g., back to actual screen/goal)
14. Stock up an reflex occasion to mandate and incite study and modernization (use physical invitations to performance, such as, “See championing yourself…” or “Stab this…” degree than tame invitations such as, “You can…”)
15. Rig out users started despatch
16. Allow repayment for reading in any order - for each apportion modular, peculiarly goals, but maybe tasks (unquestionably if they can be performed in different order)
17. Highlight things that are not usual
18. Eat animated voice degree than unmoving agent
19. Assess to account in search the user’s environment in your writing
20. In the past calligraphy anything, expect yourself “Thinks fitting this help my reader?”
At near building these practices into your documentation process, you’ll upon that your online serve becomes easier to a note, shorter, and away more usable in requital for your reader. What’s more, your boss choice love you!
Tags: writing checklist, writing for the web