My second tip for writing is to understand the purpose of the document. Why are you are writing it and how do you intend for it to be used?

• Are you aiming to entertain or inform your reader (or both)?
• Is the reader required to follow a process or comply with governance? A process diagram may form the backbone of the document and your writing will be the flesh on the bones.
• Do you need the reader to make a decision after reading the document? Be up front about any decisions required and repeat it at the end so it’s clear.
• What are the implications if your message is misunderstood? If you are writing a technical specification you want to be sure there is no room for misinterpretation.