
|
Most of our writing supports some kind of equipment or system. It can support requirements capture, the design and manufacture of the product (hardware or software), its contractual acceptance or its long-term successful operation. Most of the material we write falls into one of three categories:
We use illustrations and examples whenever we can. Experience has shown us how a simple graphic (maybe a message flow diagram or an isometric sketch) saves people from struggling to visualize an idea - and stops them coming to a wrong conclusion. |
We use Developing Quality Technical Information (Hargis and others, IBM) as our reference for topic-based writing and especially for creating instructional material. Read more about our bookshelf. We can tailor each specification and handbook to use your in-house conventions and templates or, if you prefer, we can use our own standards. We understand the technical concerns of your development engineers and the more task-orientated objectives of your customer and end user. The result is writing pitched at the right level for each reader - writing which informs, educates and reassures. Here are some of our applications and techniques. |