DRIVE 2026

Using the BPC in All Phases of a Dynamics Implementation

How can you apply the Microsoft Business Process Catalog consistently across all five Dynamics 365 Success by Design phases?

Key takeaways of this session:
  • ✔ Gain a clear understanding of the Microsoft Business Process Catalog and how it is structured within the Mavim platform.
  • ✔ Understand how Mavim adds value to every phase of the Success by Design framework.
  • ✔ Learn how Mavim enhances the experience for Dynamics 365 end users through smart deep links and AI integrations.
duration 23 minutes
who is this webinar for
Business Owners, Dynamics 365 Project Consultants, Dynamics 365 Solution Architects, End Users
Summary
Dynamics 365 implementations often fail due to unclear process scope, disconnected workshops, and limited alignment between business and IT. In this webinar Lennard explains how the Microsoft Business Process Catalog - imported into Mavim - supports every phase of the Success by Design framework, from strategize to operate. Clear scope decisions, structured fit‑gap analysis, synchronized DevOps execution, and continuous process improvement after go‑live.
Speakers
 
Lennard van Leuven Value Engineer, Mavim
 
video Chapters
00:29
Microsoft Business Process Catalog explained
03:01
Using the catalog in Strategize & Initiate phase
14:10
From Mavim to Azure DevOps during implementation
16:37
Training, Copilot, and Continuous Improvement after go-live
In partnership with logo_no tagline

 

From Static Process Documentation to Continuous, Data-Driven Execution

An overview of how the Microsoft Business Process Catalog is applied in Mavim across all five Success by Design phases to connect business processes, implementation work, and operational improvement.


solutions
Fragmented Process Understanding Blocks Execution

Traditional Dynamics implementations rely on static documents, manual workshop notes, and disconnected Visio diagrams. Scope decisions, fit‑gap analysis, and process ownership are scattered across files and tools. This causes rework, unclear priorities, and limited traceability once implementation starts, especially when business and IT teams work in silos.

problem-solving
Implementations No Longer Tolerate Ambiguity

The Success by Design framework requires clear scope, structured analysis, and traceable decisions across all phases. Without a shared process foundation, organizations struggle to control risk, prioritize extensions, and prepare end users. Delays surface during implementation and again after go‑live when processes no longer reflect reality.


exclamation-mark
From One-Off Design to Continuous Process Control

The approach shifts from documenting processes once to managing them as a living system. Processes, roles, scenarios, and decisions evolve together through strategize, initiate, implement, prepare, and operate phases. This supports iterative design, structured execution, and continuous alignment with how Dynamics 365 is actually used.

not-equal
One Process Model Reused End-To-End

The Microsoft Business Process Catalog in Mavim covers 781 processes in this demo environment, with 71% requiring no extensions and 29% requiring changes. Fit‑gap details, risks, and priorities flow directly into Azure DevOps as work items, reducing translation effort and keeping business and implementation teams aligned throughout the project.

“End users can jump directly from a process into the exact Dynamics 365 screen where they need to work”

FAQ's

What is the Microsoft Business Process Catalog

The Microsoft Business Process Catalog is a structured collection of business processes, scenarios, and implementation guidance for Dynamics 365. It provides a standardized process taxonomy that helps organizations understand and organize business operations before configuration or customization begins. 

How does the catalog support the Success by Design framework?

The catalog aligns with the five Success by Design phases: strategize, initiate, implement, prepare, and operate. Each phase uses the same process foundation for scope definition, discovery workshops, fit‑gap analysis, implementation execution, training, and continuous improvement.

How is fit‑gap analysis handled in Mavim?

For each process, fit‑gap fields are used to indicate whether the standard Dynamics 365 process fits or requires changes. When a gap exists, priority, risk, effort, and time criticality are captured and later reused during implementation and reporting

How does Mavim integrate with Azure DevOps?

Processes in Mavim are synchronized to Azure DevOps as work items. All fit‑gap details, risks, and descriptions are transferred automatically. The DevOps work item ID is linked back to the originating process in Mavim, maintaining traceability between business design and implementation work.

What happens after go-live?

After go‑live, end users can view processes in the Mavim portal, give feedback directly on processes, and use Copilot integrated with Dynamics 365 to ask process‑related questions. Process owners receive notifications and can update processes, supported by process mining based on Dynamics event logs.