System Implementation and After Implementation Considerations, Research Paper Example

Implementation strategy

The implementation strategy adopted depends on individual organization based on their goals, timeframes and requirements. In a nutshell however, majority of organizations adopt two types of implementation strategies. They entail ‘the big bang’ strategy of implementation and the ‘phased-roll out’ approach (Guerrero, 2012). The use of ‘the big bang’ involves a single big action during implementation with all the system users being forced to shift to a new system within a given period of time in the course of implementation. Some of the users are usually hurt by this strategy.

The ‘phased-roll out’ approach on the other hand entails small changes being executed over a prolonged time duration and involves a prearranged plan of sequential steps that facilitating for adequate transition from the old system to the new one. This can easily be achieved through module, business unit or geographically in case the organization has multiple locations.

Importance of system documentation

Keeping the documentations of a system up-to-date is associated with some benefits. This facilitates avoidance of crucial errors in the system. Preservation of the system history is also made possible during diverse stages of the system lifecycle such that the users and maintainers have an easy time. The role of updating the documentation is reserved for the maintainers. Through documentation, people who are unfamiliar with system functionality and structure are taught the design motifs of the system. Software interpretation is also facilitated by documentation. On successful investment of along with efforts, documentation is effectively applied with no effect on the process. However, a problem might arise when particular problems that are associated with system design are encountered and a guide is not available. This is as difficult as trespassing through the jungle with no compass or map, which only translates to loss of time and money (Health Resources and Services Administration, 2015). Although documentation is an intensive process particularly when handling a complex system and on large scale, the benefits derived after successful execution are worth the task after all.

The ongoing system maintenance requirements

The processes of verification, testing as well as implementation of a system have been accomplished, the nest most important process involves maintenance of the process to facilitate effective and uninterrupted performance thus allowing the system to adapt to any upcoming requirements as the need may arise (Guerrero, 2012). This process might sometimes call for systematization to facilitate easy identification of the needs for maintenance. Some scenarios of the system are anticipated to meet extended application which thence requires a suitable mechanism that is able to monitor any feedback coming from the users so as to identify the requirements for maintenance as well as modification. The routine of maintenance is determined to a large extent by complexity of applicable technology in a particular system. Majority of the items in a system are associated strict maintenance schedules and recommended maintenance schedules as specified by the vendor and it is a part of the agreement made at purchase. In some cases of maintenance and upgrade, some modifications are made to the hardware, the software as well as communication which subsequently necessitate additional verification along with testing to ascertain that updated specifications are met.

Causes of system implementation successes and failures

The pattern of the processes followed during implementation plays a crucial role in determining the success as well as the failure of a system (Guerrero, 2012). Some of the most crucial facets during the process of implementation include the following:

• The conflict arising between orientation of machine in the information system of the specialist and the orientation of the company user
• The impact that is associated with information system on the structures of the company, behavior as well as work groups.
• The planning along with the management in the activities of system development.
• The extent to which the user participates in the processes of design as well as development.

The failure of the system could be attributed to some factors that are out of the organization. Such factors include pressures associated with external environment that the company might not address unless it runs against the inherent characteristics of the business (Guerrero, 2012). However, majority of the cases involving system failure along with the outcomes of the implementation process are attributed to factors that arise from within the business.

Handling the successes and failures during implementation process

One of the most important considerations in this regard entails good planning that can be achieved superb forward planning. In this case, consider detailed planning during all the stages of implementation process, the timeliness of tasks, fall-back positions as well as re-planning.

Clear responsibility as well as team members accountability is also a worth course in handling the successes and failures during implementation process. All team members must be equipped with coherent comprehension of the roles as well as the duties that they are entitled to as well as their expectations visa-a- vis the measurable achievements (Health Resources and Services Administration, 2015). Scheduling of control is an equally crucial parameter in handling the successes and failures during implementation process

References

Guerrero, A. (2012). Planning a successful EMR project management strategy. Retrieved from http://www.meaningfulusenetwork.com/planning-a-successful-emr-project-management-strategy/

Health Resources and Services Administration (2015). What skills are needed to implement and support an EHR system? Retrieved from http://www.hrsa.gov/healthit/toolbox/RuralHealthITtoolbox/Project/skillsehr.html