Large-scale ERP initiatives are often structured as tightly defined projects with fixed timelines, milestones, and delivery frameworks. Yet in practice, enterprise environments rarely remain static. Business priorities shift, leadership teams evolve, regulatory pressures emerge, and organisations are forced to adapt mid-programme. The challenge for many transformation leaders is not the technology itself, but the ability to sustain momentum while the organisation around the programme continues to change.
Embridge Consulting has been working closely with organisations navigating these realities across complex ERP and digital transformation initiatives. Drawing on these experiences, the firm has formalised an approach it calls Elastic Change, a delivery model designed to balance programme discipline with adaptability while recognising the human impact of continuous transformation.
In this conversation with ERP News, Daniel Chilton discusses why traditional change management models often struggle in modern ERP environments, how leadership behaviours and emotional intelligence influence programme outcomes, and why organisations must begin treating ERP not as a one-off project but as an evolving operational capability.
Q: What specific challenges led you to formalise Elastic Change?
A: We kept seeing the same pattern: ERP programmes were designed, with good intention, as fixed projects, but reality wasn’t fixed. Priorities shifted as the business progressed through its fiscal year, funding or capacity decisions moved, a regulatory update landed mid-design, or a new senior leader joined and asked for something different.
The plan stayed rigid while the organisation evolved, and it’s the teams who carried the strain. We have a saying that systems and processes don’t burn out, people do. Elastic Change formalises what consistently worked in practice: a set of delivery services that can flex, strong technology foundations that can scale, and leadership that recognises the human impact of continuous change.
Q: What structural or leadership blind spots sit behind these failures?
A: The biggest blind spots are treating transformation as a go-live event and underestimating the human and operational load. We see governance that tracks tasks but not change fatigue, human resistance and adoption risk. Your programme RAG status might be green, but your workshop energy is dropping. From a leadership perspective, sponsors often underestimate the load their people carry or push pace without building enough confidence within their organisations first. Technical delivery can be strong, but if trust, clarity and energy drops, momentum goes with it.
Q: How does Elastic Change differ from traditional change management in practical terms?
A: Traditional change management is still treated as a supporting stream rather than a core element. Elastic Change integrates adaptability and human sustainability into the delivery programme through a dedicated set of services, and directly in how we lead every workshop, design session and decision forum. It’s not “comms and training at the end.” In addition to that, it’s a services model that can flex within clear outcomes and guardrails, pacing change based on capacity, and using EQ-led leadership behaviours throughout design, build, testing, adoption and optimisation. It’s a continuous model, not a one-off method.
Q: How does EQ tangibly influence success in large-scale programmes?
A: EQ affects the moments that decide whether people commit or comply. Leaders with EQ name pressure early, listen before enforcing decisions, communicate trade-offs clearly, and adjust pace when fatigue shows up. That builds trust, reduces resistance and protects discretionary effort. When leaders don’t regulate themselves, stress spreads and programmes stall. In practical terms, EQ improves decision speed, lowers friction in workshops and testing, strengthens sponsor effectiveness, and drives sustained adoption after go-live. So for example, when someone asks “why are we changing our system, the current one works just fine” high EQ leaders stay calm and curious, understand the resistance and help their team move forward. Or when tension rises in UAT, strong EQ diffuses it instead of allowing emotions to escalate.
Q: How do you address stakeholder fatigue and change saturation?
A: First, we treat fatigue as a delivery risk, not a people problem. We actively assess capacity, simplify and sequence change, and reduce unnecessary “micro-actions” that create friction. Such as not stacking multiple releases on the same teams in the same quarter. Identifying signals early reduces the degree of intervention needed, this is why creating safe escalation routes and building trust is essential. We focus on confidence-building moments: credible training, visible leadership alignment, quick wins, and honest communication about what’s changing and why. We also protect the people carrying the programme by setting realistic pacing, clear decision rights, and stronger support around the roles most impacted.
Q: How does Elastic Change support scalability when priorities shift mid-project?
Elastic Change plans for change rather than hoping it won’t happen. We set clear outcomes and governance, but design delivery to flex within those guardrails. That means modular workstreams, scalable resourcing, and a model that allows organisations to expand or redirect services. When priorities shift, we don’t throw away six months of work and begin again. We adjust within guardrails and keep momentum.
Q: How do you measure whether change has truly “stuck” beyond go-live?
A: Adoption must be visible and actively supported, so data around login and feature usage are important. But we look to measure reductions in workarounds, shadow spreadsheets and manual fixes. We also monitor data quality and processing times across core workflows.
But metrics alone aren’t enough. We build change champion networks, create structured feedback loops to adjust how people are responding, and use adoption dashboards to maintain visibility. Continuous improvement support ensures the solution evolves with staff needs, not just technical requirements.
When people are engaging, giving feedback, advocating for the new way of working and operating confidently without heavy programme intervention, that’s when change has truly stuck.
Q: What role do data visibility and governance play in an adaptive model?
A: They’re foundational. Without trusted data and clear governance, organisations can’t adapt because they can’t see what’s happening. Good data visibility reduces debate, increases decision speed and improves accountability. That’s not just operationally helpful, it builds confidence and protects energy across teams. In an adaptive model, data allows you to steer continuously, not just report progress.
But adaptability doesn’t mean a lack of control. Elastic Change is not a rejection of programme discipline or delivery rigour. It isn’t uncontrolled scope creep, and it doesn’t abandon plans, milestones or accountability. Instead, scope, outcomes and guardrails are clearly set. That means clear decision rights, escalation routes and defined non-negotiables. Delivery is then designed to flex within those controls as insight grows and priorities shift.
That balance is critical. Governance provides the structure leaders need for confidence, while adaptability ensures change can evolve without breaking people, programmes or momentum.
Q: How must frameworks evolve over the next 3–5 years?
A: Transformation needs to move from “programme delivery” to “continuous capability.” AI will accelerate change cycles, but it also raises the cost of low levels of human interaction and weak data foundations. Frameworks will need to be more modular, outcome-led and resilient, with stronger integration and governance. Most importantly, leadership capability, particularly emotional intelligence, will become a differentiator of success. The winners will be organisations that can evolve fast without burning out their people, because AI will amplify both good and bad operating models.
Q: For leaders planning ERP initiatives in 2026, what one mindset shift would you recommend?
A: Stop thinking of ERP as a project you complete and start treating it as part of an operating model you evolve. Optimisation, adoption and continuous improvement are where value is won or lost. Design for adaptability and scale from day one, and lead with emotional intelligence so people can sustain the change. The goal isn’t just go-live. It’s long-term momentum, scale and sustainable performance.
ERP News Editorial Team
The ERPNews Editorial Team covers global developments in ERP (Enterprise Resource Planning), enterprise software, cloud platforms, AI, automation, and digital transformation, providing independent news and editorial analysis for senior business and technology leaders. Our reporting focuses on market signals, strategic shifts, and enterprise impact across the ERP and enterprise technology ecosystem.
For editorial inquiries, please contact:
📩 [email protected]
