Every ERP Records Yesterday. What Is Responsible for Tomorrow?

My daughter is learning her multiplication tables. Like every child, she spends hours repeating them until she knows them by heart.

One evening I asked myself a simple question: does memorizing the answer mean she understands multiplication?

Of course not. It just means she remembers.

Understanding comes later, when she starts using those same numbers to solve problems she’s never seen before.

That got me thinking: maybe organizations aren’t so different.

Over the last thirty years we’ve built remarkable systems to help enterprises remember. Every function has its own way of preserving what already happened. Finance records every transaction. Supply Chain captures every movement. Sales stores every customer interaction. And yet inventory management is still a headache, forecasting remains notoriously difficult, and the same operational problems keep coming back.

The problem isn’t that we don’t remember enough. It’s that remembering, by itself, doesn’t make us better at deciding what to do next.

We’ve become incredibly good at remembering. But I’m not sure we’ve spent nearly as much time on what helps an organization learn, and they’re not the same thing.

An ERP can tell you what happened, and it can tell you exceptionally well. But that’s very different from helping you decide what should happen next. That was never its job.

Which leaves me with a question: if every enterprise system is designed to preserve what already happened, what is actually responsible for helping an organization make better decisions tomorrow?

And if organizations really learned, shouldn’t some mistakes only happen once?

Yet they don’t.

Throughout my career I’ve seen the same data issues return year after year. The same reconciliation discussions. The same debates about ownership. The same projects trying to solve problems that had supposedly been solved before. Different people, different systems, different industries, sometimes even different companies, but surprisingly similar conversations.

At some point I stopped seeing this as a technology problem and started wondering whether organizations actually know how to learn. Because remembering a lesson isn’t the same as changing what happens next.

So what does it actually mean for an organization to learn?

The more I think about it, the less I believe it’s about accumulating more information. People don’t become better simply because they remember more. They become better because they learn to recognize patterns, understand context, adapt when circumstances change, and anticipate what might happen next.

Technology can preserve memory, reveal patterns and connect information at a scale no human ever could. But only people can decide what matters, what has changed, and what to do differently next time.

What if the next enterprise capability isn’t another system, but the ability to make tomorrow’s decisions better than today’s?