CRM 2011: Considerations for Improving Information Systems

Nathan Eccles, 15 November 2012

Ever feel like your existing information system is tired and in need of some attention?

CRM 2011 Considerations for Improving Information Systems *

When looking to improve an information system there are 7 possibilities. You can; restructure, reengineer, refurbish, rejuvenate, re-architect, replace (with a package or service), or rewrite the system. 

These options should be carefully considered when looking to move your existing system to CRM 2011, or when making changes within your existing CRM system. 

Restructure the System

This approach is applicable if the underlying system itself is running as desired, but it runs inefficiently or is difficult to use. In this scenario the best course of action may be to restructure the system by removing unnecessary code and workflows, altering the sitemap so users only see the areas they need to access, and modifying form design to make for a better user experience. 

Re-Engineer the System

This approach is used to fix bits of the system which may not be working as desired. This might mean rewriting plugins or JavaScript to better meet the original business requirements, or recreating workflows to match business rules. 

Refurbish the System

If a system is working as desired and there are no immediate issues, refurbishing to add in new features and make the system more desirable to use may be an option. Within CRM this may mean adding new code to simplify user input, or creating new views to make it easier for users to see data. 

Rejuvenate the System

This approach is the step up from refurbishing in that the additional functionality added is valuable to the business. This includes tasks such as creating new workflows and dialogues to reflect business processes, or creating new charts to display useful data from the system. It could also mean creating entire new entities to store additional data. 

Re-Architect the System

If the system as a whole is operational and meets requirements, but significant improvements could be made, then re-architecting should be considered. This involves identifying a “to-be” architecture for a section of the system, which outlines how best that section should operate. Within CRM this might involve revising an entire area of functionality and re-constructing it in a more efficient manner following the “to-be” architecture. 

Replace with a Package or Service

If a system is no longer meeting requirements, or there are many disjointed systems in place, it may be most beneficial to simply replace the entire system with a single CRM package. Given the extensible nature of Dynamics CRM, one system can be implemented to manage and record customers, sales, marketing, services, and any other information driven business system. 

Rewrite the System

If the CRM system you are currently using does not meet business requirements due to poor design, sketchy or convoluted code, or misunderstandings during original development, it may be time to rewrite your entire system. This involves starting from scratch and going through the entire information systems development process, starting with a thorough business analysis. 

Here at Magnetism we are happy to help you to improve your existing systems, whether that be making minor changes to help the system run a little smoother, or completely redesigning and rewriting your system. 

If you’re interested, get in contact with use through our Contact Us form, or give us a call! 

* http://www.clker.com/clipart-broken-computer.html