This article provides a practical framework for discussion. The right answer depends on the specific Dynamics 365 configuration, requirements and constraints of your organisation.
Define the process outcome
Start with what the business needs to achieve and control.
Separate mandatory from preferred
Not every current-system behaviour is a future-state requirement.
Demonstrate standard D365 early
Use targeted walkthroughs and POCs to validate assumptions.
Document exceptions
Capture volume, frequency, materiality and edge cases.
Challenge customisation
Require a clear business case and lifecycle justification.
Close the loop
Every gap needs an owner, decision, solution route and acceptance criteria.
Experiencing this in your D365 environment?
Use a focused review to separate root causes from symptoms and define the right next action.
Use a focused review to separate root causes from symptoms and define the right next action.