More ERP work is often the wrong answer because ERP transformation is not a technology installation. It is a cultural, behavioural, and organizational shift that must be absorbed in stages. Trying to solve everything at once overwhelms the organization before it has built the capability to sustain change.

Why CFOs Want Everything Solved at Once

The instinct is understandable, and it comes from a good place.

Most CFOs recognize that an ERP transformation of this scale is something an organization may only do once. The investment is massive. The disruption is real. The window of organizational attention is finite. Naturally, the impulse is to make sure nothing is missedto solve every problem, close every gap, and deliver a complete solution in a single effort.

This instinct would be correct if ERP implementation were simply a technology tool introduction; a system swap where the old platform goes away and the new one appears with all features configured.

But it’s not.

Why the “Solve Everything at Once” Approach Fails

ERP transformation is a fundamental change in culture, behavior, and cross-functional collaboration. It redefines how people work together, how decisions are made, and how outcomes are measured. That kind of change cannot be absorbed in a single pass, no matter how well-planned the project is.

When organizations try to do everything at once, they encounter predictable failures:

•Change fatigue. Teams are overwhelmed by simultaneous process changes, system changes, and behavioral expectations they haven’t had time to internalize.

•No early signals. When everything is delivered as one large effort, there are no intermediate checkpoints to measure whether the organization is actually adopting the changes or just surviving them.

•Hidden dysfunction. Problems that would have been caught early in a phased approach stay buried until the full scope is live, when the cost of correction is highest.

•Cultural resistance hardens. When people can’t see incremental wins, they lose confidence in the transformation. Resistance grows instead of dissolving.

The desire to get it all done at once is the right ambition applied with the wrong execution model.

Rome Wasn’t Built in a Day

ERP transformation at this scale is not a sprint. It’s the construction of something enduring, and enduring things are built in stages.

An organization that tries to transform culture, behavior, and cross-functional collaboration all at once is like a weekend jogger signing up for the Olympics. The ambition is admirable. But without building stamina, capability, and muscle memory first, the attempt collapses under its own weight.

The organizations that succeed at ERP transformation are the ones that learn to walk before they try to run. They introduce change in smaller chunks. They measure progress and improvement in terms of team collaboration early on. They build confidence and capability phase by phase, so each stage supports the next.

This is not about doing less. It is about building the organizational capacity to do more, sustainably.

The False Comfort of “Keeping Things Moving”

“Keeping momentum” is one of the most expensive ERP myths.

Momentum without prioritization rewards speed over impact, masks trade-offs, pushes decisions downstream, and creates rework that finance absorbs later.

MVP1st consistently sees ERP instability worsen when progress is measured by tickets closed instead of outcomes achieved. Activity accelerates. Clarity does not.

This is the point where ERP stops feeling like an investment and starts feeling like exposure.

What CFOs Actually Need Before Approving More Work

Before authorizing additional ERP effort, CFOs need answers to a smaller set of questions:

•Which issues increase financial or compliance risk? Not everything is urgent. Distinguish real risk from perceived urgency.

•Which problems block growth? Identify the constraints that actually limit the business, not the ones that frustrate individual teams.

•Which fixes reduce future rework? Prioritize changes that eliminate downstream correction over changes that add new capability.

•What happens if we do nothing? The most clarifying question a CFO can ask. If the answer is “nothing material changes,” the work can wait.

•Has the organization absorbed the last round of changes? New work should not begin until the previous phase has been measured, adopted, and stabilized. Adding more before the team has built capacity guarantees diminishing returns.

ERP assessments exist to answer these questions before more work gets approved, not after cost overruns appear.

When Less ERP Work Creates Better Outcomes

Paradoxically, CFOs regain control fastest when they:

•Pause execution briefly to reassess priorities against enterprise objectives.

•Define what not to fix so that scope is governed by intent, not accumulation.

•Measure adoption before adding scope. Each phase must demonstrate that the organization has internalized the change before the next phase begins.

•Align remaining work to business outcomes so that every approved effort traces back to the transformation’s defined objectives.

This doesn’t slow progress. It prevents waste and builds the organizational stamina required to sustain long-term transformation.

Rome wasn’t built in a day, but it was built. One stage at a time, with each layer strong enough to support the next.

Strategic Difficulty Beats Flawless Execution: A Lesson from Milan

The 2026 Winter Olympics in Milan offered a striking illustration of this principle. In the figure skating team event, Japan’s Shun Sato delivered a technically flawless free skate; three quad jumps, positive execution grades on every element, no mistakes. It was, by any conventional measure, a perfect performance. America’s Ilia Malinin, by contrast, attempted five quads, tripled a planned quad, had to fight to stay upright on a landing, and took visible deductions. He was measurably imperfect.

Malinin won gold. Sato took silver.

The difference was not execution quality. It was strategic difficulty. Malinin’s program was built around moves no one else could attempt, elements of such high base value that even with deductions for imperfect execution, the total exceeded what a flawless but less ambitious program could produce. Sato was perfect at a level of difficulty the scoring system valued less than Malinin’s imperfect attempt at a level of difficulty only he could reach.

The ERP parallel is direct.

And the outcome can still fall short of an organization that prioritizes fewer, higher-impact elements and accepts imperfection where it does not determine the result.

The CFO’s role is not to demand perfect execution across every dimension. It is to ensure the transformation is weighted toward the decisions that determine business value. Some deductions along the way are not failure. They are the cost of attempting what matters most.

An ERP transformation that executes imperfectly on the right priorities will outperform one that executes flawlessly on the wrong ones every time.

Not sure whether more ERP work will actually help?

If the instinct is to add more work because problems keep surfacing, the real question is whether the organization has built the capacity to absorb what’s already been delivered. More scope on top of unabsorbed change doesn’t accelerate transformation, it overwhelms it.

The answer is often to slow down, measure what exists, and build from strength.

Talk to an MVP1st expert before approving more work without clearer priorities.

FAQ

Does stopping ERP work increase risk?

No. Continuing without clarity increases risk faster. Pausing to assess whether prior changes have been absorbed is one of the most effective risk-reduction actions a CFO can take.

Isn’t ERP progress always better than delay?

Only when progress is tied to prioritized outcomes and the organization has demonstrated readiness for the next phase. Progress without adoption is activity, not advancement.

Who should decide when to pause?

Finance should lead the decision, informed by IT and operations. The CFO has the broadest visibility into whether additional work is creating value or compounding exposure.

How do you know if the organization is ready for more?

Measure adoption of the current phase. If teams are still relying on workarounds, haven’t changed behaviors, or can’t articulate how the last round of changes improved their work, the organization isn’t ready for more.