|
To The Point Technical Writing
|
 |
Your job requires that you write technical documents that technical and non-technical people can understand. You might be a field engineer having to supply reports to the home office or customers. You have a lot of information to convey. You keep getting questions and you have to spend extra time explaining what you've written.
|
 |
A one-day customized learning experience that will use your own company's documents. Topics covered include:
| • | Purpose and organization of data
| | • | The three most wordy technical writing constructions
| | • | Active and passive voice
| | • | Technical writing cliches
| | • | Readability
| | • | Stylistic needs of non-technical and technical readers
|
|
 |
Technical writers and those who must convey technical information will:
| • | Increase their writing confidence and speed
| | • | Create technical memos, e-mails, and letters that any reader can understand.
| | • | Formulate procedures that emphasize action rather than explanation
| | • | Draft change requests, specifications, and protocols that clarify rather than confuse
| | • | Write test reports that focus on the most important data and subordinate the rest
|
|
 |
"I think this class should be a required part of everyone's professional
development plan."
- Project Manager, Lucent Worldwide Services
|
 |
Lucent Worldwide Services • Scient • Qualcomm • KPMG
|
