Enterprise environments are rarely static, yet traditional ERP transformations often treat massive technological shifts as fixed-destination journeys. Daniel Chilton, a leading voice at Embridge Consulting, is challenging this rigidity through a delivery model known as “Elastic Change.” This approach acknowledges that while systems and processes don’t burn out, the people operating them certainly do. By integrating emotional intelligence, modular governance, and a focus on human sustainability, Chilton aims to move organizations away from the “one-off project” mindset and toward a model of continuous operational evolution.
In this discussion, we explore the structural blind spots that cause large-scale programs to stall and how leadership can maintain momentum when the organizational landscape shifts mid-stream. We delve into the practicalities of treating change fatigue as a primary delivery risk and the necessity of using data for real-time steering rather than simple progress reporting. Ultimately, the conversation shifts toward a future where the successful integration of enterprise software is measured not by a go-live date, but by the long-term resilience and adaptability of the workforce.
Traditional ERP projects often stick to rigid milestones despite shifting fiscal priorities or regulatory updates. How do you design a delivery model that flexes without losing control, and what specific guardrails prevent this flexibility from turning into uncontrolled scope creep?
A delivery model must plan for change rather than simply hoping it won’t occur during the long lifecycle of an ERP rollout. We achieve this by building modular workstreams and scalable resourcing that allow a program to expand or redirect services without throwing away six months of previous work. To prevent this from becoming a free-for-all, we establish clear non-negotiables, defined decision rights, and escalation routes that act as the structural skeleton of the project. This ensures that while we might adjust the pacing or the specific sequencing of a release to accommodate a new fiscal reality, we remain anchored to the original intended outcomes. It is about creating a “services model” that moves within a set of guardrails, ensuring that every pivot is a calculated adjustment rather than a loss of discipline.
Leadership behaviors often dictate whether a team commits to a new system or simply complies with it. How does emotional intelligence change the way a sponsor handles resistance during design sessions, and what tangible steps can they take to rebuild momentum when energy levels drop?
Emotional intelligence, or EQ, is the differentiator between a leader who enforces a decision and one who inspires a commitment. When resistance surfaces in a design session—such as a stakeholder questioning why a functioning legacy system is being replaced—an EQ-led leader stays calm and curious, seeking to understand the root of the fear rather than shutting it down. Tangible momentum is rebuilt when sponsors name the pressure early and clearly communicate the trade-offs being made, which protects the “discretionary effort” of the team. By acknowledging that workshop energy is dropping or that tension is rising during User Acceptance Testing, leaders can diffuse stress before it spreads, ensuring that the human “engine” of the program doesn’t stall.
Change fatigue is frequently viewed as a human issue rather than a delivery risk. What specific signals indicate that an organization is reaching saturation, and how can leaders sequence releases to avoid stacking multiple high-impact changes on the same teams in a single quarter?
We have to stop looking at tired employees as a HR problem and start seeing them as a RAG status risk; if your workshop energy is plummeting, your project is effectively “red” regardless of what the task tracker says. A major signal of saturation is when teams begin to miss “micro-actions” or when safe escalation routes become silent because trust has eroded. To manage this, we actively assess capacity and simplify the change roadmap, specifically ensuring we do not stack multiple high-impact releases on the same department within a 90-day window. By protecting the people carrying the program and setting a realistic pace, we build confidence through credible training and visible leadership alignment rather than just pushing for a deadline.
Beyond basic login rates and feature usage, how can organizations verify that a new system has truly integrated into daily operations? What metrics or feedback loops help identify shadow spreadsheets and manual workarounds that persist long after the official go-live date?
True integration is found in the absence of “shadow systems,” so we look specifically for a measurable reduction in manual workarounds and those ubiquitous offline spreadsheets that teams use to bypass the ERP. We monitor data quality and processing times across core workflows to see if the system is actually streamlining the business or if people are just doing the same old work in a new interface. Beyond the hard data, we establish change champion networks and structured feedback loops that provide qualitative insight into how staff are responding emotionally to the tool. When employees are actively advocating for the new way of working and operating confidently without heavy intervention from the project team, we know the change has genuinely “stuck.”
In an adaptive delivery model, data visibility is often used for real-time steering rather than simple progress reporting. How does this shift affect decision-making speed, and how do you maintain strict governance while allowing workstreams to remain modular and scalable?
High-quality data visibility acts as a lubricant for the entire transformation process, significantly increasing decision speed because it reduces the time spent debating “what” is happening and allows more time for “how” to react. In an adaptive model, we use these insights to steer the ship continuously, adjusting our course based on real-time organizational capacity rather than waiting for a monthly steering committee meeting. We maintain governance by treating it as a foundational structure—not a rigid cage—where workstreams are designed to be modular so they can be scaled up or down without breaking the core program. This balance provides leaders with the confidence they need to allow for flexibility while ensuring that the rigors of delivery and accountability are never abandoned.
Treating an ERP rollout as a one-off project often leads to post-launch stagnation. Why is it more effective to view these initiatives as evolving operational capabilities, and how should leadership reframe the goal of “go-live” to ensure long-term performance and continuous improvement?
The traditional “go-live” mindset is dangerous because it implies that the work ends just as the value realization begins; in reality, optimization and adoption are where the return on investment is actually won or lost. Reframing the ERP as an evolving operational capability means the organization is prepared to grow the solution alongside its staff needs and shifting technical requirements. Leadership must signal that “go-live” is merely a milestone in a larger journey of sustainable performance, ensuring that support structures remain in place to iterate on the system post-launch. By designing for adaptability from day one, the organization avoids the typical post-project slump and ensures that the technology remains a competitive asset rather than a stagnant legacy burden.
What is your forecast for ERP transformation?
I believe transformation will shift from being viewed as “program delivery” to becoming a “continuous capability” that sits at the heart of the business. In the next 3 to 5 years, AI will drastically accelerate change cycles, but this will also expose and amplify any weaknesses in an organization’s data foundations or human interaction models. We will see frameworks become much more modular and outcome-led, where the primary differentiator for success isn’t the software itself, but the emotional intelligence of the leadership team. The organizations that thrive will be those that can evolve their systems at high speed without burning out their people, treating technological change as a permanent, sustainable rhythm of the modern enterprise.
