There is a particular kind of failure that doesn't show up at go-live. It shows up eighteen months later, when the project team has been reassigned, the steering committee has stopped meeting, and the planning platform that once represented a genuine shift in how the business operated has quietly drifted back toward the way things used to be done.
The Pattern Behind the Drift
Gartner's 2026 CFO Agenda, based on a survey of more than 200 CFOs, found that confidence in technology and talent-driven initiatives is declining even as investment continues. Cost optimisation dominates the agenda, but the underlying challenge is that many of the technology bets placed in previous cycles have not delivered the sustained operational change that was expected.
McKinsey research across 1,200 public companies over a ten-year period found that of organisations announcing cost-reduction and efficiency initiatives, only one in four was able to sustain the gains for more than four years. Finance transformation follows the same pattern. The initial improvement is real. What erodes is the operating discipline needed to maintain it once leadership attention moves elsewhere.
Why Good Transformations Regress
A transformation project has a defined end date. The operating model that's supposed to keep the new way of working alive often does not. When the project closes, governance closes with it, and decisions that used to go through a structured change process start happening informally again, department by department. McKinsey's 2025 research found that centralised capabilities routinely generate shadow functions within two years of implementation, as business units quietly rebuild the capacity they gave up.
Organisations change. New cost centres get created, products launch, reporting lines shift. A planning model that isn't actively maintained falls out of step with the business it's meant to represent, and every gap between the model and reality becomes another reason for someone to build a workaround. The 2025 FP&A Trends Survey found that a record 30% of organisations had not upgraded their planning systems in over five years. The platform is the same. The business it was built to model no longer is.
During an active transformation, adoption gets visibility: it's tracked, reported, and reinforced. Once the project ends, that visibility usually disappears. EY's research into finance transformation identifies a clear finding: leaders who put humans at the centre of transformation efforts are 12 times more likely to significantly improve performance. Most organisations invest in that human focus during the project. Few maintain it afterward.
If the deepest expertise in how the platform works sat with the implementation partner or a small project team rather than being embedded in the business, that knowledge leaves when the project does. Six months later, no one inside the organisation is confident enough to extend the model, so they stop trying and the model freezes in place while the business keeps moving. Gartner projects that CFOs expect one in two finance employees to be digital talent by 2027, yet digital talent currently makes up less than 20% of most finance functions.
What Sustaining Transformation Actually Requires
The organisations that hold their gains share a common trait: they treat the end of the project as the start of an operating responsibility, not the end of one.
Define a permanent owner before go-live, not after
A named role or small team, sitting in the business rather than in IT, is accountable for the planning platform's ongoing accuracy and relevance. This is not a help desk function. It is an active responsibility to keep the model current as the business changes. The 2025 FP&A Trends Survey found that only 9% of FP&A teams act as true strategic partners to senior leadership. The ones that do have one thing in common: internal ownership of the planning process.
Build a standing governance rhythm, not a one-off committee
A lightweight, recurring forum reviews what's working, what's drifted, and what needs to change in the model. McKinsey's 2025 research on organisational change recommends 90-day cycles of decision, action, and reflection as the mechanism for sustaining new capabilities. Applied to xP&A, this means a quarterly review of model accuracy, adoption health, and emerging workarounds, before small gaps compound into the kind of distance that drives people back to manual processes.
Transfer capability deliberately, not by osmosis
Rather than assuming knowledge will transfer naturally during the project, successful organisations build a specific plan for which internal people will be able to extend, troubleshoot, and adjust the platform once external support steps back. They test that capability before the project closes, not after. Given that Gartner finds the majority of finance functions still below 20% digital talent, this means deliberate upskilling during the engagement.
Keep measuring adoption after the project ends
The metrics that mattered during go-live, whether numbers originate in the platform unedited, whether business managers are engaging with the model directly, don't stop mattering once the project closes. The 2025 FP&A Trends Survey found that only 11% of organisations have achieved full integration of strategic, financial, and operational planning. That figure represents the ceiling for organisations that stop measuring after go-live, because what doesn't get tracked doesn't get maintained.
Where xP&A Makes This Harder, and More Necessary
Extended Planning and Analysis spreads planning ownership across finance, sales, supply chain, and HR rather than concentrating it inside finance alone. That's the point of xP&A: a shared, enterprise-wide view of the plan rather than a finance-owned process that other functions feed into. Research from Unit4 found that over 60% of companies are already using xP&A solutions for revenue performance management and workforce planning. The uptake is real. The governance required to sustain it at that scale is still catching up.
If finance is the only function still actively maintaining its part of the model a year later, the connected planning process xP&A was meant to create starts fragmenting back into the functional silos it replaced. Sustaining xP&A requires the same cross-functional governance that built it in the first place, just at a lower level of intensity, maintained indefinitely rather than for the life of a project.
How Decision Inc Approaches It
At Decision Inc, we design our xP&A engagements with the operating model that follows go-live built in from the start, not added as an afterthought once the implementation is complete.
That means defining, with the client, who owns the platform once our team steps back, what a sustainable governance rhythm looks like for their organisation, and what capability needs to sit inside the business rather than with us. Our project governance and change management methodology, applied across more than 400 client engagements per year, is built around handover as a deliberate phase of the project, with specific milestones for internal ownership and capability before we consider an engagement complete.
Across retail, government, mining, and beyond, the pattern holds: the transformations that last are the ones where someone inside the business was made responsible for keeping them alive, before the people who built them moved on to the next project.
A successful go-live proves a platform can work. A transformation that's still delivering value two years later proves something different: that the organisation built a way of operating that didn't depend on the people who built it.
That is the harder thing to design for, and it is the only version of success that compounds.