Later Errors
A common misconception is that the project is complete once the system has been installed, tested and gone-live, but the consequences of ignoring the activities during the Review phase of the systems lifecycle are equally damaging to the success of a system implementation. The infoKit on Creating an MLE contains a section on embedding which contends that many attempts to deliver e-Learning have not managed to get beyond the initial 'project' implementation stage and gone on to use the technology to change teaching and learning practice.
Here are a few examples of mistakes made after the system has gone-live:
| Inadequate internal and external resources have been appointed to technically support the system post go-live or to speedily resolve those issues that existed when the system went live and those that inevitably arose afterwards. |
| Internal user groups have not been established or retained to continue the communication with users to identify and resolve new issues, implement system upgrades and address new requirements. |
| The organisation has not been involved with external user groups or other institutions using the same system to specify new sector requirements, communicate them to the supplier and encourage development of the enhancements to meet those needs. |
| A productive working relationship with software suppliers has not been maintained to ensure that patches, enhancements and upgrades are applied in a timely and practical manner to resolve the issues that inevitably arise. |
| The implementation has been assumed to reach conclusion even though some functionality and aspects of the complete business cycle have not been implemented initially and have been deferred to a later date. |
| Implementing the conventional functionality of the software has been the focus at the expense of management and business information reporting requirements which have failed to be addressed, even though the benefits to be realised were recognised and there were genuine plans to deal with them at a later date. |
Of course, many mistakes are also made during the actual process of implementing a system and these can lead to project failure even if an ideal system solution has been selected, contract negotiations have been amicable and concluded satisfactorily for all parties and the project has been planned, resourced and managed well.
Implementing any system demands a thorough understanding, detailed planning, close management, continual monitoring and wide communication of the many activities involved.
