You’ve just inherited a stack you didn’t build. It’s grown out of acquisitions, a couple of platform changes and years of small workarounds that each made sense at the time. The pressure you’re feeling is to start fixing it: pick something visible, show some early progress, prove you’re on top of it.
The best place to start is simpler: before you change anything, ask for the architecture diagram.
Start with the map
I’m a visual person, so the first thing I want is to see the shape of everything: the systems, how they connect, and how data moves between them. A diagram tells you that in a way a pile of logins and a handover document never will. Where does product data actually live, what’s talking to the ERP, and how many systems does an order pass through before it’s fulfilled. You can’t plan a single change safely until you can see all of that in one place.
I ask for the diagram up front. Some clients have one ready (which is a good sign) but a lot don’t.
If there isn’t one, that’s the finding
That usually means no one person can see the whole picture, which is often how a stack gets tangled in the first place. Changes get made in one place without anyone clocking the knock-on effect three systems down. So the very first step is to build one. It doesn’t need to be polished: a rough sketch of the main systems and how they connect is enough to start seeing where the gaps are.
Building that map is the first real diagnostic. You find the integration nobody remembered was still running. You find two tools secretly doing the same job. You find the manual step someone does every week to paper over a gap that was never closed. None of that shows up in a feature list. You only see it once you trace the data from system to system
Why the map comes before the plan
Early on, the temptation is to move quickly and show progress, and fixing something visible is the obvious way to do that. The risk is acting before the full picture’s clear. Effort lands where it’s most visible rather than where it matters most, and a quick win can come undone when a bigger problem surfaces upstream.
The diagram eliminates any guesswork. With an accurate map in front of you, it’s far easier to see what any given change will affect, and to scope it realistically. Once you can see the flows, you can tell which change is low-risk and which one actually touches half the estate.
What a good first map gives you
Everything that follows depends on that map. Without that view, you’re making decisions on a stack you can’t fully see. A complete map shows you:
Where the data lives, and where the real single sources of truth are
How systems are integrated, and which of those connections are fragile
The workarounds and manual steps holding the gaps together
Which parts you can change in isolation, and which you can’t touch without a plan
If you’ve inherited something messy and you’re not sure where the real risks are hiding, start by drawing out how everything connects. If you need some guidance, we’re happy to build it with you.
Emma heads up delivery and operations here at Unified. She sits on the leadership team and has the responsibility to keep everything ticking along as clients expect.
