
Helping you solve your documentation issues
By Ellis Pratt, 16 July 2007
It is important you know the key purpose of your document: Who is your audience? What do you want to happen as a result of someone reading it? Try to understand the user and see through their eyes. You can do this by pre-empting questions the readers may have:
The pyramid style of writing, devised by Ron Blicq, is a very useful way of arranging the structure of your document:
Professional business writers, such as technical authors, typically break a document down into small, discrete units of information, organised around a skeleton of topic headings. If you use this "component" or "modular" approach, you can plan and structure the document using the heading "labels" that describe each section. These signposts help enormously when you start writing, and they can also help you be consistent and avoid missing out any important content. Indeed:
Your list of headings can be structured to form a storyboard, to guide the reader through your document. Meaningful titles for sections also help with the readability of your document, as they enable readers to scan down a document and find the sections that relate or are of interest to them.
Here is some advice regarding the words you use:
The best way to get a writing project completed on time is to adopt standard project management principles:
It's not uncommon for 30% of a writer's time to be spent working on the "look and feel", once all the writing has been done. Of course, documents designed to be read on paper don't work when they are read on a screen, so it's important to change the formatting to suit the delivery medium. The more documents (and the content contained within them) are published in different places, the more important it will be for you to be able to create these without being faced with spending lots of time on reworking. Look at the tools you use, to see if you can control the "look and feel" independently of your content. You can achieve this partly by using standard templates, but you might want to consider using content management software.
A key aspect to managing any business information is for people to be able to:
This is also true for business documents. However, it isn't always easy, with many organisations being in state of having lots of out-of date or missing documents, or more than one version of the same piece of information.
Having a dedicated writing or editing resource, such as that offered by Cherryleaf can help, but it's also important to look at the systems and tools you have in place for creating, maintaining and improving documents.
If you are using a word processor, you can format the headings with the preformatted styles contained in the word processor templates (For example "Heading 1" and "Heading 2" styles in Microsoft Word). A style within Microsoft Word is a set of formatting characteristics that you can apply to text in your document to quickly change its appearance. When you apply a style, you apply a whole group of formats in one simple task. Using styles makes it easier to make changes to the look and feel across the whole of the document, and makes it easier to import the content into other software at any stage in the future.
One popular approach is to have one source for content, allowing you to reuse pieces (or components) of information. These pieces are managed and maintained in a database, and then published to different audiences, documents, and in a range of media formats, such as print and online. You can write information once and re-use it many times, and make changes to it in one place. It promises a reduction in errors and duplication, time needed to review content, translation costs (as you can re-use content translated in the past), as well as better consistency.
For free documentation advice, please visit our Web site, and read the articles. Subscribe to our free Newsletter and we can keep you up to date with documentation issues.
Sign up to the FREE 1 Minute Documentation Audit from Cherryleaf to stay ahead of the competition.

This one minute documentation audit can help you identify in seconds, the real reasons why your user documentation isn't generating the results you want.