A lot of companies put in systems because everyone else is. If that’s your reason, stop. You’re wasting your money.

Get serious about it. What do I mean by getting serious? Figure out who the best people in your company are and commit them to the project. By managing the project very carefully and having the best people involved in the project, by keeping the project moving along, and by getting it done quickly, I think we get far better results.- Denis Picard

Eighty/20 Post Review

Once the users see what they can do with the new system they often get a flood of creative ideas on how to use it .  When this happens there is a great temptation to add functionality to the system on the fly. Once again common sense in the Eighty/20 process kicks in. The priority should be to concentrate on getting to stability because nothing destroys confidence in a new system quicker than a never-ending stream of errors and problems.

If possible, all new requests for functionality should go into a new document for “Phase 2.”  This serves two important purposes; it lets each contributor know that their ideas are important and will be addressed, and it keeps proper focus on the implementation in progress.

At some point the consultant will sit down with the manufacturer to decide if there is a need for a “Phase 2.” If there is a need, then a process must be followed to prioritize the requests for additional functionality. The consultant should help to create clear specifications for each request that follow a standardized format.

The format identifies the business problem, the business benefits, the solution, the estimated work, and the costs.

In effect, the Eighty/20 process is starting all over again, and failure to do this systematically can hurt progress to date.

Contact Us | About Mike Liddell | APS | ERP | Seqencing | Scheduling | Lean Scheduling | Buy the Book | Home