PROFILE #0006 · Microsoft First-Party Products
Care Quality Commission
A £90 million-scale transformation built around Microsoft Dynamics 365 struggled because organizational change, process redesign, and technology implementation moved faster than the organization could absorb.
- Status
- Recovered
- Year
- 2024
- Founded
- 2009
- Funding
- UK public-sector programme
The Idea
The Care Quality Commission (CQC), the independent regulator of health and social care in England, launched a major transformation programme between 2019 and 2024.
At the technology level, the organization moved from a legacy CRM system to a bespoke cloud-based regulatory platform built on Microsoft Dynamics 365. The new platform was intended to replace the legacy CRM capabilities while also providing broader ERP functionality.
But the project was much larger than a technology replacement. CQC was simultaneously attempting to introduce a fundamentally different operating model, redesign core processes, change organizational structures, and implement a new technology platform.
The Rise and Fall
The transformation encountered serious problems.
An independent IT review commissioned by CQC in late 2024 concluded that the primary cause of the technology failure was a failed organizational transformation. The report found that CQC had attempted to change core processes, structures, roles, and technology at the same time, creating an unstable foundation for the technology implementation.
The technical consequences included poor software releases, data-quality problems, complex assessment processes, and a poor user experience. The review also identified unrealistic timelines, reliance on contingent labor, and technical problems in the software development process.
The financial scale also increased substantially. CQC’s whole-life cost estimate grew from approximately £57.5 million to £131.8 million as scope and programme duration expanded. A UK Parliament response later reported actual spending of £92.4 million against an £88.3 million budget for the regulatory platform.
Importantly, the independent review did not conclude that Dynamics 365 itself was unsuitable. It stated that the D365 platform was technically capable of supporting the required CRM/ERP solution, but that substantial rebuilding and development work was required.
Why It Failed
CQC is a powerful example of organizational transformation failure becoming technology failure.
The project tried to solve too many problems simultaneously:
- redesign the operating model;
- change business processes;
- introduce a new technology platform;
- build a bespoke regulatory application;
- and deliver the transformation under aggressive timelines.
When business processes are still changing, software requirements become moving targets. When organizational ownership is unclear, technology decisions become difficult to govern.
What Happened Next
The independent review did not recommend replacing Dynamics 365. Instead, it concluded that the regulatory platform was salvageable and recommended retaining D365 as the strategic platform while substantially rebuilding the application.
The review also recommended strengthening internal capability, reducing reliance on contingent staff, improving governance, and gradually moving toward a more modular architecture.
Lesson: A modern ERP/CRM platform cannot compensate for an unstable operating model.
The technology may be technically capable, but implementation success depends on having sufficiently stable business processes, clear ownership, realistic delivery plans, strong internal capabilities, and disciplined governance.