Скачать или смотреть Postponing ERP testing always feels practical!

Postponing ERP testing always feels practical.

Until it becomes expensive.

In this week’s short from The ERP Perspective with David Zimmerman from Opkey, one uncomfortable truth comes through:
The cost of delaying ERP testing is rarely visible upfront… but it shows up fast after go-live.

Too often, postponement is driven by:
• Budget pressure
• Limited resourcing
• A lack of awareness of best practice
• Over-reliance on the system integrator to “cover it”

And yes, during implementation, SIs have to test.

They’re protecting delivery, contracts, and handover.

But here’s the problem… That same level of rigour often disappears the moment the system goes live.

Because once you’re live, you’re no longer “implementing an ERP.”

You’re running a business.
• Supporting internal teams
• Keeping critical processes running
• Managing change
• Keeping the lights on

And when testing hasn’t been embedded properly, quality becomes reactive, not intentional.

That’s why postponing testing isn’t a cost-saving move.

It’s a risk deferral strategy.

And in a live ERP environment, deferred risk compounds fast.

Which is exactly why automation-first, continuous testing isn’t about the system alone.

It’s about protecting the business that now depends on it.

🎧 The full episode is out Friday on The ERP Perspective, where David explains why testing discipline often drops after go-live, how budget and resourcing pressures drive risky decisions, and why organisations must carry implementation-level rigour into live operations.

👇 Watch the clip.

💬 Want to be part of the conversation? Drop us a message, or let us know in the comments if you’d like to get involved with The ERP Perspective.

Where does testing typically break down after ERP go-live in your organisation, budget, ownership, or awareness?

#erptransformation #erpleadership #digitaltransformation