Most leaders go into digital transformation with the right intent: modernize operations, improve visibility, and future-proof the organization. The problem is that the industry often sells an oversimplified story, one where the software is the hero, the implementation is mostly “execution,” and the business value shows up automatically once the system goes live.
In reality, transformation is messy, political, and human. And the mistakes we see today are often the same ones we saw a decade ago, because while the technology has evolved, the way organizations buy, govern, and implement that technology hasn’t changed nearly enough. Here are the inconvenient truths that leaders need to acknowledge early, before the project starts defining them.
People will be your biggest transformation challenge, and they’re usually underfunded
The most consistent root cause of transformation failure isn’t the technology. It’s the people side: resistance, confusion, lack of ownership, and leadership misalignment that often remain unresolved. Yet most programs still spend the majority of their budget and attention on technical work streams, configuration, integrations, data migration, and testing, while change management gets treated like a checklist item.
A “working” system doesn’t mean a working business. You can meet every contractual deliverable, complete every test script, and still fail operationally because adoption never happened. The hard truth is that transformation succeeds when people change how they work, not when software gets installed. Leaders almost never look back and say they invested too much in change management. The regret is always the opposite.
“AI-ready ERP” is often marketing more than reality
Just when the market was saturated with cloud hype, AI became the new headline. While AI can absolutely deliver value, the term “AI-ready” is now used so loosely that it often becomes meaningless. Many products are labeling long-standing capabilities, like planning algorithms or analytics features, as “AI,” or they’re selling roadmap promises as if they’re production-ready today.
The smartest way to cut through AI-washing is to insist on realism. If a vendor can’t show the capability live, in your day-in-the-life scenarios, using workflows your business actually runs, then it’s not a capability you should plan your transformation around. Leaders need to separate what exists now from what might exist later, and what looks impressive in a demo from what will actually get used in the business.
Your legacy system may be more mature than the “modern” replacement
This one surprises executives, because “modernization” is often framed as an obvious upgrade. But many organizations are moving from deeply mature, heavily optimized legacy systems to newer cloud platforms that are still catching up in core capabilities, especially for complex industries like manufacturing, distribution, and asset-intensive operations.
Yes, cloud platforms often come with newer capabilities, improved analytics, emerging AI features, and easier update cycles. But they can also reduce flexibility, limit customization, and create real process compromises. Leaders need to be honest about the tradeoffs. Modern does not automatically mean better for your business, especially if you’re sacrificing workflows or differentiators that were working well.
“Best practices” don’t come out of a box
Software vendors love to say their systems include best practices. The uncomfortable truth is that “best practice” is usually just “the way the software was designed.” That doesn’t mean it’s wrong, but it also doesn’t mean it’s optimal for your organization.
Every business has unique complexities, regulatory constraints, customer promises, operational models, and competitive differentiators. The best practice for your business is the one that supports your strategy and operating model. That’s something leadership must define. If you outsource that definition to software or to an implementation partner, you risk standardizing the very things that made you successful in the first place.
Vendors and integrators often have incentives that don’t match yours
This is where many leaders feel uncomfortable, because it challenges the assumption that major brands automatically mean safety. The reality is that most vendors want to sell software quickly, and most system integrators want to staff large teams quickly. Their business models reward speed to signature, bigger scope, and longer project duration.
That doesn’t mean they are “bad actors,” but it does mean their incentives aren’t naturally aligned with yours. A time-and-materials model can reward overruns. A fixed-fee model can reward corner-cutting. Either way, if you don’t have strong governance and cost controls, the project can start managing you rather than the other way around.
You manage the integrator; they do not manage you
One of the most damaging mistakes organizations make is deferring decision rights to their implementation partner. It often happens subtly: leadership assumes the integrator knows best, the project becomes “their plan,” and internal teams start treating vendor guidance as fact instead of input.
No integrator, no matter how large, should ever have ultimate authority over your transformation. This is your business, your risk, your operating model, and your future. The integrator is one contractor inside a bigger program. Leaders must keep governance inside the organization, even if they bring in outside experts to support it.
Phase Zero is the most skipped phase, and often the most valuable
Most organizations treat transformation like a race: sign the contract, start the project, bring in the army of consultants, and “figure it out as we go.” That approach almost guarantees wasted spend and early chaos, because you’re paying a high run-rate before the organization is aligned on what it’s building, why, and how success will be measured.
The most valuable stage of transformation often happens before the implementation begins. This is where you resolve leadership misalignment, define scope boundaries, clarify decision-making, establish governance, and build a realistic plan for data, adoption, and change. If you skip this step, the vendor ecosystem will fill in the blanks for you, and they’ll do it in a way that benefits them more than it benefits you.
Cloud lock-in and cost creep will become tomorrow’s regret if you ignore it today
Cloud adoption can be the right move, but leaders need to recognize what comes with it: recurring subscription increases, add-on licensing, and limited ability to reverse course. Once you’ve migrated and redesigned your operating model around a vendor’s cloud platform, switching becomes far harder than it was ten years ago.
That means you must negotiate with your future self in mind. Transparency around pricing, clear contract terms, data portability, and exit options should be part of the decision, not afterthoughts once the deal is signed.
The bottom line
Digital transformation isn’t a technology project. It’s an organizational change effort enabled by technology. Leaders who acknowledge that early, and fund people, governance, and readiness as seriously as they fund software, dramatically improve their odds of success.
If there’s one message to take away, it’s this: you don’t need to be anti-vendor or anti-consultant to win, but you do need to be clear-eyed. Own the PMO. Invest in adoption. Demand proof over promises. And don’t confuse “big name” with “low risk.”
If you want a deeper dive into these realities (including real-world case studies), my new book Welcome to the Jungle explores what causes transformations to fail, and what successful leaders do differently.
Eric is recognized globally as a leading voice in digital transformation and ERP strategy. Over the past two decades, he has helped hundreds of organizations – including Nucor Steel, Fisher & Paykel Healthcare, Kodak, Coors, Boeing, and Duke Energy – define their technology roadmaps, modernize complex operations, and deliver real business value from large-scale transformation initiatives.
As Founder and CEO of Third Stage Consulting, Eric leads an independent, technology-agnostic advisory firm focused on helping clients navigate the shift from traditional ERP to more flexible, AI-enabled Digital Enterprise Operations (DEO) models. His work spans ERP selection, implementation quality assurance, organizational change, and operating model design across a wide range of industries and geographies.
Eric is also a prolific thought leader, known for his pragmatic takes on AI, cloud, and enterprise software trends, as well as his firm’s benchmark research and frameworks for de-risking transformation. He is dedicated to helping executive teams cut through vendor hype, make confident investment decisions, and successfully reach the “third stage” of their digital evolution.
