13 signs your Dynamics 365 project is doomed

Image for post
Image for post

How does a project get to be a year late? One day at a time. Fred Brooks

  1. The customer doesn’t schedule time for people to work on the project
  2. Tight deadlines
  3. Colombo — Just one more thing otherwise known as scope creep
  4. No Training — customer has no plans to train users how to use Dynamics 365
  5. A “Manager” makes all process decisions not the users
  6. A Dynamics 365 initial release..gulp
  7. The system will do everything
  8. No Dynamics 365 champion or influential backers
  9. Development team is under manned or has no senior person to steer the ship
  10. The project depends on a new third-party technology
  11. The project start keeps getting delayed
  12. Not listening
  13. Failed previous implementation


  1. 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.
  2. When a new Dynamics 365 solution is being created, customers can take this as an opportunity to add nice to have functionality, not because it’s needed but because they can.
  3. The customers get a brand spanking new system, but all the users think it’s rubbish because they do not understand how to use it because there wasn’t any training!!!
  4. 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 use the system and guess what, it isn’t the same as the manager imagined
  5. Microsoft Dynamics 365 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.
  6. Functionality is added they hardly ever or never use. The simple Dynamics 365 solution can grow into a huge monster.
  7. If no one on the project is behind the new Dynamics 365 solution or if there isn’t a powerful backer in the company then the CRM system could be doomed.
  8. Understaffed projects will be rushed and bugs thrive in this environment. Junior developers try to get things to work rather than the best customization for each instance. These problems can be caught/managed if there is a senior developer to keep things in check.
  9. If the project is Dependant on an untested third-party software. 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.
  10. 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.
  11. 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 Dynamics 365 projects are a collaboration between the customer and supplier.
  12. Failed previous implementations/projects can leave deep scars. Scared of being burnt again can cause a project to run 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.

Written by

Have been working with Dynamics 365 since version 4 and enjoy reading and delivering enterprise projects

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store