Technology amplifies operating discipline — it does not create it. Before selecting an ERP or planning platform, get the process architecture right, or budget to automate your problems.
There is a familiar arc to failed supply chain technology programs. It begins with a software selection, proceeds through an implementation that runs long, and ends with a system that faithfully automates the processes everyone agreed were broken.
The root cause is almost never the software. It is sequencing. Technology amplifies whatever operating discipline exists — it does not create discipline where there is none. An ERP deployed onto ambiguous planning roles, dirty master data, and unowned processes will produce ambiguity, dirt, and orphaned workflows at higher speed.
The sequence that works is unglamorous: process architecture first, data model second, technology third. Define who plans what, at which horizon, with which decision rights. Fix the item master, the BOMs, the lead times. Then — and only then — evaluate platforms against the process you actually intend to run.
This ordering also changes the selection itself. When requirements come from a designed process rather than a features wishlist, the field narrows quickly, demos become decisive, and the implementation partner can be held to outcomes rather than configuration hours.
AI-driven forecasting, control towers, and autonomous planning are real and worth pursuing. But they compound on a foundation. Build the foundation deliberately, and the technology delivers. Skip it, and you will pay to automate your problems.