How My Daughter Getting in a Car Accident Is Like an ERP Implementation Gone Sideways

Aug 14

The other day, my daughter got into a car accident on the way to school, with all four of my kids in the car.

Thankfully, no one was seriously hurt (can’t say the same about the car).

And as it turns out, there are three reasons this incident is the metaphorical twin of watching an ERP implementation go sideways.

1. You Don’t Think It’s Going to Happen to You

Much like nobody thinks their kid is going to end up in a fender bender, nobody thinks their ERP project is going to go off the rails. It’s always “other people” who run into those problems—until it’s not.

2. When It Happens, You Get Hyper-Vigilant

Now that my daughter has had her little crash course in real life, I find myself wanting to micromanage every lane change. And guess what? That’s exactly what happens in an ERP mess. The CFO, the CEO—suddenly everyone’s in the weeds, micromanaging like they’re directing traffic at rush hour.

3. It Costs More Than You Planned

And, of course, the grand finale: it’s going to cost you. Just like that car repair bill and those delightful insurance premium hikes, an ERP going sideways means you’re spending more time and money than you ever signed up for.

So what is the silver lining?

In the end, my kids now have a story, and a lesson, they’ll never forget. Having gone through this, they’re more likely to be cautious drivers in the future.

Similarly, once you’ve experienced an ERP turned sideways, you’ve got insights worth sharing. It’s not only about fixing the problem this time—it’s about helping others steer clear of the same pitfalls.

And unlike a random car crash, teams know when they're getting started with an ERP implementation.

What can help teams be as prepared as possible?

Check out our articles on System Selection and Implementation to learn more!