The customer doesn’t schedule time for people to work on the project
Very very tight deadline
Colombo – Just one more thing otherwise known as scope creep
No Training – customer has no plans to train users how to use CRM
A “Manager” makes all process decisions not the users
A CRM initial release..gulp
The system will do everything
No CRM champion or influential backers
Development team is under manned or has no senior person to steer the ship
The project is dependent on a new third-party technology
The project start keeps getting delayed
Failed previous implementation
sometimes customers under-estimate the amount of time their people will need to spend on the project, to answer questions, clarify requirements and test the new CRM system. This is a vital part of the project and low customer involvement will increase the chance of creating a system which isn’t useful to them.
Very very tight deadlines are rarely met and if they are it’s because corners have been cut, be prepared for some nasty bugs to leap out.
When a new CRM system is being created, sometime customers take this as an opportunity to add more and more and more functionality, not because it’s needed but because they can.
The customers get a brand spanking new system, but all the users think it’s rubbish because they have no idea how to use it because there wasn’t any training!!!
In some projects a manager will decide they will make all decisions. They create a great system in theory, but forget to ask the users how they actually use the system and guess what, it isn’t the same as the manager imagined
Microsoft Dynamics CRM can have a few bugs which need ironing out in a new release. These bugs will be fixed, but it can take a month or so. This can make a stressful time whilst you wait for Microsoft to fix them up.
Functionality is added they hardly ever or never use. The simple CRM system can grow into a huge monster.
If no one on the project is really behind the new CRM system or if there isn’t a powerful backer in the company then the CRM system could be doomed.
Understaffed projects will be rushed and bugs thrive in this environment. Junior developers are often trying to get things to work rather than the best customization for each instance. These problems can be caught/managed if there is a good senior developer to keep things in check.
If the project is Dependant on an untested third-party software you could be heading for danger. Who knows how the software will perform under certain conditions or under a heavy lead, the main problem is you only find out when it’s too late.
Projects which keep getting delayed can cause problems. During this time key people can leave and business requirements can change. It’s difficult to keep picking up a project with the same enthusiasm. All in all it doesn’t lead to the best working environment.
Some customers won’t listen to advice and demand to have things done their own way. This can go against best practices and advice. This often leads to problems (which you pointed out to them earlier). Good CRM projects are a collaboration between the customer and supplier.
Failed previous implementations/projects can leave deep scars. Scared of being burnt again can cause a project to run very slowly with lots of checking and a lack of trust. This perhaps isn’t a true sign of failure, but a sign of a difficult project.