A lone figure standing at the edge of a vast, complex maze

Taligens Insight

Seven Pitfalls of System Implementations

Most fail not because of the technology — but because of how the work is framed, governed, coordinated, and adopted.

Change Management9 min read

System implementations are among the most complex, and most consequential, investments your organization will make. Missed go-lives ripple into operational disruption, burned-out teams, and eroded stakeholder trust. And the numbers are sobering. According to Gartner, by 2027 more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals, and as many as 25% will fail catastrophically.[1] Across Bent Flyvbjerg's broader database of roughly 16,000 major projects, only 8.5% hit both cost and time targets.[2] Separately, his 2025 Project Management Journal article on IT cost risk finds that IT projects carry unusually extreme tail risk compared with 22 other project types: when they go more than 50% over budget, the average overrun reaches 453%.[3]

The patterns behind many of these failures are visible early, and many can be reduced or avoided with stronger planning, sponsorship, process design, change management, and user readiness. In many cases, the breakdown is not the technology alone, but the way the work is framed, governed, coordinated, and adopted. Below are seven pitfalls that consistently derail implementations, and what it takes to navigate them.

The Seven Pitfalls

What consistently derails system implementations

Lack of Planning

Implementations that skip rigorous upfront planning set themselves up to recover from problems rather than prevent them. Teams jump into execution without aligning stakeholders on scope, outcomes, or a realistic roadmap. Benchmarks against comparable projects are ignored. Effort, specialized skills, critical dependencies, and risks are underestimated.

The result: programs that begin confidently and stall expensively. As McKinsey's review of a major multinational ERP recovery showed, the root cause of years of delays was not the software. It was “insufficient planning and anticipation of issues” from day one.[4] Strong planning is not bureaucracy. It is the ground on which every commitment in the program stands.

Underestimating the Impact of Change

A new system does not just change workflows. It changes how people work, coordinate, and find meaning in their roles. The everyday assumptions employees hold about their job, their team, and what counts as good work all come under pressure. In lean organizations, the bandwidth to absorb that pressure is already stretched thin. When leaders reduce Change Management to a memo and a training session, they are not managing change. They are hoping for it.

Prosci's ongoing research is unambiguous. Organizations with excellent change management are seven times more likely to meet project objectives than those with poor change management, and nearly five times more likely to stay on or ahead of schedule.[5] Change Management is not a nice-to-have. It is the multiplier on everything else you spend.

Limited Sponsorship and Alignment at the Top

Even the most disciplined implementation team cannot succeed without visible, engaged leadership above them. Sponsors are not figureheads. They are the people who resource the program, break through resistance, and signal to the business that this change matters.

Without active sponsorship and a clear governance structure, implementations drift. Business value gets negotiated away. Accountability blurs. McKinsey's work recovering a stalled ERP transformation at METRO AG, which had burned through five years and its entire budget while completing only a single pilot, confirmed it. As the program lead Florian Waldmann put it, “make sure you have direct access to, and sponsorship of, the C-suite. Sponsorship is essential because there will be some hard times when you need to make changes to accommodate the plan.”[4] Without that access, the program lacks the authority needed to act when conditions shift.

Inadequate Process Design

Technology enables better processes, but only if the processes are better to begin with. Too often, implementations simply digitize existing inefficiencies, automating the way things have always been done rather than asking how they should be done.

Without cross-functional alignment and genuine co-design with end users, gaps and workarounds emerge. Frustration follows adoption. When process mapping is treated as documentation rather than a chance to observe how work actually flows and where it breaks down, the business inherits a new system shaped around old constraints. The opportunity to open new possibilities for action, for the business, its customers, and its people, is lost.

Ineffective Project Management

The most experienced project managers know their role is not to track status. It is to lead. Inexperienced PMs default to administration: managing timelines and filling out reports while alignment erodes beneath them. They avoid hard conversations, allow slippage to normalize, and miss the early signals that weeks are about to become months.

Wellingtone's State of Project Management report found that only 34% of organizations mostly or always complete projects on time, and only 34% mostly or always complete them on budget.[6] Effective project management demands accountability, proactive risk escalation, and a commitment to holding the line. As Waldmann observed in the McKinsey interview, “If we said we would finish a specific task on a given date, then we moved mountains to make it happen. If you do not do this, the timetable slips. Days turn into weeks, and weeks turn into a delayed go-live date.”[4]

Lack of Effective Communication

Most implementation communications tell people what is happening. Effective communications help people understand why it matters, both to the business and to them personally. There is a significant difference between the two.

Top-down broadcast messaging does not reduce resistance. It does not build ownership. It does not address the concerns and questions that determine whether employees engage with a change or quietly disengage from it. McKinsey research finds that organizations where the implementation timeline is communicated clearly are more than three times as likely to report success as those where it is not.[7] Communication is not about information transfer. It is about listening as much as speaking, and building the trust that genuine commitment requires.

Insufficient End User Training and Support

Training delivered as a series of software tutorials misses the point. Users do not need to know where to click. They need to know how their job changes, what their new responsibilities are, and how the new system fits into the work that matters to them.

When training is rushed, role-agnostic, or disconnected from business processes, users arrive at go-live underprepared. Productivity collapses. Workarounds multiply. The business pays for its new system twice: once in the investment, and again in the productivity losses and re-training costs that follow a weak launch. Prosci data shows that 41% of IT software implementations only partially meet their objectives, a number closely tied to insufficient investment in user readiness.[5]

Preparation Turns Knowledge Into Outcomes

Knowledge is power, but preparation is what turns that knowledge into outcomes. At Taligens, we partner with bold leaders to navigate these risks and create the conditions for system implementations to deliver real business value, with teams that are equipped, aligned, and ready for what comes next.

Ready to give your next implementation the conditions to succeed?

Set up a conversation with one of our partners.

Set up a conversation

Sources

[1] Gartner, “Latest Enterprise Resource Planning (ERP) Insights.”
[2] Flyvbjerg, B. & Gardner, D., How Big Things Get Done, 2023.
[3] Flyvbjerg, B., Budzier, A., Aaen, J., Keil, M., & Zottoli, M., “The Uniqueness of IT Cost Risk: A Cross-Group Comparison of 23 Project Types,” Project Management Journal, 2025.
[4] McKinsey & Company, “Getting an ERP Transformation Back on Track,” July 14, 2025.
[5] Prosci, “The Correlation Between Change Management and Project Success”; Prosci, Best Practices in Change Management, 12th Edition.
[6] Wellingtone, The State of Project Management Report, 2024.
[7] McKinsey & Company, “How the Implementation of Organizational Change Is Evolving,” 2018.