Digital Transformation Underdelivered? What to Do Next

Your transformation project went live. The vendor left. Leadership moved on to the next initiative. But on the operations floor, things don’t feel better. Data still lives in spreadsheets. People still chase approvals by email. The new system sits half-used while the old workarounds persist.

In PwC’s 2026 Digital Trends in Operations Survey of 767 operations and supply chain leaders, 89% said their technology investments had not fully delivered the expected results. If that number surprises you, it shouldn’t. Most operations managers we talk to nod when they hear it.

So skip the “why transformations fail” retrospective. You already know that part. What follows is what to do right now to close the gap between where you are and where you were promised you’d be.

Start with a Diagnosis, Not a Verdict

The first instinct after a disappointing transformation is to blame the software. Sometimes that’s fair. More often, though, the system can do what it was supposed to do. The problem sits somewhere between the technology and your team’s daily work.

Before you rip anything out, run a structured diagnosis. Separate three categories of underperformance:

Configuration gaps. The system was set up wrong, or set up for a generic business rather than yours. Fields are missing, workflows don’t match your actual process, reports pull the wrong data.
Adoption gaps. The system works fine, but your team isn’t using it. They’ve gone back to email, spreadsheets, or manual workarounds because the new way feels slower or less trustworthy.
Expectation gaps. The system does exactly what it was designed to do, but leadership expected more. The business case oversold what technology alone could deliver.

Each category requires a different fix. Configuration gaps need technical work. Adoption gaps need people work. Expectation gaps need honest conversations with leadership about what “success” really means.

How Do You Know Which Gap You’re Dealing With?

You can run a simple diagnostic in a single week. Walk through your three or four highest-volume workflows and answer these questions for each one:

Can the system handle this workflow end to end? If not, you have a configuration gap. Document what’s missing or broken.
Does the team actually use the system for this workflow? If the system can handle it but people bypass it, you have an adoption gap. Talk to the people who bypass it. They’ll tell you exactly why.
Does the workflow produce the outcome leadership expected? If the system handles it and the team uses it, but the results still disappoint, you have an expectation gap. The workflow may be working as designed but the design doesn’t solve the business problem it was supposed to solve.

Most underperforming transformations have all three gaps in different workflows. The diagnosis tells you where to focus first.

Fix Configuration Gaps Before Anything Else

Configuration problems are the easiest to fix and the most damaging to leave in place. Every day your system runs with bad configurations, it teaches your team not to trust it.

Common configuration gaps we see across mid-size businesses:

Approval workflows that don’t match reality. The system routes approvals through a chain that doesn’t reflect how decisions actually get made. People skip the system because the system skips them.
Missing fields or validation rules. Data goes in incomplete because the system doesn’t require the fields your downstream processes need. Someone ends up fixing data manually at month-end.
Reports that answer the wrong questions. Standard reports shipped with the system, but nobody configured them for your actual KPIs. Your team pulls data into Excel to build the reports they actually need.

The fix is specific and technical. Make a list. Prioritize by impact on daily operations. Work through it with your implementation partner or internal IT team. This isn’t a second transformation. It’s finishing the first one.

Deloitte’s research on digital transformation value found that organizations with mature value tracking mechanisms are 2.5 times more likely to achieve their projected ROI compared to those with ad hoc tracking. If your system went live without clear metrics tied to operational outcomes, fixing that gap is part of the configuration work.

Adoption Gaps Aren’t a Training Problem

When a team doesn’t use a new system, the default response is “more training.” That rarely works. People almost always know how to use the system. They just find that using it makes their job harder, slower, or less reliable than the old way.

Adoption gaps have predictable causes:

The new workflow takes more steps. If entering an order in the new system takes 12 clicks instead of 6, people will find shortcuts. That’s rational behavior, not resistance.
The system doesn’t surface the information people need. If an operations coordinator has to open four screens to see what they used to see in one spreadsheet, they’ll keep the spreadsheet.
Performance is measured the old way. If your team’s targets assume the old workflow speed, they can’t afford the productivity dip that comes with learning a new system. Research from Panorama Consulting shows that 60% of ERP implementations experience significant user resistance, and temporary performance dips of 10 to 20% are normal during transition periods.
The old system is still available. If people can fall back to the old way, they will. We’ve seen this repeatedly with mid-size businesses: keeping legacy systems accessible as a backup actively prevents adoption rather than providing a safety net.

The fix for adoption gaps is not more training. It’s removing the friction that makes the old way feel better. Simplify the workflows. Customize the views. Adjust performance targets during the transition. And yes, eventually, turn off the old system.

The Expectation Gap Is the Hardest Conversation

Sometimes the transformation did exactly what it was scoped to do, and the result is still disappointing. The business case promised outcomes that technology alone can’t deliver.

A new ERP won’t fix broken processes. It will automate them. If your quoting process was slow because of unclear pricing rules, an automated quoting tool will produce wrong quotes faster.

A new BI platform won’t make people data-driven. It will give them access to dashboards. If nobody had time to analyze data before, they won’t have time after. We covered this pattern in our post on why operations teams don’t use BI tools.

Closing the expectation gap requires an honest reassessment. What did the transformation actually deliver versus what was promised? Where is the distance between “the system can do this” and “the business is actually achieving this”? That distance is your remaining work, and it usually isn’t technical. It’s process redesign, role clarity, and operational discipline.

Build a 90-Day Recovery Plan

Once you’ve diagnosed the gaps, you need a plan your team can execute alongside their daily work. Not a second transformation, but a focused effort to get value out of the investment you’ve already made.

Weeks 1 to 2: Prioritize ruthlessly. From your diagnostic, pick the three workflows with the largest gap between current performance and expected performance. Everything else waits.

Weeks 3 to 6: Fix and adjust. For each workflow:

Close configuration gaps (technical fixes).
Simplify the user experience (fewer clicks, better views, relevant defaults).
Set clear, measurable targets for what “working” looks like in this workflow.
Remove access to legacy workarounds where possible.

Weeks 7 to 10: Measure and iterate. Track the metrics you set. Compare to baseline. If a workflow improved, move to the next one. If it didn’t, dig into why.

Weeks 11 to 12: Report and reset. Show leadership what improved, what didn’t, and what’s left. Reset expectations with data, not promises.

In our experience, this focused approach recovers more value in 90 days than most “phase two” projects recover in a year. The difference is specificity. You’re not trying to “optimize the system.” You’re fixing three things, measuring the results, and moving on.

When Should You Cut Your Losses?

Not every underperforming transformation can be salvaged. Sometimes the right answer is to stop investing in the current system and plan a replacement. The distinction looks like this:

Worth recovering:

The system has the capabilities you need, but configuration and adoption are the bottlenecks.
Your team’s complaints are about usability, not fundamental functionality.
The vendor is responsive and willing to support post-go-live optimization.
The data in the system is mostly accurate, just underused.

Consider replacing:

The system cannot support your core workflows, and it’s a product limitation, not a configuration issue.
Integration costs with your other systems keep growing with no ceiling.
The vendor has stopped investing in the product or won’t answer support requests.
You’ve accumulated so many workarounds that the system creates more work than it eliminates.

If you’re in the second category, read our post on the sunk cost trap in technology projects before deciding. The money you’ve already spent is gone. The question is whether the next dollar goes further on this system or a different one.

Frequently Asked Questions

What percentage of digital transformations fail to deliver expected results?

The numbers vary by source but stay consistently high. PwC’s 2026 Digital Trends in Operations Survey found that 89% of operations leaders say their technology investments haven’t fully delivered expected results. McKinsey and Boston Consulting Group research puts the broader digital transformation failure rate at roughly 70%.

How long does it take to see ROI from a digital transformation?

Most mid-size businesses should expect 12 to 18 months before measurable ROI shows up, though some operational efficiency gains can appear within the first quarter after go-live. Deloitte found that organizations with structured value tracking mechanisms realize ROI 2.5 times more reliably than those measuring ad hoc.

Why do employees resist using new systems after implementation?

Resistance is usually rational, not emotional. People revert to old methods when the new system requires more steps, doesn’t show the information they need, or when performance targets don’t account for the learning curve. Panorama Consulting found that 60% of ERP implementations see significant user resistance, often because the new workflow is genuinely slower or less intuitive than what it replaced.

Should you replace a system that isn’t delivering results?

Not automatically. Most underperforming systems have configuration and adoption problems, not capability problems. Run a diagnostic first: can the system handle your workflows end to end? If yes, the issue is configuration or adoption, and both are cheaper to fix than a full replacement. Only consider swapping the system when the product cannot support your core operations at a fundamental level.

How do you measure if a digital transformation is actually working?

Focus on operational outcomes, not system metrics. Instead of measuring “number of users logged in” or “records created,” measure the business outcomes the system was supposed to improve: order processing time, error rates, time to close the month, approval cycle time. If those numbers are moving in the right direction, the transformation is working, no matter what adoption dashboards show.

How Tier2 Keel Supports Post-Go-Live Optimization

The recovery framework above works with any system, but it’s built into how Tier2 Keel operates. Keel’s unified architecture means configuration changes like new workflows, adjusted approval chains, and custom views don’t require development cycles or vendor escalations. Your team can adjust how the system works as they learn what the operation actually needs.

Because Keel covers the full business lifecycle from leads through invoicing and settlement, the “data lives in three systems” problem that drives most adoption gaps doesn’t apply. Your operations team works in one place, with one set of data, using views designed for their specific role.

If your current system is underdelivering, see how Keel handles it differently or book a walkthrough with our team.

Your Next Step

An underperforming transformation is not a failed one. The system is live. The data is there. The investment is made. The only question worth asking now is: what specific, measurable thing are you going to fix this week? Pick one workflow. Diagnose it. Fix it. Measure it. Then do the next one.