When we ask operations leaders 'what's your supply chain digitization plan?', the answer usually starts with the name of a piece of software or a platform — 'we're upgrading our ERP' or 'we're about to buy an analytics platform.' That's the wrong starting point. Successful digitization almost never begins with picking technology.
The first question that needs answering before any technology decision is: 'which daily or weekly decision is currently the slowest or least accurate?' It might be production scheduling, inventory allocation across warehouses, or supplier selection during a supply shortage. Whatever technology gets chosen needs to directly improve that specific decision — not a vague, general goal like 'more agility.'
The second question is: 'what data is this decision currently made with, and where does it come from?' Answering this usually reveals an uncomfortable truth: the data needed for this decision is scattered across several disconnected spreadsheets, a few uncoordinated legacy systems, or even just in one particular person's memory. Before buying any new technology, this data fragmentation needs to be mapped and consolidated as much as possible — otherwise the new system just adds another layer on top of the same disorder.
The third question is perhaps the most uncomfortable one: 'who will actually use this system's output, and are they ready today to change how they work?' Many digitization projects succeed technically but fail on adoption, because the end user was never genuinely involved in designing the process and sees the new system as something imposed from above.
Once these three questions are answered, choosing the technology becomes much simpler — and in many cases, it turns out the actual solution needed isn't an expensive platform at all, but a simpler intermediate tool (a well-structured spreadsheet system, or a lightweight dashboard) that can be implemented in a few weeks and immediately improve that specific decision.
This doesn't mean bigger investments (a new advanced planning system, a new ERP) are never necessary — sometimes they genuinely are. But even in those cases, the experience of solving a smaller, well-defined problem with a simpler tool builds a real proof of concept, which both earns organizational trust and clarifies the actual requirements for the bigger system.
A common mistake is treating the interim tool (a well-structured spreadsheet system, say) as a temporary fix that never actually gets replaced — or, in the opposite direction, continuously bolting unnecessary features onto that same simple tool until it becomes a maintenance problem in its own right. Both patterns signal that the original purpose of the interim tool has been forgotten.
A short checklist before any digitization decision: has the specific decision that's supposed to improve been named? Has the data needed for that decision been mapped? Has the end user been involved in designing the new workflow? And is there a set date to review and decide whether to extend or replace the interim tool? If the answer to any of these is unclear, it's still too early to move on to picking technology.
Supply chain digitization, in the end, isn't a technology project — it's a better-decision-making project, for which technology is just the tool. Organizations that respect this order — decision first, then data, then technology — get more measurable, more durable results.
Related Articles