Why are Failures so Common?
- Risks Not Identified
- Business Processes Remain Unchanged
- Budget & Timeline Expectations Not Met
Risks Not Identified
Study after study show that implementing a new AMS, LMS, or Website is fraught with risks. Projects frequently go over budget, exceed timeline expectations, and do not achieve the value originally envisioned. The risk of failure is particularly high for associations that do not have the expertise or experience to guide a complex technology project to a successful conclusion on their own.
Success or failure is not determined by the actions of your new system vendor alone. The vendor does not control aspects of the project such as requests that cause scope creep, or decisions about unnecessary customizations, or a tendency to automate your legacy business processes on the new system, or a wide range of other issues that are under your control. Success depends on planning for the inevitable risks your project will face, and executing a proactive risk mitigation strategy throughout all phases of the project.
The Framework’s Risk Register identifies more than 90 common risks inherent in new system implementations, and guides you through best practice strategies for addressing problems before they occur. A Risk Management emphasis is embedded throughout the Framework in order to help you navigate through problematic areas that often derail the implementation of an AMS, LMS, or Website system.
What We Believe
We believe an association should not be blindsided by hidden risks when implementing an AMS, LMS, or Website. That’s why the Risk Register is included as a core part of the IT Guidance Framework, to reduce the risks and help you formulate a proactive plan to mitigate the consequences.
The Framework helps you mitigate risks before they occur
Examples of some of the most common risks:
Risk #1: Scope Creep
Risk #2: No Focus on Business Process Change
Risk #3: Problems with the software & integrations are not uncovered until after go-live
Risk #4: Over-customizing can take you off the upgrade path or make upgrades extremely costly
Risk #5: Unrealistic expectations about the internal effort required to develop custom screens and workflows with the vendor’s software development toolkit
Risk #6: Project is viewed as an “IT-owned” initiative; lack of staff engagement
Risk #7: Under-estimating the time commitment needed from staff to make the project successful
Risk #8: Assumption that the AMS/LMS/Website vendor will manage all aspects of your project
Risk #9: Data / Content Conversion not given the proper attention