Draw the Experience Before You Draw the System
Most executives starting an ERP journey begin with a list. Modules to buy. Vendors to shortlist. A budget to defend. They start in the middle of the story and wonder later why the ending never arrives.I’ve sat across the table from enough of these journeys to notice the pattern. The organisations that end up with a system that actually works are not the ones who picked the best software. They’re the ones who could visualise — clearly, specifically — the end state of the experience they wanted to deliver, before a single contract was signed.That’s the leader’s actual job at the start of this journey. Not to pick software. To articulate the potential experience of the customer, starting from the point they’re attracted to you, all the way through to becoming a long-term, loyal customer. Most leaders skip this. They jump straight to requirements, which is like designing a building from the inside of a room before anyone has drawn the building.Look at the companies everyone points to as examples of organisations that work. ALDI. Apple. Dyson. IKEA. None of them started by asking what their systems should do. They started by deciding, with total clarity, what the customer experience needed to feel like. ALDI decided the experience was speed and value — no frills, no wasted motion, get in and out with what you need at a price that respects you. Apple decided the experience was simplicity — fewer choices, fewer steps, a product that feels inevitable rather than configured. Dyson decided the experience was visible engineering — you should be able to see why it works. IKEA decided the experience was participation — you build it, so you understand it and you value it.Here’s the part executives miss: none of those companies achieved that experience through one department doing its job well. They achieved it because every department, every supplier, every project team was aligned to the same end state. ALDI’s buying team, store design, supply chain, and checkout process are not separately excellent — they’re orchestrated toward one outcome. If procurement optimised for margin without regard to shelf simplicity, the experience would collapse. If IKEA’s warehouse team optimised for efficiency without regard to the customer’s ability to find and carry their own flat-pack, the whole model falls apart.This is the concept your ERP journey actually depends on: alignment. Not alignment as a value on a poster. Alignment as the discipline of getting every department to share the same understanding of how their part of the business contributes to one end-to-end experience. Without that shared picture, each department will optimise for its own definition of “better” — finance for control, operations for throughput, customer service for resolution speed — and the new system will faithfully digitise five different ideas of what good looks like, all running at once, all slightly working against each other.This is where most ERP requirements documents quietly fail. They’re written department by department, each describing their current process, none of them describing the customer’s journey end to end. You end up with a system that satisfies every department’s checklist and serves no one’s actual experience, because no one was the customer in the room.The order has to run the other way. Visualise the end-to-end experience first — what does it feel like to be the resident, the ratepayer, the staff member, the supplier, on the other side of this system. Then work backwards: what does each department need to do, and how does it need to align with every other department, for that experience to become real. Only then does it make sense to ask which software does that.If you’re about to start this journey, draw the experience before you draw the org chart, and draw the org chart before you draw the system architecture. The companies that get this right — ALDI, Apple, Dyson, IKEA — didn’t get there by being good at procurement. They got there by knowing exactly what reality they were trying to manifest, and refusing to let any department drift from it.
