Why This $25 Billion Steel Company Succeeded in ERP Implementation When So Many Fail

Most headlines about ERP focus on failure. Multi-million-dollar projects that miss deadlines, blow through budgets, or get abandoned entirely. The success stories, by contrast, often go untold. But understanding what makes a transformation succeed is at least as important as dissecting what went wrong. This post examines one of the most successful ERP implementations we have ever worked on: a $25 billion multinational steel company that defied the industry’s high failure rate through disciplined strategy, strong ownership, and a willingness to ignore conventional wisdom. Their approach was not about cutting-edge technology or following trends. It was about prioritizing business value above everything else.

The ERP Failure Rate Is Real, But Not Inevitable

Industry research consistently shows that 70 to 80% of ERP implementations fail to meet their original expectations. In our work, we have analyzed countless case studies dissecting what not to do.

What we do not talk about often enough is what the organizations that succeed actually do differently. This North American steel company, with 25,000 employees and a long history of disrupting the global steel market, offers a clear blueprint.

Who This Company Is

While not a household name to the general public, this organization is widely recognized in business circles. It is even featured in Clayton Christensen’s The Innovator’s Dilemma for its radical approach to steel manufacturing. The company revolutionized its industry in the 1970s and 1980s by undercutting competitors with more efficient processes and lower prices.

That same disciplined, contrarian mindset is what powered their ERP success. They approached the transformation the same way they approached steel production: with focus, rigor, and a willingness to challenge conventional wisdom.

5 Things They Did Differently

Five distinct decisions separated this company’s approach from the typical ERP implementation.

1. Laser-Focused on Business Value, Not Technology Hype

This company did not care about being cutting-edge or cloud-first. Their leadership was, by their own admission, proudly skeptical of technology for technology’s sake. If a software feature did not add measurable value for customers or employees, they did not implement it.

They did not chase trends. They evaluated every decision through one simple lens: does this improve business outcomes? The result was a remarkably focused project that delivered what it set out to deliver, without the scope expansion and feature creep that derail most implementations.

2. Resisted the One-Size-Fits-All Trap

Many companies fall into the trap of consolidating everything into a single ERP platform regardless of operational nuances. This client chose a hybrid architecture instead, consolidating where consolidation made sense and retaining separate systems where it did not.

Their reasoning was simple: forcing full consolidation across every part of the business did not produce ROI. Some operations were genuinely different enough that fitting them under one platform would have cost more than it saved. By being honest about that, they avoided the customization spiral that brings down so many large implementations. When we advise clients on business process optimization, this kind of honest assessment about what to standardize and what to leave alone is one of the most valuable conversations we have.

3. Said No to Cloud When It Did Not Make Sense

During the multi-year implementation, their software vendor pushed hard to shift from the on-premise solution to the vendor’s new cloud version. The client’s response was straightforward: the cloud version lacked the depth and stability they needed for the complexity of their manufacturing operations. Moving would cost more and deliver less.

It was an unpopular decision and went against industry momentum. It was also the right call for their business. This level of independent thinking, holding the line on what genuinely served their operations rather than following vendor pressure, is a hallmark of successful ERP selection and implementation work.

4. Owned the Project, Did Not Let Vendors Call the Shots

Unlike many organizations that defer to system integrators or software vendors, this client took complete ownership of the project. The advisors (including us), the software vendor, and the system integrators were partners providing input. The client was the decision-maker.

Even when the timeline slipped, the client maintained control. They adjusted staffing levels, pushed back on overbilling, and kept the project lean and intentional. This kind of disciplined ownership is rare. It is also one of the strongest predictors of success we have ever observed in ERP work.

5. Lived Their Culture Without Calling It That

Their organizational culture was so consistent and aligned that it did not need to be discussed. It was simply baked into everything they did. The team was united, efficient, and relentlessly focused on results.

Ironically, they actively disliked terms like change management and culture, even though they practiced both better than most organizations we have worked with. Their organizational change management was not a separate workstream. It was the way the company already operated. That kind of cultural alignment is impossible to fake and difficult to build, but when it exists, it makes nearly every other part of a transformation easier.

Key Takeaways for Your ERP Implementation

The lessons from this success story apply to any organization preparing for a major transformation:

• Lead with business strategy, not technology
• Do not buy into buzzwords or vendor pressure
• Say no when something does not serve customers or employees
• Make decisions for your business, not for your consultants
• Own the project rather than outsourcing accountability

This project was one of the most successful we have ever worked on, not because it was flashy or fast, but because it was disciplined, thoughtful, and focused on long-term value. If more organizations approached ERP this way, we would see far fewer failures in the industry. For additional case studies and patterns from the most successful transformations we have observed, our Lessons from 1,000 Digital Transformations report goes deeper on what differentiates the winners from the rest.

Questions We Hear Most

What Was the Single Biggest Factor in This Company’s Success?

Ownership. Of all the factors that contributed to this client’s success, the most important was that they refused to outsource accountability for the project. Every major decision was theirs. Every tradeoff was evaluated against their own priorities. Vendors, consultants, and system integrators provided input and expertise, but the client made the calls. In our experience, this single behavior separates successful ERP projects from failed ones more reliably than any other factor.

Can a Cloud-First Strategy Ever Be the Right Answer?

Yes, often. Cloud ERP is the right choice for most organizations, particularly mid-market companies that benefit from rapid deployment, lower upfront costs, and reduced infrastructure management. The point of the steel company’s story is not that cloud is wrong. It is that the decision should be made based on operational fit, not vendor pressure or industry momentum. Organizations with highly complex, mature manufacturing operations sometimes have legitimate reasons to wait. Most organizations do not.

How Do You Replicate This Kind of Culture If You Do Not Have It?

You cannot replicate decades of cultural alignment overnight, but you can borrow the practices that make it effective. The steel company’s culture worked because it was action-oriented, decision-friendly, and results-focused. Organizations without that baseline can still adopt the same disciplines for a transformation: clear ownership, fast decision cycles, accountability tied to business outcomes, and a willingness to push back on vendors and consultants when their recommendations do not fit.

If you are planning a transformation and want guidance on building the discipline that produces this kind of outcome, contact us at eric.kimberling@thirdstage-consulting.com.