The Second Opinion Your D365 F&O Programme Probably Needs
Most Dynamics 365 Finance & Operations programmes do not fail at go-live. They fail quietly, months earlier, in a series of small decisions nobody thinks to challenge at the time. A customisation gets waved through because the business sponsor is travelling. A data migration workstream slips two weeks and nobody updates the critical path. A junior consultant replaces the architect who sold the deal, and the weekly status report still says "green." By the time the programme is visibly in trouble, the cost of fixing it is a multiple of what it would have been to catch it early.
This is not a Microsoft problem, and in most cases it is not really a partner problem either. It is a problem of who is watching.
The numbers are worse than people admit
Gartner puts ERP project failure, defined as missing the original objectives, somewhere between 55% and 75%. Industry coverage of Dynamics specifically is blunter: roughly 60% of failed Microsoft Dynamics installations are attributed to implementation problems rather than the product itself. Pearson Carter, recruiting into this market every day, estimates over 70% of ERP projects miss their goals because of poor planning, unclear outcomes, and weak implementation strategy.
The reasons are remarkably consistent wherever you look. Over-customisation that breaks with every Microsoft update. Data migration treated as a last-minute technical task. Performance issues that only appear under real production workloads. Vague business goals that give the implementation team nothing concrete to design toward. Scope creep with no change control. Fixed-price contracts that reward sign-off rather than outcomes. None of these are secrets. They appear in Microsoft's own FastTrack guidance, on MSDynamicsWorld, on the Dynamics Community forums, and in every retrospective consultants share with each other over a drink.
The uncomfortable question is: if everyone knows the failure modes, why do they keep happening?
Why problems do not get raised in time
In most F&O programmes there are three parties in the room. The customer, who is usually implementing F&O for the first or second time in their career and cannot calibrate what "normal" looks like. The system integrator, who has every commercial reason to keep the programme green on the status report until a problem becomes unavoidable. And Microsoft's FastTrack team, whose Success by Design workshops are genuinely useful but whose engagement is scheduled, not continuous, and whose remit is architectural rather than commercial.
Nobody in that triangle is paid to tell the customer, early and plainly, that the programme is drifting. The customer's own PMO often lacks the F&O experience to spot the warning signs. The SI's delivery lead is commercially conflicted. FastTrack will flag architectural risk but will not tell a customer their partner is thin-staffing the engagement or that the statement of work is impossible to deliver in the quoted budget.
This is the gap independent review is built to fill.
What independent review actually does
At Dr Dynamics we think of independent review as an assurance function that sits alongside the customer, not instead of their SI. The point is not to second-guess every design decision. It is to give the customer a trusted source of calibration at the moments where small problems are still cheap to fix.
In practice that means a small number of things, done well.
First, a realistic reading of programme health. Not the RAG status on the steering committee deck, but an evidence-based view: are the build velocity, defect trends, data migration readiness, and test coverage consistent with the go-live date the programme is still promising? This usually takes a week and produces findings that are uncomfortable but actionable.
Second, a customisation and technical debt review. Every accepted customisation is a future cost. Someone independent needs to ask, for each one, whether it is really required, whether a standard configuration would do the job, and what it will cost to carry through every future Microsoft update. Doing this at design time is cheap. Doing it at UAT is painful. Doing it in hypercare is a crisis.
Third, a data and performance readiness check before go-live. The most common cause of a "slow after go-live" F&O deployment is that the test environment never saw realistic volumes, concurrency, or batch sequencing. Catching this two weeks before cutover is possible. Catching it on the first Monday of live operations is a board-level event.
Fourth, and perhaps most valuable, honest conversations the customer cannot have with their SI. Is the bench being swapped out? Is the statement of work actually deliverable? Is the change control process working, or is scope quietly expanding every sprint? These are the questions that decide whether a programme comes in on budget, and they are the questions a commercially conflicted delivery partner cannot answer for itself.
Recovery is harder than assurance, but the same discipline works
Not every customer comes to us before the wheels come off. When a programme is already in trouble, the work looks different but the principles are the same. Get an unflinching view of reality. Decide what must survive and what can be cut. Rebuild the governance that was missing. Stabilise the data and testing workstreams. Re-plan with numbers the team actually believes.
Recovery projects are rarely about replacing the SI, even though customers sometimes arrive expecting that to be the answer. More often the partner is capable but has been set up to fail by weak decision rights on the customer side, a statement of work that was never realistic, and a governance structure that never existed. Fixing those is cheaper and faster than starting over, and it protects the investment already made. The independent reviewer's job is to make that path visible and credible to both sides.
When to call us
Three moments where an independent review pays for itself many times over.
Before you sign. A two-week review of the statement of work, the partner's proposed team, and your own readiness is the cheapest insurance in the programme. It will not make you popular with the SI selling the deal, but it will catch the problems that become invoices later.
At the gates. Design complete, CRP2, pre-UAT, pre-go-live. A short, focused review at each gate keeps the programme honest and gives the steering committee a second data point against the weekly status report.
When something feels wrong. If the status reports are green but the sponsor's instinct is that the programme is drifting, that instinct is almost always correct. The value of an independent review in that moment is not to confirm the fear. It is to turn a vague worry into a specific, fixable list.
D365 F&O is a capable platform, and most of the partners in this market are competent. The programmes that fail are almost never failing because nobody knew what to do. They are failing because nobody with the authority to act was looking closely enough, early enough, at the things that actually mattered. That is the job Dr Dynamics does. If you are in the middle of an F&O programme and the last paragraph sounded a little too familiar, it is probably time for a conversation.
Dr Dynamics provides independent reviews, assurance, and recovery services for Microsoft Dynamics 365 Finance & Operations programmes. We work alongside customers and their delivery partners to catch problems while they are still cheap to fix, and to bring troubled programmes back on track.
Read more: Solution Blueprint Review (Independent) | Dr Dynamics