Implementation

Commission OA Systems to implement your CRM of course!

At OA, we recommend starting with a discovery of what you think you want Dynamics 365 to do for you, as well as learning what your organisation presently does .

Often this leads to a restatement of what you want that encompasses things that you might not have previously identified, and sometimes de-emphasises things previously thought to be important. Once a clear statement of overall requirement is achieved then we can plan with you what the solution looks like, and what the plan to deliver that solution is.

For many organisations, this process has been a formal document, build, test and then deploy process. However, increasingly, OA is finding that a more agile process works, whereby an overall statement of requirement is derived, then broken down into a high level, prioritised list of functionality, which in turn is delivered in iterations, providing useful business functionality earlier in the project.

In some cases, this is deployed to a pilot team for the business, and in other cases to the whole business. Again, the current pre-eminence of the cloud means that you can licence an ever-growing team of users, allowing a phased adoption of your solution.

Key to implementation is training and change management. OA has found training of key stakeholders very early in the project gives them a better understanding of what the platform can do, leading to better expectation and change management for the wider business. Training for end users before adoption is vital to success. This need not be on your whole business process but can focus on the key paradigm of how Dynamics 365 operates.

Informed involvement by everyone is vital!