| How
To Write A User Guide (2d/2) |
|
| A user guide is a step-by-step list of instructions for a USER of the a system. The user guide must be simple to follow and have text and pictures to help them do there job. | |
| Each sub-system that you have created must have a user guide so that the user knows what to do. Assume that the user has very little or no knowledge of how to the their job now that you have introduced a computer system for them. | |
| You should have already described the training that the users will need, so the user guide should help them until they are confident of doing their job properly. | |
| Remember to use plenty of screen prints and descriptions to help the guide to be as easy to follow as possible. | |
| DESCRIBE STEP-BY-STEP HOW TO DO A PARTICULAR TASK. | |
| Below is a list of your sub-tasks and what you should write about each one. | |
| Once your user guide has been developed you must get some ‘users’ (other people) to test it and give you some suggestions for improvement (feedback) and you need to make these improvements to your guide. There is a form to help you do this. You will end up with a ‘Draft Version User Guide’ and a ‘Final Version User Guide’ | |
| Your User Guide should have step-by-step instruction for: | What Instructions are needed: |
| Using the logo | How would a user put the logo onto the top of letter (letterhead)? |
| Updating the Customer database | How would a user add or edit the details in the database? |