Most ERP implementations start the same way:

Document the AS‑IS
Design the TO‑BE
Argue about it endlessly, and eventually find ourselves back at the beginning

This roundtable‑style session creates a safe space for open and direct discussion around one of the most common ERP realities:

ERP implementations rarely fail at design.
They erode due to missing or undocumented business processes, a lack of process‑driven structure, and unclear ownership.

Together, we’ll explore how the Microsoft Business Process Catalog can serve as a living backbone for ERP implementations, not just during the project, but long after go‑live.
The discussion will focus on business‑process‑led implementations, rather than module‑driven, siloed designs, and how this shift impacts adoption, stability, and long‑term value.
This is not a product walkthrough or a methodology lecture.
It’s a real‑world, experience‑driven conversation, focused on:

Why AS‑IS processes are often outdated before the project even begins
How TO‑BE designs drift once delivery teams step away
Where process ownership disappears, both before and after go‑live
How a living Business Process Catalog helps close the gap between design and reality
Using Microsoft Business Process Catalog for stabilization, governance, onboarding, audits, and continuous improvement

Participants are encouraged to share examples, lessons learned, and good, bad, and ugly insights from their own ERP journeys.
Minimal slides.
Maximum participation.
No judgment, just shared learning.

Participants Will Leave With

A clearer understanding of AS‑IS vs TO‑BE limitations
Practical ideas for keeping business processes alive before and after go‑live
Stronger language to articulate process value to business owners and leaders
Patterns and insights learned from peers across the Microsoft ecosystem