The systems are the easy part.

Every shop has someone whose expertise is real and hard-won and almost entirely in their head. When they leave, retire, or just get pulled in another direction, that knowledge leaves with them.

We work directly with those people — not to extract what they know and hand it to a system, but to help them see the value in passing it on and actually want to do it. That usually takes more than one conversation. It takes someone who can ask the right questions, earn the trust, and help them work out what letting go actually means for them.

A change announced is not a change adopted. The people affected by it usually have something to say — about what's getting lost, about whether it'll actually work, about what they're worried won't be considered. When that stays unsaid, it surfaces later as resistance, workarounds, or quiet non-compliance.

We create the conditions for that conversation to happen before the rollout, not after. When people have real input into how something changes, they're more likely to make it work — and the end result is usually better for it.

Sometimes the real opportunity isn't getting people to accept a new tool — it's rethinking how the work actually happens. Not patching the old process with something faster on top of it, but asking whether it still makes sense for the people doing it and the customers depending on it.

We facilitate that redesign work with the people closest to the process: mapping how it really works now, where it breaks down, and what a better version could look like. The output is something the team helped build, which is most of why it gets used.