You have one. Every multi-unit operator does. The manager whose store just runs. Labor lands, shrink stays low, the team stays, the reviews are good, and when something goes sideways at another location, she’s the one you send. You’ve thought about cloning her. You’ve probably tried: put her in charge of training, had new managers shadow her for two weeks, asked her to write down how she does it. And the other stores still don’t run like hers.
That’s not a talent gap in the rest of your bench. It’s a transfer problem, and it has a specific cause.
Why "Just Write It Down" Produces a Folder Nobody Opens
Roughly 80% of the processes in a typical business are undocumented. That number gets quoted a lot. The part that matters more is what the documented 20% actually contains: the official process, not the real one. Documentation captures the workflow. Your best manager’s edge is the judgment she applies to the workflow, and those are different things.
Ask her to write down “how to run a store” and you get a bad manual, for the same reason a great chef asked to write down “how to cook” produces a bad cookbook. Expertise is stored in the situations where it gets used. She can’t narrate it cold. So the shared-drive folder gets built, the calendar invite goes out, the two-week shadow happens, and six months after she gets promoted or leaves, her successor has quietly rebuilt half of what she knew, badly, and is still learning the other half by breaking things.
Documentation captures the workflow diagram. Tribal knowledge is the judgment that gets applied to the workflow. Those are different substrates.
Verti
Median tenure in most operations sits around three and a half years. Knowledge isn’t walking out the door at retirement. It’s walking out continuously.
What Actually Gets the Judgment Out
The method that works is unglamorous: sit with her, one real case at a time, and ask why. Not “how do you schedule,” but “why did you pull Tuesday’s mid shift last week and not the close.” Not “how do you handle shrink,” but “why did you count the candy wall on a Wednesday.” Never let it float into the abstract.
A knowledge-capture team ran this with a senior insurance underwriter who could not describe her renewal process on a blank page. Case by case, asked why this file gets approved and that one doesn’t, she talked for an hour on every decision. Every reason came out. None of them were in her team’s SOPs.
That last step is where most operators skip ahead. Encoding one person’s habits into the system institutionalizes the quirks along with the judgment. The output you want is a working profile: the case types she sees, the reasoning behind each call, the exception library, the triggers that make her escalate, and where she looks first when a store feels off.
Documents Don't Run Stores. Routines Do.
Here’s the trap on the far side of the capture: producing a document and calling it done. A documentation project produces documents. What you need is something that runs, every store, every week, whether or not she’s in the building.
The delivery mechanism at store level is the routine, not the manual. A routine defines when the work happens, who does it, what sequence is followed, how completion is confirmed, and how exceptions escalate. That’s the form your best manager’s judgment needs to take to survive contact with a store she’s never seen.
One prerequisite worth being honest about: this works against whatever data she already uses to read a store. POS, labor, inventory, reviews. If you don’t have that layer, build it first. Buying software before the method exists is paying to digitize the chaos. The value split is roughly 70% method, 30% tool.
When to Do This
Most operators start the capture after a near-miss: she gives notice, or gets sick, or the store she left behind falls apart within a quarter. That’s the expensive version. The cheap version is doing it now, while she’s engaged, while the cases are fresh, and while the second and third best managers are around to validate what she says.
Three things worth un-learning:
- Promoting her preserves the knowledge. It moves the person. The judgment still lives in exactly one head, now further from the stores.
- Having her train everyone else transfers the system. Training moves explicit knowledge well and tacit knowledge poorly. Judgment has to be recorded in action, not lectured.
- Her method is the system. Until two or three other strong operators confirm it, it’s one person’s logic mixed with personal habit.