Operating since 2015, (Next Level Group) NLBPi is a change management consultancy; focused on maturity uplift, performance improvement, scaling and growth. Helping client organisations and businesses to improve maturity across disciplines, ways of working, maturity uplift, governance, risk, scalability, organisational maturity, leadership capability, and AI-enabled business performance via change management consulting, coaching, systems implementation, and practical change and transformation programs.
Why Most Transformations Stall or Fail (And How to Actually Fix Them)
Spoiler: It's rarely just the Vision, strategy, the technology, or the people. It's the bridge you haven't built between these inter-related factors – and the practical governance mechanisms that lets those bridges actually work.
I've spent over 30 years in the trenches of transformation work. Software deployments, organisational change, operations uplift across disciplines; in mining operations, enterprise-wide change at utilities, digital and cultural overhauls in government, complete GRC operating model redesigns. I've watched multi-million dollar programs thrive – and, more frequently, I've joined projects that have stalled multiple times before getting traction, and delivering what they hoped for and promised. Real change, as needed by the organisation (Why the change was initiated).
Here's what I've learned:
Large transformations stall and fail not because the Vision or strategy is weak, the technology is wrong, or the people are unwilling. They fail because organizations can't integrate executive vision, technological capability, operational reality, and workforce adoption. Those four worlds operate in separate silos, with different languages, different incentives, and different timelines. And critically, nobody is explicitly accountable for connecting them – with the authority to actually make trade-offs.
Let me walk you through why that happens, and how to actually fix it.
The Four Worlds That (Sometimes) Don't Talk To Each Other
1. The Executive Vision – Business outcomes, ROI, market positioning. Lives in boardrooms and strategy decks. Speaks the language of shareholder value.
2. The Technological Capability – Systems, APIs, deployment timelines. Lives in IT and vendor teams. Speaks the language of architecture and go-live dates.
3. The Operational Reality – Real-world constraints: regulatory handcuffs, exception handling, messy data, equipment that fails at 2am. Lives on the front line. Speaks the language of what actually happens.
4. The Workforce Adoption – "How does this help me do my job?" Habits, trust, personal effort. Lives in daily work practices. Speaks the language of why should I care?
These groups sometimes don't communicate in each other's languages. The executive team cares about quarterly results. Technology cares about go-live dates. Operations cares about keeping the lights on. The workforce cares about getting through the day. Sometimes, nobody owns the benefit that emerges when all four align, at a meta/program level.
And that's where transformations deliver less than hoped; ( i.e. When these linkages break down.).
What Failure Actually Looks Like
I've joined projects where these scenarios have play out before my arrival:
Scenario 1: Technology arrives before reality catches up
The system goes live on schedule. Technically and functionally quite flawless. But the new workflow was designed by people who've never done the job. Operators find workarounds within weeks. Adoption metrics look okay. However most of the promised benefits are slow, or never materialize.
Cost: Studies (McKinsey, Gartner) suggest 40–60% of large-scale technology investment is never realized.
Scenario 2: Vision disconnected from operations
The leadership team approves a new process that removes three approval steps. On paper, elegant. In practice, those steps exist because of a key vetting step. When the new process launches without them, you either create compliance risk or quietly add them back – killing the efficiency gain in the circular problem we shouldn't have solved.
Cost: Regulatory exposure, project rework, and loss of leadership credibility.
Scenario 3: Change managed, but the new way doesn't work
The change team runs beautiful workshops. Communication is excellent. Adoption scores are high. Yet the new process breaks when the change doesn't stick.
Cost: Organisational cynicism about transformation. The most expensive legacy you can leave.
Why This Keeps Happening
1. Different languages, no translator with teeth
Strategy speaks ROI. Technology speaks APIs. Operations speaks exceptions. Workforce speaks effort. Translation isn't enough – you need someone who can stop work when translation reveals a fatal conflict. Nobody has that authority.
2. Incentives actively work against integration
The technology lead is bonused on go-live date. Operations is bonused on uptime (which conflicts with planned downtime for change). Middle managers are bonused on old metrics – so they quietly block new processes. Executives are bonused on quarterly results, not 18-month benefits. Nobody is bonused on "the transformation delivers lasting benefits." A bridge-builder without changed incentives will fail. I've seen the best integration leader in the world defeated by a bonus scheme that rewards go-live date over benefits realization.
3. Timeline mismatch – and denial about it
Technology: calendar-driven. Executives: immediate benefit. Operations: needs 3–6 months to stabilize. Workforce: adoption is a curve, not an event. When no one acknowledges this, everyone measures success against their own clock – and everyone ends up disappointed.
4. Middle managers are the invisible linchpin
Front-line workers often want change that makes their jobs easier. Senior leaders want strategic results. Middle managers decide whether to enforce new processes – and they're caught between competing pressures. Their own incentives frequently push them to quietly maintain the status quo, protecting their teams from disruption while appearing to comply. They become invisible blockers by default, not by design.
5. External factors don't care about your go-live
Market shifts, new regulations, supplier failures, economic downturns – these can sink a transformation even with perfect internal alignment. A good bridge includes early-warning systems and contingency playbooks, not just internal translation.
How To Actually Fix It
I've done this successfully multiple times. It requires five distinct actions – and they're not "communicate more" or "hire a change manager."
1. Assign a Value Integration Lead – with real authority
Not a coordinator. Not a facilitator. Someone who reports directly to the transformation steering committee, with the power to:
- Pause a workstream if an operational or adoption conflict is unresolved
- Veto design decisions that haven't been validated with frontline users
- Escalate incentive misalignments to the board ("Ops is bonused on uptime, but the new system requires planned downtime – we need to change the bonus scheme")
This role sits in a Transformation Management Office that is above IT, operations, and HR – not under any of them. And it has a budget for user research and small-scale pilots.
I've done this role. It's uncomfortable. You're constantly telling a CIO that their timeline is fantasy, or telling an executive that their favorite efficiency gain doesn't match operational reality. But it's necessary – because without that discomfort, the conflicts stay hidden until go-live.
2. Do Real Change Impact Analysis – and put conflicts on the table
Not a checklist. A structured process:
- Walk the end-to-end process with the people who do the work.
- Document every assumption the design makes about operational reality.
- Classify conflicts as solvable, needs executive trade-off, or showstopper.
- Bring the trade-offs to the steering committee before design is locked – not after go-live.
Example from a mining transformation: The new scheduling system assumed perfect GPS coverage underground. Reality said otherwise. That conflict went to the steering committee – they chose to invest in infrastructure rather than launch a broken system.
3. Design for Reality, Not Vision
The future-state process should account for exceptions, regulatory obligations, and the 20% of use cases that consume 80% of the effort. Then build a transition strategy that acknowledges the messy middle – not a big-bang go-live unless it's truly justified.
Key tool: A "realism review" at three design milestones – with operational staff in the room and a formal veto for the Value Integration Lead.
4. Align Incentives, Benefits Gained and Problems Solved: Before Go Live
Review every metric and bonus that touches the transformation:
- Does technology have a post-go-live benefits metric (e.g., "90% of workflows fully adopted at month 6")?
- Does operations have a "process adherence without workarounds" metric?
- Are middle managers rewarded for enforcing new ways, not just protecting old KPIs?
- Is executive compensation tied to benefits realization 12–18 months post-go-live?
If not, change the incentives/value proposition / benefits gained or definition of problems solved. A bridge without aligned gains is a footpath to nowhere.
5. Build a Governance Rhythm That Forces Integration
Integration doesn't happen by osmosis. It requires a structural cadence that surfaces conflicts before they calcify:
- Weekly: Integration working group (Value Integration Lead + domain representatives) – flags conflicts, assigns fixes.
- Monthly: Steering committee – makes trade-offs on unsolvable conflicts, reviews incentive alignment, tracks external risk radar.
- Quarterly: Benefits review – measures adoption and actual business outcome. If adoption is high but strategic benefits are low, the bridge is broken. Investigate. Fix it.
This rhythm forces the timeline mismatch into the open. Go-live becomes a milestone – not the finish line.
A Success Story: When the Bridge Worked
A global utility was replacing a 20-year-old outage management system. Early designs looked great to IT and executives. But the Value Integration Lead spent two weeks riding along with field crews and discovered something the design team had missed: the new mobile app required 4G connectivity – and 40% of the service territory had no coverage.
Instead of proceeding as planned, they bypassed standard project reporting and took that data straight to the steering committee. They made three conscious decisions:
- Added offline mode to the app – delaying go-live by 3 months.
- Changed the technology team's benefits gained to include post-go-live usability targets.
- Created a middle-manager incentive for surfacing process exceptions in the first 90 days.
The transformation launched 3 months late but delivered 95% of forecast strategic outcomes within 12 months. A study revealed that the original trajectory would have captured less than 40% of the outcomes intended in this branch of the change implementation.
The difference wasn't better strategy or better technology. It was the bridge to the definition of done and related benefits, properly resourced and governed based on clarity of the future state.
How to Know If You're at Risk – A Quick Diagnostic
Answer yes/no:
- No single person has the authority to pause work over an integration conflict.
- The technology team's bonuses are tied only to go-live date, not benefits realization.
- Middle managers' performance metrics don't change during the transformation.
- You haven't walked an end-to-end process with frontline staff in the last 30 days.
- "Go-live" is treated as success – no formal benefits review 6–12 months later.
- External risks aren't on the steering committee's agenda.
Three or more "yes" answers? You're leaving 40%+ of your investment on the table.
The Bottom Line
Strategy is necessary. Technology is necessary. Operations are necessary. Workforce adoption is necessary.
None of them is sufficient on their own.
Transformation succeeds when all four align – not by accident, but through deliberate, governed, and accountable integration.
That requires a Value Integration Lead with teeth. Aligned incentives. Middle managers as allies, not invisible blockers. Governance that surfaces conflicts before they become failures. And an honest acknowledgment that the world doesn't freeze for your go-live.
If you're about to start a large transformation, don't just assign a change manager or a technical lead. Build the bridge to clarity on future state and related benefits. Give it teeth. Fund it. Measure it by strategic outcomes delivered, not by go-live dates.
That single decision – in integration, not just planning – is the highest-leverage move you'll make. Everything else flows from it.
Don Cook has spent 30 years leading transformations in Local and State Government, GOCs, utilities, mining, and technology sectors. He works with organisations to design and govern strategies that actually deliver benefits realisation. You can find him at nlbpi.com.au