Procurement transformation at year two: why the second year kills most programs

By now the statistic is well known: approximately 70% of digital transformations fail to meet their objectives. McKinsey, BCG, and Bain have been reporting versions of this number for years. Bain's 2024 analysis put the figure at 88% for business transformations that fail to achieve their original ambitions. The global cost of failed digital transformation efforts is estimated at $2.3 trillion per year.

But the 70% number hides a more telling pattern. Most transformations do not fail at launch. They do not fail during vendor selection or system integration. They succeed in year one and stall in year two. The technology goes live on time. Users are trained. Initial spend flows through the new system. The steering committee celebrates. Then — quietly — adoption plateaus, savings stop compounding, and the program loses sponsorship. By month 18, the original ambition has been replaced by a maintenance budget and a shared sense that "transformation" is something the organization tried once.

This pattern is especially acute in procurement. Deloitte's 2025 Global CPO Survey found that nearly 70% of procurement leaders name digital transformation as a top priority for 2026, yet only about one-third feel fully prepared to execute it. The gap between ambition and readiness is the exact breeding ground for the year-two stall.

The year-two stall is not a technology problem

The critical insight, and the one most organizations miss, is that the stall is not caused by the technology. McKinsey's research consistently finds that culture and people factors — belief, trust in leadership, clarity of purpose — are the largest obstacles to digital transformation, more significant than technology itself. When teams lose confidence, "even the best-designed programs grind to a halt," as one McKinsey analysis put it.

DeepStream's research on procurement digitisation specifically cites failure rates of 70–84% globally and "up to 80% in procurement," tying failures not to tool selection but to vision gaps, change management deficits, and organizational readiness. Whatfix notes that many procurement initiatives "stall after implementation because organizations treat them as one-time projects, not ongoing commitments."

The pattern repeats across industries. Year one metrics — on-time go-live, trained user count, initial spend through the system — do not measure genuine behavior change. They measure project management. Year two reveals whether the organization has actually adopted the new way of working. Most have not.

---

Four mechanisms that drive the stall

Understanding why transformations stall in year two requires seeing the four specific mechanisms at work. Each is predictable. Each is preventable.

Mechanism 1: Deployment is mistaken for adoption. The most dangerous assumption in any transformation is that go-live equals change. Project teams celebrate the deployment date, but the organization has not internalized the new process. Users quietly work around the system. They revert to spreadsheets, email approvals, and the procurement manager's personal phone. The system records transactions, but the real workflow has not changed. By the time anyone notices that savings projections have not materialized, the behavior is already entrenched.

Mechanism 2: Early savings create unrealistic expectations. McKinsey's procurement benchmarks show that organizations acting quickly in the first six months can capture approximately 16% of a two-year savings goal within the first three months. This creates a dangerous signal: the program appears to be ahead of plan. Sponsors relax. The change management budget is reduced. But the early savings came from low-hanging fruit — contract renegotiations, license reclamation, process standardization on a single tool. The harder work — changing how category managers evaluate suppliers, how business units request procurement services, how finance validates savings — has not started. When the low-hanging fruit is gone, the savings curve flattens, and the program is labeled a failure.

Mechanism 3: Sponsor attention shifts. Transformation programs require sustained executive sponsorship for 18–24 months minimum. In most organizations, the CPO or COO who championed the program in year one has moved to a new priority by year two. Deloitte's CPO survey data shows procurement is under a structural workload squeeze — workloads rising 10% while budgets grow only 1% — creating constant pressure to reallocate attention to the next crisis. The program that was the CEO's priority in January is the forgotten initiative by December.

Mechanism 4: Capability building is under-invested. Deloitte's research highlights digital literacy and AI fluency as core skills for tomorrow's procurement teams, not fringe capabilities. Most transformation budgets allocate 80%+ to technology and 20% or less to training, role redesign, and capability building. The result is a workforce that has new tools but has not developed the judgment to use them. The tools become expensive shelfware.

---

What the data says about the stakes

The gap between successful and stalled transformations is widening. Deloitte's research shows that top-performing procurement teams — which they term "Digital Masters" — allocate up to 24% of their budgets to procurement technology and deploy AI and machine learning at three times the rate of peers, with some having fully deployed AI solutions at 16 times the rate of average organizations. Meanwhile, the rest are still running pilots and proof-of-concepts that never reach scale.

McKinsey's Global Procurement Excellence benchmark shows that companies with advanced, digitally enabled operating models enjoy five percentage points higher EBITDA margins than peers. The gap between those who navigate the year-two transition successfully and those who do not is not theoretical — it shows up on the P&L.

---

How to prevent the year-two stall: four actions for CPOs

Preventing the stall requires treating year two as the critical phase from day one. That means designing the transformation program around adoption, not deployment.

• Separate adoption from deployment in the program plan. Most transformation budgets front-load spending on technology and vendor implementation. Instead, allocate at least 30% of the total program budget to adoption activities in year two: role redesign, process documentation, coaching, peer learning, and sustained communication. Make adoption a distinct workstream with its own milestones, metrics, and governance.
• Build capability before scaling. Train teams on the new process and tools before you expect them to use it at scale. Use just-in-time learning embedded in the tool, not one-time classroom sessions. Set a certification milestone before broad rollout — a measurable signal that the team is ready, not just scheduled.
• Create governance that survives sponsor turnover. Institutionalize the program through a transformation steering committee with rotating membership, documented decision rights, and a charter that can survive a CPO departure. The program should not depend on a single executive's enthusiasm.
• Measure adoption, not just deployment. Replace go-live metrics with adoption metrics: percentage of transactions flowing through the new process, time-to-competence for new users, savings validated by finance (not just identified by procurement), and user-reported satisfaction with the new workflow. If these metrics are not improving in month 13, the stall has already begun.

---

What this means for buyers

The year-two stall is the single largest destroyer of procurement transformation value. It is also entirely predictable and entirely preventable. The organizations that succeed treat year two not as a maintenance phase but as the main event.

• Audit your current or planned transformation program. What percentage of the budget goes to year-two adoption vs. year-one deployment? If it is under 30%, restructure the allocation before the program launches. Measurable outcome: sustained savings curve beyond month 12.
• Replace go-live metrics with adoption metrics in your program dashboard. Track transactions through the new workflow, not trained user counts. Measurable outcome: early warning of stall risk by month 13.
• Invest in capability building six months before the technology goes live. Pre-training creates readiness; post-training creates excuses. Measurable outcome: 80%+ user competence at go-live, not 60%.
• Institutionalize sponsor governance. Document decision rights, create a steering committee charter, and rotate membership so the program survives personnel changes. Measurable outcome: program continuity through CPO turnover.

---

Frequently asked questions