Often the people reading reports do not have the same level of understanding or expertise as the writer. It is often hard for the writer to “dumb-down” and create a document that is easy to read and consequently effective.
This practical workshop deals with the skills needed by technical experts to get their messages across to the lay person. It focuses the writer on understanding the reader and the effect technical language has upon them. It gives the technical writer ways to pitch their reports so that they get the results they want.
After this two-day workshop you will :
 |
 |
 |
have a greater knowledge of the syntax involved in report writing |
 |
 |
 |
have a better insight of the report reader |
 |
 |
 |
be able to write more focussed reports |
You can expect to:
 |
 |
 |
learn to write with the reader in mind |
 |
 |
 |
write more focussed reports |
 |
 |
 |
write effectively without using technical jargon |
Introduction
 |
 |
 |
The writing process |
 |
 |
 |
Speaking and writing |
 |
 |
 |
Focus on the reader |
 |
 |
 |
Describing a machine |
Getting to Grips with Language
 |
 |
 |
Types of nouns |
 |
 |
 |
Verb forms |
 |
 |
 |
Active and passive sentences |
Writing the Report
 |
 |
 |
Sections of reports |
 |
 |
 |
Organising material |
 |
 |
 |
Headings |
 |
 |
 |
Links |
 |
 |
 |
Writing coherently |
Choosing the Right Words
 |
 |
 |
Plain English |
 |
 |
 |
Redundancy |
 |
 |
 |
Technical language |
 |
 |
 |
Explaining and defining |
 |
 |
 |
Writing clear instructions |
 |
 |
 |
The jargon game |
Polishing a Report
 |
 |
 |
Using diagrams |
 |
 |
 |
Expressing ideas: conclusions |
 |
 |
 |
Expressing ideas: recommendations |
 |
 |
 |
Editing for clarity |
 |
 |
 |
Writing clear instructions |
 |
 |
 |
The jargon game |
Anyone in a technical profession who needs to write reports. IT staff, engineers etc.
|