Why Improved User Friendliness Doesn’t Translate Into Easier Implementation for Microsoft Dynamics CRM

Microsoft Dynamics CRM is a wonderful application, but occasionally, Dynamics CRM projects fail. In my experience, there are three primary causes for a CRM implementation to fail:

1. Inappropriate requirements. The key to Dynamics CRM implementation success is to develop the right business requirements. I have seen many projects where the requirements were changed, and then changed some more, and then changed again. Dynamics CRM is a very flexible application, and changes can be applied quickly, but the odds of a project failing increase as more changes are built in to the requirements.


Requires FREE Membership to View

Become a Member Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more, and it’s all FREE. You’ll also receive periodic email newsletters with the latest relevant articles and content updates.
About Sandor Schellenberg

Sandor Schellenberg is the owner and founder of friendlyITsolutions, which mainly focuses on Microsoft Dynamics CRM and related software in the Microsoft stack. He is a Senior Microsoft Dynamics CRM Consultant/Solution Architect and is specialized in data migration & integration. In autumn 2009 his work was recognised and rewarded with a invitation to Scribe Software MVP Program. 

His roots in Microsoft-based Internet technologies go back more than twelve years, and since 2005 he has specialized in Microsoft Dynamics CRM. Starting with his first guest post on the blog of Menno te Koppele, he decided to start his own blog, Friendly Microsoft CRM Monster, a blog with a wink. The blog is widely read in the Dynamics CRM community and focused mainly on Microsoft Dynamics CRM technical and integration/migration topics.

Read full bio...