ERP Resilience: Lessons from the Lockdown

By May, the patterns were unmistakable. Some companies adjusted to lockdown almost smoothly. Others were still in chaos. The difference wasn't industry or company size. It was their ERP.

I should be more precise: it wasn't their ERP exactly, but their relationship with their ERP. Which is what I want to talk about because it reveals something important about what makes enterprise software actually resilient.

The Businesses That Thrived

The companies navigating May 2020 relatively well had specific things in common. They could see their cash flow in real time. They understood their supply chain without calling anyone. They could reforecast revenue quickly. They had inventory visibility across multiple locations. They could make decisions based on data, not hope.

None of these are capabilities their ERP suddenly developed because of the crisis. These companies had invested in their ERP before the crisis happened. They had the data infrastructure in place. They understood how to use it.

More importantly, they weren't discovering major gaps in their operational knowledge while their business was imploding. They already knew what was broken about their ERP and had worked around it or fixed it.

The Prediction Problem

The hardest operational problem in May was forecasting. Revenue had collapsed overnight for some industries and skyrocketed for others. Supply chains were broken. Labor was unpredictable. How do you plan?

The companies with good ERP infrastructure could model scenarios. "If demand stays at 30% of normal, how long before we run out of cash?" "If supply chain delays stretch from four weeks to eight weeks, what hits us first?" "If 20% of our staff can't work, can we still fulfill orders?"

You can ask these questions without an ERP. You can build a spreadsheet model. But the data to feed that model has to come from somewhere. Spreadsheets mean someone manually pulling numbers from disconnected systems and manually checking them for consistency.

A good ERP makes that instant. You query the database. You get the actual numbers. You model against reality instead of guesses.

The Companies That Broke

The companies that really struggled typically had one of three problems:

The scattered data problem: Everything was in different systems. Orders in one place, inventory in another, financial data in a third. Asking "how many days of inventory do we have?" meant calling three departments who each had to check their system, and then trying to reconcile numbers that didn't match. By the time you had an answer, conditions had changed again.

The trust problem: The data in the ERP was old, known to be inaccurate, or both. So decision-makers ignored it. They ran their actual business on spreadsheets and whiteboards and gut feel. When everything went remote, those informal systems collapsed. Nobody could gather around a whiteboard. Nobody could check "Karen in accounting" for the real numbers. Suddenly they needed to trust their ERP data, and they couldn't.

The rigidity problem: The ERP was set up for a very specific workflow. Manufacturing company runs on a six-week production cycle. Lockdown requires a two-week pivot. The ERP won't adjust easily. You can't quickly reconfigure the production planning module. So you end up running parallel systems—the old ERP for "the way it was" and informal processes for "the way it is now."

These companies weren't in trouble because of technology failure. They were in trouble because they'd never invested in operational visibility before they needed it desperately.

The Integration Question

By May, companies were also discovering which ones could integrate with new suppliers and processes quickly.

A company that needed to add remote work processes could adjust workflows quickly because their ERP had been designed for flexibility. Most couldn't. The ERP was built for a very specific business model, and when that model changed, the software became a constraint instead of a tool.

This is one of those things vendors promise but rarely deliver. They claim their ERP "adapts to your business." In reality, most ERPs adapt okay to variations of the exact workflow they were designed for. Ask them to support something genuinely different and you hit walls.

The companies with the best resilience had either invested in custom development to add flexibility or had chosen systems that were actually modular and flexible. Surprisingly, some of the older vendors' systems were more adaptable than the newer cloud systems. It depended entirely on architecture, not when it was built.

The Information Availability Problem

Here's something I didn't expect to be so critical: whether non-finance people could access the data they needed.

In a normal environment, if a sales manager needs to know the margin on a product, they ask their finance team. In May, everyone's working from home, communication is harder, and the manager needs the answer now because a customer is waiting.

The company where only finance people had ERP access had a massive bottleneck. The company where relevant people could query the system themselves kept moving.

This raises serious questions about access control and who should see what. Most traditional ERPs default to "very few people have access to financial data." It's secure. It's also slower when you actually need data.

The better-run companies had invested in controlled access. Sales managers could see relevant product margins but not payroll. Manufacturing could see supply chain and production data but not customer pricing. Controlled transparency instead of locked-down data.

What Resilience Actually Looks Like

Talking to companies across May, the ones that impressed me most weren't the biggest or the most sophisticated. They were the ones that had a pattern:

First, they understood their business through their ERP, not in spite of it. The data was accurate and current enough to trust. They used it regularly, so they knew how to find what they needed.

Second, they had flexibility baked in. They could adjust processes because the ERP wasn't so tightly coupled to their old workflow that change broke everything.

Third, they had invested in visibility. More people could see relevant data. Questions didn't have to flow through a bottleneck of highly trained specialists.

Fourth, they had recognized what the ERP couldn't do and built around it. Custom dashboards. Automated reporting. Integrations with communication tools.

The pandemic didn't create resilience in these companies. It revealed resilience that had already been built.

The Forgotten Truth

There's a business technology lesson buried here: infrastructure investments don't matter until they matter desperately. You can spend six months debating whether your ERP is good, whether you should migrate, whether it's really the bottleneck.

Then circumstances change abruptly, and suddenly you discover whether you built on sand or rock.

By May, most companies knew which one they'd chosen. The surprising part was that it didn't correlate with what they'd paid or what vendor they'd selected. It correlated with whether they'd actually thought about resilience before they needed it.