Your Transformation Does not Start Where Theirs Did
Every transformation program rests on the same five things: technology (the systems and the apps that talk to each other), process (the workflows and the automation), people (change, leadership, ownership), architecture (how the business and the systems fit together), and data (the master records and the transactions flowing through all of it).
Ask most consulting firms how to sequence a transformation and you’ll get the same answer, dressed in different slide templates. Map the As-Is process. Design the To-Be. Then architecture. Then technology. Then people. Then data. Five steps, five weeks of workshops, one deck.
It’s not that the sequence is wrong. It’s that it’s generic — and generic is the opposite of diagnosis.
I’ve sat on both sides of enough of these programs to know the sequence that worked for the last client is not automatically the sequence that will work for you. Sometimes the right place to start is the exact opposite end. Start with data, and the rest follows — because until you know what your master records actually say, every process map and architecture diagram is sitting on a foundation nobody has checked.
Take two organisations trying to modernise their back office. One has years of clean, well-governed data and a leadership team that already agrees on what “good” looks like. For that organisation, going straight to technology and architecture might be exactly right — the data can be trusted to carry the new systems.
The other organisation has the same ambition and a completely different starting condition: data scattered across disconnected systems, duplicated records, no single source of truth for a customer or an asset. For that organisation, starting anywhere except data means building beautiful new architecture on top of a swamp. The technology will look modern. The reports will still be wrong.
A third organisation might have neither problem — clean data, sound architecture — and still fail, because the actual blocker is people. Change fatigue, no clear ownership, a leadership team that says yes in the steering committee and no in the corridor. Roll new technology into that environment and you get expensive systems nobody actually uses.
Same five ingredients. Three completely different starting points. That’s not a contradiction. That’s the point.
Sequencing a transformation is not a checklist — it’s a diagnosis. It has to account for your current situation, your goals, your environment, the decisions you’ve already made and what they produced, and your priorities. And there’s more underneath all of that. Genericising the sequence doesn’t make the complexity disappear. It just hides it until it resurfaces as a failed program eighteen months in.
So be careful with anyone — a framework, a methodology, or a firm — who arrives with the steps already decided before they’ve understood your situation. You can find a sequence easily. Five-step frameworks are everywhere, and they’re easy to sell precisely because they don’t require anyone to actually look at what’s in front of them.
The question worth sitting with: when someone hands you a roadmap with the boxes already arranged, are you looking at a diagnosis of your organisation — or a product built to be sold to the next one too?
