![\"Risks](\"\/wp-content\/uploads\/Risks-Intro-1.jpg\")
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.<\/p>\n
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<\/strong>, or decisions about unnecessary customizations<\/strong>, or a tendency to automate your legacy business processes<\/strong> on the new system, or a wide range of other issues that are under your<\/em> 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.<\/p>\n The Framework\u2019s 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.<\/p>\n We believe an association should not be blindsided by hidden risks when implementing an AMS, LMS, or Website. That\u2019s why the Risk Register<\/strong> 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.<\/p>\nWhat We Believe<\/h2>\n
![\"Risks](\"https:\/\/iscgi.com\/wp-content\/uploads\/Risks-Intro-2.jpg\")
<\/a><\/h2>\nThe Framework helps you mitigate risks before they occur<\/h2>\n
Examples of some of the most common risks:<\/strong>
\n
\nRisk #1:<\/strong><\/span>\u00a0 Scope Creep<\/a>
\n
\nRisk #2:<\/strong><\/span>\u00a0 No Focus on Business Process Change<\/a>
\n
\nRisk #3:<\/strong><\/span>\u00a0 Problems with the software & integrations are not uncovered until after go-live<\/a>
\n
\nRisk #4:<\/strong><\/span>\u00a0 Over-customizing can take you off the upgrade path or make upgrades extremely costly<\/a>
\n
\nRisk #5:<\/strong><\/span>\u00a0 Unrealistic expectations about the internal effort required to develop custom screens and workflows with the vendor\u2019s software development toolkit<\/a>
\n
\nRisk #6:<\/strong><\/span>\u00a0 Project is viewed as an \u201cIT-owned\u201d initiative; lack of staff engagement<\/a>
\n
\nRisk #7:<\/strong><\/span>\u00a0 Under-estimating the time commitment needed from staff to make the project successful<\/a>
\n
\nRisk #8:<\/strong><\/span>\u00a0 Assumption that the AMS\/LMS\/Website vendor will manage all aspects of your project<\/a>
\n
\nRisk #9:<\/strong><\/span>\u00a0 Data \/ Content Conversion not given the proper attention<\/a><\/p>\n