47 Minutes of You Talking to Yourself Is Not a Training System

47 Minutes of You Talking to Yourself Is Not a Training System

I hit stop on the recording and felt genuinely accomplished.

Forty-seven minutes. I’d walked through the whole thing — how to handle incoming leads, how to prioritize, what goes where, what happens next. My VA was going to watch this and just… know. I’d basically cloned myself. Problem solved.

Two weeks later, the task came back to my desk with questions.

I recorded a 23-minute follow-up to answer them.

That one came back too.

Somewhere around week three, the quiet math hit me. I had now spent more time recording myself explain this work than I’d spent doing the work in the first place. For three weeks running. And the work was still on my desk.

Not a crisis. Not a breakdown. Just a slow, flat “oh.”

You didn’t build a system. You narrated your own bottleneck and called it delegation.

—

The Video Captured What You Did. It Didn’t Capture Why.

Here’s what most people miss when they go full documentation mode:

The Loom showed every step. It did not show a single decision.

Every judgment call I made in that 47 minutes — the ones that happened in half a second, the ones that looked like nothing from the outside — none of that transferred. Every “it depends.” Every “I usually do this but sometimes I do that.” Every moment where the work actually required my brain to be there.

The person watching got footage of a maze. They still didn’t have the map.

Recording steps is not the same as documenting decision logic. And if you’re being honest, most of what makes your work hard to hand off isn’t the steps. It’s the judgment calls between the steps that you’ve never had to articulate because you’ve always been the one making them.

That Loom wasn’t a solution. It was evidence — pretty clear evidence, in hindsight — of how much undocumented thinking still lived entirely inside my head. I just dressed it up with a webcam and a progress bar.

—

Why the Work Keeps Coming Back

There are three reasons work boomerangs back to your desk, and a video addresses none of them.

The trigger is unclear. Your person doesn’t know when to start the task or what initiates it. So they wait. Or they guess. Or they ask.

The decision points aren’t mapped. When they hit a fork in the road — and there’s always a fork — they come back to you. Because the video showed them the highway but didn’t tell them what to do when the detour sign shows up.

There’s no quality bar. They don’t know what “done” actually looks like, so they default to the safest option: ask Jeff.

None of this is a failure of attention or effort on their part. It’s a structural failure. The information existed. The execution structure didn’t.

A process isn’t documented until someone other than you can run it without asking follow-up questions. That’s the line. If they’re still asking, you haven’t crossed it yet — no matter how long the video is.

—

What Has to Be True Before a Handoff Is Actually a Handoff

I had to learn this the wrong way before I could articulate it, but here’s what I know now.

Before any documentation — video, SOP, Notion page, voice memo, whatever — can become a real handoff, three things have to be in place:

The work has to be defined, not described. “Here’s how I do it” is not the same as “here’s the outcome, the inputs, the decision rules, and the finish line.” One is a tour. The other is a transfer.

The exceptions need a home. Every process has edge cases. If the answer to every edge case is “ask me,” then you’re still the system. The exceptions have to route somewhere that isn’t your inbox.

The handoff has to be testable. Hand it off and walk away. Come back later and look at the output. If the work got done right without you checking in, it’s a system. If it didn’t, you don’t have a gap in their training — you have a gap in your documentation.

The question I started asking, once I finally got tired of the boomerang: “What decision would they need to make here, and do they have what they need to make it without me?”

Every time the answer was no, that was a hole. Not in them. In what I’d built.

—

The Video Was Never the Problem

I eventually built something that actually held.

Not because I got better at recording Looms. Because I finally did the thinking that the documentation was always supposed to shortcut.

That’s the trap. The video feels like the hard work because it takes time and it’s visible and you can send a link. But the actual hard work is making your judgment transferable — pulling the decision rules out of your head and putting them somewhere that exists outside of you.

The video was never the problem. The problem was using the video to avoid that harder thing.

—

One Thing You Can Try This Week

Pick one task you’ve either recorded a walkthrough for or explained to someone more than twice. Write down — not in a video, just in a note — the three decisions you make inside that task that nobody else could make without asking you. That’s it. Don’t build an SOP. Just name the decisions. That list is where your real documentation work starts.

—

The Question Worth Sitting With

If you sent someone a Loom this week — walk it back. Not the video. The decision points inside it.

If you made three judgment calls to get through that task and none of them are written down anywhere, you didn’t document your process. You recorded your ceiling.

The work will keep coming back until the thinking comes with it.

If you want to start pulling that thinking out of your head and into something that actually runs without you — that’s exactly what we build at FlowStateOps. Book a Discovery Call and let’s look at what’s still stuck in your head that belongs in a system.

—