The people who left weren't just headcount. They were the ones who remembered why certain calls had been made. Who knew which clients were quietly fragile. Who could read the room in ways that don't appear in any system.

You didn't know that at the time. Or you did, but underestimated how many good people would gladly take the package and leave.

Now you're three months in. The new structure looks cleaner. But the informal operating system — the one that actually ran things — went with them.

Something is missing and no one can name it precisely. Meetings take longer. Small things fall through. The organisation is technically functional but something is off.

That's where this work starts.

We typically begin by mapping what actually left — not the headcount, but the informal operating system that went with it. Who held which relationships. Where the institutional memory lived. What the organisation is now missing that nobody can name precisely. Consulting and systems mapping make the invisible loss visible. From there, the work rebuilds what can be rebuilt and designs around what can't.

The organisation stops running on half a system. What replaces the gap is explicit, documented, held by people who own it — and who know they're valued enough to stay.