It Project Implementation Failures

IT Project Implementation Failures
When implemented correctly, a computerized provider order entry (CPOE) is able to provide organizations and patients with many benefits.   Errors related to medications can be reduced.   Test results and prescriptions can be received in a more timely fashion.   Fewer administrative staff may be needed.   Billing may be more accurate and received faster.   Reductions in transcription errors can occur.   A CPOE also provides medical personnel with features like support with decisions.   With the many benefits of implementing a CPOE, risks are also present.   There are many indicators of a project that is likely to fail (Wager, Lee, & Glaser, 2009).   The case study of Memorial Health System CPOE Implementation portrays several indicators of project failure.
Failure Indicators
The first indicator of project failure that manifests in the cast study is that there was a lack of belief in the project.   Some stakeholders of the health system considered the project controversial.   Several physicians out-right opposed the project (University of Phoenix, 2011).   The University of Phoenix (2011) shares, “They worried their workload would increase because CPOE systems replace verbal order with computer-entered orders by doctors.”   The time-line given for the project was questioned by several board members (University of Phoenix, 2011).
A failure to respect uncertainty becomes apparent as several prominent physicians protest by taking their referral business to another local health system.   This health system gave them the promise that no CPOE would be used.   Not long after, the CPOE's two project champions left Memorial Health System (University of Phoenix, 2011).
Another indicator of project failure surfaced when a very vocal opponent of the IT project was appointed as the new chief executive officer (CEO).   Though the new champion opposed of the project, many board members were still supportive of it.   Insufficient leadership support...