Time saving for key personnel

You probably realise that your designers, software developers, marketing people or other key individuals who are responsible for writing your support documentation, would be better off employed doing real activities like designing, developing software or making sales?

There are major disadvantages to assigning skilled people with tasks as time-consuming as documentation which in most cases is out of their comfort and skill zone.

• They generally resent doing it.

• They may not be very good at it (after all, it's not usually what they're trained for).

• It holds up progress by diverting their attention from the tasks they do best.

• They frequently struggle to have the documentation ready.

This approach may be to difficult to define in your balance sheet, but in terms of lost time and focus, it can prove to be an expensive option. 

Our primary objective is to provide the best possible documentation with the least demand on your resources.

You will be surprised at just how little of their time we need!

Typically, our only requirements are:

• an initial walkthrough – similar in level to a demonstration that you might provide to a prospective client, but dealing with some behind-the-scenes detail. These walk-throughs are normally recorded for later transcription to a document which is far more effective than making notes.

• access to working software or hardware – neither of which need to be in their finished state, as we routinely document systems while still in development. Indeed, this is usually the best approach since it means that the system and its documentation can be ready for release at the same time.

• periodic access to relevant members of your staff throughout the project to answer specific queries.

Any existing documentation that may be available, such as user requirement and design specifications, are very useful but not essentia