Writing Helpful Help – A Minimalism Checklist by Glenn Murray

Back

Writing Helpful Help – A Minimalism Checklist
by Glenn Murray

User documentation is all too often written by programmers for programmers. It tends to focus on the product’s features, rather than the user’s tasks. Generally, programmers aren’t in the ideal position to be writing user documentation. They’re too close to the bits and bytes, and they’re too far from the user. To them, what the product can do tends to be far more important than what the user can do with the product.

It’s a subtle – but vital – distinction. Research shows that the key to effective user documentation is writing task oriented help. Even better, write your help according to the minimalist theory. In the documentation world, “minimalism” is a fancy word for a commonsense practice. In basic terms, it means write to your reader and keep it simple.

The theory itself has a lot of twists and turns. If you want to read a great – but slightly wordy – book on the subject, check out the book “Minimalism Beyond the Nurnberg Funnel”, 1998, edited by John Carroll.

In the meantime, if you can tick every item in the following checklist, you’ll be well on your way to usable online help that both your readers and your managers will thank you for.

Helpful Help Checklist

1. Base the help on real tasks (or realistic examples)

2. Structure the help based on task sequence – Chapter headings should be goals and topics should be tasks

3. Respect the reader's activity – this is generally more about what you don’t do than what you do. Don’t waste the reader’s time by diving off into tangents

4. Exploit prior knowledge and experience – Draw the reader’s attention to previous tasks, experiences, successes, and failures

5. Prevent mistakes -

Author's Biography:

Posted on: April 24,2005

Email: glenn@divinewrite.com
Website: http://www.divinewrite.com