 |  |
|
|
|
|
|
|
|
|
|
|
|
|
Unless your new system is very simple, there will be a lot more about it than just the computer. The way people work and interact will change. Old expertise will become irrelevant and new skills needed. | Nine Steps up the Ladders |
Be prepared for a " learning experience" |
|
|
| |
 |
Decide at the outset what you want the computer to do, how you want it done, and how it will benefit your business. This is especially true when setting up databases as they may be hard to change later. | Decide what you want, and why your business needs it |
|
|
|
 |
Mr Macho switches on the PC and looks for the button to press to make his business go faster. It's much better to plan the project thoroughly before you start, and try and anticipate the problems. | Curb your impatience and plan the project |
|
|
|
 |
Your shiny new system will only work if the users want it to, so involve them at every stage. They will also know how the job is really done in the office and will be able to see how it can be improved. | Consult the users endlessly |
|
|
|
 |
Sorting out the 'bugs', training the users, and entering all the data into the computer are things that cause extra delays when you think you've almost finished. Allow plenty of time for them. | Allow time for training, setting up data, and fixing bugs |
|
|
|
 |
Be prepared to bring in extra help. The businesses we work with often use students on 'sandwich courses', during their vacations, or on post-graduate computer training schemes. | Bring in extra help if needed |
|
|
|
 |
Every computer application in your business should have an 'owner' who is responsible for keeping it working, helping the other users to make good use of it, and fussing over it when it is not well. | Make sure every system has an owner |
|
|
|
 |
A computer project needs a lot of commitment from you and your staff. If you succeed you will be ahead of your competitors. If you don't, you will have wasted a lot of time and effort getting nowhere. | Commitment, commitment, commitment |
|
|
|
 |
'Big Bang' implementations can blow up in you face. It's nearly always best to implement in a series of steps that seem almost too simple. That way you build and learn in easy stages. | Keep it simple |
|
|
|
 |
 |
|
|