CRM Project Plans – Where Does It All Go Wrong?

by Jim Berkowitz on January 26, 2010

leadership2 CRM Project Plans   Where Does It All Go Wrong? Here are several excerpts from a post by Richard Boardman, CRM Project Plans – Where Does It All Go Wrong?:

For those of you currently planning a CRM project, I thought it might be helpful to identify some of the areas where things tend to go ‘off-piste’, but before I do perhaps it’s a good idea to suggest why we might care in the first place.

If the CRM project team come under time pressure, either through underestimating the time-line or through unforeseeable disruption, the, not unnatural response, is to try and speed things up. Unfortunately, often with limited things that can be sped up, this leads to cutting corners in some form or another. Commonly this manifests itself in dumbing down the requirements, reduced testing, and rushed training, which in turn invariably ends with user adoption issues which may ultimately prove insurmountable.

Therefore understanding which bits of the implementation process are prone to delay is a key way of effectively managing time-line expectations. So the following are my top six areas where people tend to get caught out…

  1. Contract negotiation
  2. System design
  3. Any key sign off point
  4. Data-load
  5. User acceptance testing
  6. User adoption

Then of course there’s the less foreseeable. In a recent project, pretty much the whole of the vendor project team were made redundant, which was more than mildly disruptive. These situations are not easy to cater for, however making reasonable allowance for the standard phases of an implementation is key to staying away from potentially perilous route of trying to deliver on a project plan that was never achievable in the first place.

Check out the complete source article for more detail on each of the above six areas where projects run into problems.

{ 3 comments… read them below or add one }

MarenKate January 29, 2010 at 2:42 am

Thanks for the points. I have a team and i think i’ll be needing this kind of informations to make them effective.

Arturo F Munoz March 22, 2010 at 7:36 pm

I think system design should be split into design vs. fit, because with SaaS vs. on-premise solutions you’re not designing a system but determining instead how well the existing model provided by the SaaS might match the process demands that your organization has envisioned.

With a SaaS you get rapid deployment but you trade off customization flexibility, and working through those trade-offs can take time.

Intelestream Inc June 14, 2010 at 3:52 pm

At Intelestream we have written a whitepaper containing important considerations when planning a CRM project. It can be read at our web page.

Leave a Comment

Security Code:

Previous post: Lotus Knows Social Media, But Do Customers?

Next post: Four Reasons for an Information Concierge