A founding business owner like you says something like this:

• “I just know how to ...”
• “I just know what to watch for.”
• “There are just some things I know to follow up on.”

These sentences sound harmless. They are not. They mean the business is still depending on invisible judgment that lives in your head. As long as that stays hidden, the role you’re in cannot truly be transferred to someone else, the process cannot truly be scaled, and you cannot fully get out of the center of your business.

This tool helps you pull that hidden know-how out of your head and turn it into SOPs, training assets, and decision logic other people can actually use.

Use this tool when:

1. You keep stepping back in because other people miss things you notice automatically.
2. A handoff keeps breaking down, even after the “right person” has been assigned.
3. A role has been transferred on paper, but not in practice.
4. People are still coming back to you for judgment, follow up, or exception handling.

How to transfer knowledge

When you say something like, “I just know how to ...” or “I just know what to watch for,” that is a knowledge transfer problem. Those things are not magic. They can be written down, trained, and handed off.

What needs to happen

• Identify the things you “just know” to watch, check, or follow up on.
• Get that knowledge out of your head and into a format other people can use.
• Turn it into SOPs and training material so your team can run the process without needing you at the center.

How to do it

1. Schedule protected time for the work, because what gets scheduled gets done.
2. Have someone interview you; don’t make it hard on yourself by sitting down in front of a blank screen and trying to type it out.
3. The interviewer can use questions like these:
   1. What are the things you just inherently know to follow up on?
   2. Why do you know that?
   3. How do you know that?
   4. When you see that something needs follow up, what do you do next?
   5. What different paths can the situation take?
   6. Why do you choose one response instead of another?
   7. Why do you call this person and not that person?
4. Record the interview on video to capture your explanation in full.
5. Don’t worry for a second about how you sound. AI doesn’t care and AI can work with any input.
6. Transcribe the recording with AI and ask AI to create a first draft SOP from the transcript.
7. Manually edit that draft into a clean process document and training system.
8. When software is involved, record the screen, button clicks, and mouse movement so the result can also become a training video, or at least give a running head start to someone recording their own software training video.

The main point

Don’t wait to “just sit down and write it.” Instead, create a structured interview, record it, transcribe it, draft the SOP from it, and then refine it. That turns hidden know-how into a repeatable training asset.

What This Looks Like in Real Life

Three examples illustrate what this looks like in real life.

Founder knows the trouble before anyone else does

In one coaching conversation, a founder was talking about a department that was underperforming. On the surface, the problem looked like a people problem or a process problem. But when we dug in, he said there were things he just inherently knew to follow up on.

He knew which jobs were drifting off schedule. He knew when the handoff from sales to production was incomplete. He knew what information should already be in the system, which questions to ask next, and who to call when something was slipping.

None of that lived in a usable training system. It lived in him.

So the assignment was not “work harder” or “get more involved.” The assignment was to extract that judgment and turn it into SOPs, checklists, follow up logic, and training material so the department leader could run it without needing the founder’s instincts every time.

Owner is still the hub of outside relationships

In another client situation, the issue was not production knowledge. It was relationship knowledge.

The owner had spent years building trust with key referral sources, clients, and outside partners. Other people technically had the role, but when something got sensitive, confusing, or high stakes, everyone still wanted the owner.

Why? Because the critical knowledge had never been transferred. The owner knew how to read the moment, how to reassure the other party, what tone to use, when to push, when to pause, and when to escalate.

That kind of judgment feels intangible until you interview it out. Once you do, it can become scripts, response principles, escalation rules, and examples that help the next person handle the relationship with confidence.

A founder’s “special sauce” with vendors and exceptions

In another coaching pattern I have seen across founder-led businesses, the founder is the one who knows how to handle unusual vendor situations, pricing exceptions, or operational curveballs.

The team sees the founder solve these issues quickly and assumes the answer is experience. That is true, but incomplete. Usually there is a repeatable thought process under the surface. The founder notices two or three signals, asks a few diagnostic questions, rules out one or two bad options, then chooses a response path.

Once that judgment gets recorded and questioned out loud, it stops being mysterious. It becomes teachable.

The Trap to Avoid

The trap is trying to force yourself to “just document it.”

That usually means staring at a blank screen, trying to force tacit knowledge into neat sentences, and giving up because the task feels heavy, fuzzy, and annoying.

Blank screens suck.

A recorded interview is better because it mirrors how the knowledge actually lives in your head. It comes out in stories, examples, branching paths, and explanations. That is the raw material you want.

Make It Fun and Make It Count

One of the best parts of this method is that it can do more than one job at once.

If you ask your child, your grandchild, your niece, your nephew, or some other sharp young person in your orbit, you are not just extracting knowledge. You are also doing at least three other valuable things at the same time.

1. You are building legacy

You are giving a younger person a chance to see how a business actually works.

Not the polished version. The real version. How experienced adults notice risk, make judgment calls, solve problems, and think through branching paths. That is a legacy building moment.

2. You are creating a meaningful way to help your business

A lot of owners would love to involve a child or relative in the business somehow, but the work they think of is either trivial or vague. This is neither.

“Interview me. Ask why. Record it. Help me capture what only I know.”

This is real help. This is meaningful work.

3. You are learning the value of your own time

You could pay your child, niece, or nephew $100 cash to do this with you.

To them, that is a lot of money.

To you, it feels like a lot of money too, right up until you compare it to the value created.

If that interview helps you stop doing one recurring task forever, or even reduces your involvement by 80 percent, that $100 is not an expense. It is a rounding error.

It is microscopic compared with what you save by never doing that thing yourself again.

And it is even smaller compared with what you can earn when you use that freed up time for higher value work, landing a whale customer, building a strategic partnership, launching a new service, or developing a new product.

The Simple Math

Here is the lesson.

If you pay a young relative $100 to help you extract a process you currently do yourself, you are not “spending money on documentation.”

You are buying back founder time.

And founder time, when aimed at the right target, is worth far more than $100.