Significant investment, ambitious roadmaps, and capable teams — yet Finance transformations routinely underdeliver. We examine the structural reasons why, and what a better approach looks like.
Finance transformation programmes attract significant capital, executive attention, and consulting resource. They are launched with credible business cases, detailed project plans, and genuine organisational will to change. And yet, when we look at the landscape of Finance functions that have been through major transformation in the last decade, a consistent pattern emerges: the technology went live, but the function did not fundamentally change. Costs were not sustainably reduced. Insights did not improve. The promise of the business case remained largely unfulfilled.
This is not an isolated finding. It reflects a structural problem in how Finance transformations are conceived, governed, and delivered. Understanding why these programmes fail — and what distinguishes the ones that succeed — is essential for any CFO or Finance leader contemplating a major change programme.
The single most common failure mode we encounter is the conflation of system go-live with transformation success. Organisations invest in capable platforms — whether ERP modernisation, consolidation tools, or planning software — and treat the point of deployment as the destination. In reality, it is only the starting point.
A new system installed on top of old processes delivers old outcomes at higher cost. We have seen organisations migrate to cloud-based ERP platforms while preserving every manual workaround, every offline spreadsheet, and every approval exception that existed in the legacy environment. The technology was new; the operating model was not. The result was a Finance function that now had two sets of complexity to manage: the old ways of working, and the new system that nobody had been trained to exploit.
Effective transformation requires a genuine commitment to changing how work is done, not just the tools used to do it. That means process redesign that precedes system design, not the reverse. It means sustained investment in training, not a one-week go-live workshop. And it means building internal champions who can drive adoption over the months and years that follow implementation.
Related to the adoption problem is the gap between documented process and lived process. Many transformation programmes invest heavily in process mapping and design workshops that produce elegant flowcharts and RACI matrices. These artefacts are often technically correct. What they frequently fail to capture is the informal network of workarounds, judgment calls, and relationship-based exceptions that actually make the Finance function run day-to-day.
When the new process is designed without properly understanding the old one — including its informal logic — the result is a design that looks clean on paper but fractures under operational pressure. Teams revert to familiar patterns because the new process does not account for the edge cases they deal with constantly. Over time, the gap between the designed process and the actual process widens, and the transformation's gains erode.
The discipline of process mining — using transactional data to understand how processes actually run, rather than how they are supposed to run — has made significant strides in helping organisations close this gap. But technology alone is not sufficient. The real requirement is the intellectual humility to design processes that reflect operational reality, not just theoretical best practice.
Change management is the most frequently underinvested component of Finance transformation. It is typically treated as a communications workstream — a series of town halls, email updates, and training sessions scheduled in the final weeks before go-live. This approach consistently fails.
Genuine change management begins at programme inception. It requires understanding who will be affected by the change, how their day-to-day work will shift, what anxieties and resistances are likely to emerge, and how those concerns can be addressed through design choices, not just messaging. It means building a coalition of engaged stakeholders who have a genuine stake in the success of the new model — not just formal sponsors who have signed off on the business case.
"Resistance to change is not irrational. It is a rational response to uncertainty, perceived threat, and a track record of organisational changes that promised more than they delivered. Effective change management begins by taking that rationality seriously."
Change management in Finance transformation also requires specific attention to the professional identity of Finance teams. Finance professionals have built careers around particular skills — often including the management of complex, manual processes that a transformation is designed to eliminate. Without a clear narrative about what the new Finance function values, and how individuals can develop within it, change management becomes an exercise in managing anxiety rather than building momentum.
Finance transformations that succeed over the medium term have one consistent feature: sustained, engaged executive sponsorship that extends well beyond the point of go-live. Those that fail frequently exhibit a different pattern: strong sponsorship during the programme phase, followed by a rapid transfer of accountability to operational teams who were not sufficiently prepared to embed and evolve the new model.
Governance gaps manifest in several ways. Steering committees that convened monthly during the programme phase cease to meet. Benefits tracking, which was rigorous during implementation, becomes informal and eventually stops. Escalation paths that existed during the programme are dismantled without replacement. The programme office is closed before the operating model has genuinely stabilised.
The result is a Finance function left to manage a new system and new processes without the governance structures needed to make decisions, resolve conflicts, and course-correct when the design does not hold up against operational reality. Transformation gains erode not because the design was wrong, but because no one had the authority or accountability to protect and evolve it.
Finance transformations that genuinely deliver share several characteristics that distinguish them from the failures described above. First, they treat process redesign and technology implementation as parallel workstreams, not sequential ones — and they insist that the process design leads. The technology is selected and configured to support the desired operating model, not the reverse.
Second, they invest in change management as a substantive programme discipline, not a communications afterthought. This means dedicated change management resource with genuine organisational standing, a structured approach to stakeholder engagement, and a clear narrative that connects the transformation to outcomes that matter to the Finance team — not just to the CFO or the board.
Third, they maintain rigorous benefits governance beyond go-live. This requires a benefits realisation framework established at programme inception, with clear accountability for tracking and reporting on benefit delivery. It also requires the honesty to distinguish between benefits that have been delivered and benefits that have been assumed.
Fourth, they design for the Finance function they want to build, not just the one they want to escape. Too many transformations are defined primarily by what they are moving away from — legacy systems, manual processes, fragmented data — rather than by a clear and compelling vision of what excellent Finance looks like. A destination-led design is more likely to produce a programme that generates genuine organisational enthusiasm, and more likely to hold its gains when the inevitable pressures of operational life assert themselves.
Transformation is genuinely difficult. It requires sustained effort, careful design, and the willingness to confront organisational realities that are often uncomfortable. But the failure modes described here are well understood and, with the right approach, avoidable. The Finance functions that get this right do not just reduce costs — they build a fundamentally more capable function that can serve as a genuine strategic asset to the business.
Let's start with a conversation about your specific challenges.