Your Microsoft CRM Project: Why You’ll Get Better Results By Biting Off More Chewable Chunks
How do you eat an elephant? One bite at a time. Likiewise, a CRM project should be taken one byte at a time.
One of the great strengths of Microsoft CRM is that it is more configurable (without customization or programming) than any of the other major CRM systems.
The downside is that easier configurability tempts executives to try to do too much, too soon-leading not only to escalating costs, but to a heightened risk of failure.
We're in an industry where somewhere between 50% and 80% of projects fail. The typical growing company has had two or three CRM failures before it reaches puberty. We have actually trained our users in the proper method of handling a CRM initiative: Stick your head in the sand and it will eventually go away.
What's the problem? Actually, there are several problems:
- One large complex projects is always more difficult to deploy than several smaller, simpler projects. Implementing a few small simple tasks enables you to spread your costs over several phases, so you can make sure you are getting a sufficient return on your investment for each phase. Less expensive and safer than a single big roll of the dice.
- Smaller simpler projects also give you a chance to see if you are comfortable with your VAR. If not, you can find a new one for the next phase.
-
Moreover, you deploy faster, and start enjoying
benefits sooner. This applies not only
to the time of development, but also the training time for your staff. And by letting them start with a simple
system and incrementally adding functionality, you increase the chances members
of your team will actually use the system (the ...
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us hereor login