Sure, certain vendors offer toolkits that help preserve the upgrade path, but the more customizing you do, the more cost and associated work will be needed to ensure that new releases will work without problems. More importantly, customizing your system so that it is different from the vendor\u2019s other clients will make you more dependent on the specific vendor\u2019s staff who designed and developed your customizations.<\/p>\n
Customizations commit you to a never-ending cycle of testing, verification, and potential re-engineering for each new release<\/h2>\n
Best case, you will need to budget for the cost (and time) to test and verify that your customizations work with each new release.<\/p>\n Senior management should play a leadership role during the discovery phase. Department directors should be \u201chands-on\u201d alongside staff during the discovery meetings. Delegating this vital phase of the implementation, or being partially involved, oftentimes increases the risk of over-customizing. Over-customizing can take you off the upgrade path or make an upgrade extremely costly You need staff\u2019s creative ideas for how a new AMS, LMS, or Website can make your organization more effective. The best time to gather these ideas is when you are formulating your initial strategy and creating your requirements document for an […]<\/p>\n","protected":false},"author":5,"featured_media":0,"parent":20,"menu_order":30,"comment_status":"open","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"acf":[],"_links":{"self":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages\/59"}],"collection":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/comments?post=59"}],"version-history":[{"count":0,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages\/59\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/pages\/20"}],"wp:attachment":[{"href":"https:\/\/iscgi.com\/wp-json\/wp\/v2\/media?parent=59"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"Risks4b\"](\"https:\/\/iscgi.com\/wp-content\/uploads\/Risks4b.jpg\")
<\/a>In a worst case scenario, customizations will take you off the upgrade path and prevent you from upgrading to the vendor\u2019s next release. In addition to risking the upgrade path or diminished support, over-customizing is costly and will delay the timeline to go-live.<\/p>\nHow to avoid over-customizing<\/h2>\n
\n
\n<\/a><\/a>
\n
\nStaff must avoid the temptation to recreate the same business processes on the new system as used on the old system. Your focus should be on business process improvement<\/a> (see Risk #2) rather than asking the vendor to replicate the same functions as your old system. If customizations are identified, the Framework\u2019s ROI\u00a0Value Analysis<\/strong> and Change Management<\/strong> templates can be used to determine which customizations can be logically justified. The Framework provides the guidance and templates needed to prioritize which customizations are necessary for go\u2011live, and which can be deferred to a subsequent phase. In the end, it is up to senior management to ensure that the right customizations are done for the right reasons.<\/p>\n<\/a><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
![\n<\/a>](\"https:\/\/iscgi.com\/wp-content\/uploads\/Risks4a.jpg\"){kind=link}