This episode is sponsored by Mavim.

Business process modelling touches nearly every element of a Dynamics 365 ERP or CRM project, from the customer's requirements and goals to a partner's pre-sales engagement to Microsoft's own platform and tools for project execution.

On this episode we speak with Edwin Jongsma of Mavim, makers of BPM tooling built on Microsoft technology, about the variety of ways in which BPM fits into Dynamics projects today. 

We discuss some of the subtle but important reasons to focus on business process transformation from the diagnostic stage of a project onward, and why having a platform to support BPM leads to successful outcomes for both an individual project and for managing a broader IT portfolio.

Microsoft has a role to play in BPM for Dynamics 365, Edwin notes. The Lifecycle Services platform is one obvious touchpoint, as is the Catalyst methodology for envisioning and planning solutions. And Power Platform's low-code/no-code tools, have an important role to play in both defining business process and reflecting an organizations needs. 

And, Jongsma argues, partners should be applying BPM concepts to provide industry models and process expertise to shorten the diagnostic phase and provide better guidance. 

Show Notes:

• 1:45 - Why the diagnostic phase of a Dynamics project is so important
• 3:30 - Observations on Microsoft's Catalyst Framework
• 5:30 - Why customers should define a clear roadmap to their 'to-be' state on D365 F&O
• 8:00 -
• 10:45 - How to avoid the risks of typical ERP projects by connecting people and technology
• 12:00 - Why customers should expect partners to have to-be models already developed based on industry expertise
• 14:30 - Positive outcomes in project phases after a successful diagnostic phase
• 19:00 - How expertise in BPM fits with Microsoft's Power Platform value proposition

More from Mavim:

• How to optimize the diagnostic phase of your next Microsoft Dynamics 365 project (Article)
• Going Cloud on a Deadline? It's Never Too Late to Find a Better Way (White Paper)
• Low Code No Code and Business Process Management (White Paper)