Implementation

The first step to successful software implementation begins with a well-designed plan for selecting the right software for your business. Once you have done this, the plan for implementation should be a logical extension of the planning process already started.

As the work shifts from the selection stage to actual implementation, the project manager will work with the software integration team (management, staff, and software company representatives) to create an integration plan.

While each company has its own unique requirements and no two integrations are the same, we can provide the following introductory list of recommendations for project managers and those involved in the implementation process:

1. Begin with a clear understanding of your requirements including factors involving people, process, and technology. If these issues were not thoroughly documented during the software selection stage, it is important to take time to do so prior to beginning implementation.
2. Document key project milestones and associated expectations and requirements including for time, budget, and quality.
3. Review the plan frequently and revise as necessary. Successful integrations most often involve a mix of effective pre-planning and plan updates as the project evolves. A good implementation plan allows for a reasonable level of flexibility in order for you to get the most out of ERP software within your company.
4. Communicate regularly with team members about progress. Should a barrier or problem exist, take time to understand it and document the issue. Next, ask if the issue has further implications which need to be understood and, if so, by whom?
5. Ask questions frequently. It is vitally important, especially early on, that everyone is on the same page and agrees on what is being done and what is to be expected. Good questions are the lifeblood of successful software implementation.
6. Identify from the start how you prefer to communicate with others about the project. Clearly, much of what is done requires written documentation. However, there is plenty of opportunity to take advantage of how you best like to be involved and manage a project from a communications standpoint.