Brandee Fantini – Principal ERP implementations rarely get derailed by technology. More often, a set of predictable pitfalls quietly compound until the go-live date becomes a moment of intense strain and heightened scrutiny. At this point, leaders want to jump in to diagnose and fix the issues—but it’s too late.
The irony is that these mistakes aren’t dramatic failures. They’re subtle, reasonable assumptions that simply don’t hold up in the transformation process. Here are three common scenarios that leaders must navigate during ERP implementations—and tips for taking a proactive change leadership approach.
Leaders sometimes equate alignment with readiness—that because they agree on the system being implemented and the timeline in which it’ll happen, they feel ready to lead the implementation.
Without this clarity, leaders may unintentionally send mixed messages, which can cause confusion, resistance, or stalled momentum for their teams.
Proactive approach: Prioritize leadership readiness as the first project deliverable. Ensure leaders have a shared understanding of not only the benefits of implementing the ERP but also the impacts the implementation will have on the organization and its people, roles, and ways of working.
Executives typically grasp the scope of the transformation, but it’s more difficult to understand the pressure that it’ll place on the operational system and the organization’s bandwidth to metabolize the amount of change. Plants must continue to run smoothly and customers still expect consistency, but the employees who make those operations possible are now also tasked with learning new ways of working in support of the new system.
When ambitious timelines collide with exhausted teams, the implementation becomes something people survive rather than embrace.
Proactive approach: Calibrate implementation timelines to organizational capacity, not just the desired go-live date. Underestimating bandwidth is a common pitfall; adjusting for it is effective change leadership.
Resistance is almost always viewed as something to overcome. But during ERP implementations, resistance can be a diagnostic insight that tells you exactly where the process, training plan, decision flow, or communication is misaligned with the realities of how your organization operates.
Leaders who see resistance as data accelerate the process by uncovering the real blockers early.
Proactive approach: Treat resistance as an opportunity to uncover what’s not working and why. It’s rarely the loudest voices who reveal the truth; more often, it’s the uncomfortable themes that keep resurfacing.
When leaders attune themselves to the right signals—readiness, capacity, and the insights embedded in resistance—the implementation moves faster, adoption is stronger, and the organization becomes more capable, not just more automated.
ERP is a leadership transformation disguised as a systems transformation. Those who understand that distinction set their organizations up for success that sustains long after go live.
Explore the role sponsors play in successful ERP implementations in this article, or drop us a line in the form below to chat with a TiER1 team member about your leadership transformation journey.