You haven’t taken a real vacation in years. Your phone doesn’t stay in the hotel safe. You check it anyway, at breakfast, because you already know something will be waiting.
Something always is. Rarely a fire, usually just a question only you can answer, because the answer was never written down anywhere except your head. So you answer it, from the pool, in twenty minutes that turn into an hour, and you tell yourself that’s just what running a business looks like.
That twenty-minute question from the pool is the cost of unfinished SOPs. You have some. You started most of them. Very few of them are done, because “done” means sitting down and writing out every decision you make without thinking about it, and that’s a different job than the one you signed up for.
The trap has two parts
The first part is out in the open. Your operating procedures are unfinished. Everyone who’s ever tried to build them knows the shape of it: you write the goal and the steps in an afternoon, easy, and stop right before the part that actually matters. Matt Gray calls that missing part the why, in “The Art of Delegation,” and he’s right that it’s the piece almost everyone skips. Steps without the why are a checklist. The why is what lets someone make the call you’d make once the checklist runs out. Skipping it feels like a shortcut; it’s actually the harder half of the work, so it gets set aside for “when things calm down.” Things never calm down. The document sits there, technically started, permanently unfinished.
The second part you don’t say out loud. Being the person everyone still has to ask feels like being needed. If the business runs through you, you matter to it in a way that’s hard to replace. There’s a version of you that likes that, even while the rest of you is exhausted by it and says, to anyone who’ll listen, that you want to build something that doesn’t depend on you being in the room.
Those two things reinforce each other. The SOPs stay unfinished because finishing them means admitting how much of your plan lives in your head and nowhere else. And some part of you isn’t in a hurry to finish them, because a business that runs without you is a business that no longer needs you standing in the middle of it.
That’s the actual trap: you already know how to delegate. Knowing how has never been enough to make you do it.
I built a business, watched it get bigger, and kept being the bottleneck for every decision that actually mattered. I knew the fix. I’d read it, more than once, and nodded at it, and still found forty other things to do before I sat down and wrote the plan I already knew I needed to write. Having the answer changed nothing about my Tuesday. That was the actual tell.
The plan that actually works
Dan Martell’s fix, from his framework on building SOPs, comes down to one question: if you hired someone tomorrow to run your job for two months while you’re on a beach somewhere, what are the conversations you’d need to have with them first? Not a polished manual. The actual list of topics you’d sit down and walk them through, so they’d know what you know before you left.
Run that question for real, on paper, against every recurring decision you make, and you’ll find out fast how much of your “plan” was never written down because it was never fully worked out. That’s the point of the question, not a knock on you. It turns a vague feeling of readiness into a document you can hand to someone and test.
Do it task by task. Pick the decision you get asked about most. Write the goal, the steps, and the why, in that order, until a competent stranger could run it without calling you. Then pick the next one. You don’t need the whole business mapped in a weekend. You need the one thing that pulled you out of your last vacation, documented before your next one.
Do this before you book the next trip
Pick one recurring decision this week. The one someone asked you about most recently. Write the goal, the steps, and the why. Hand it to the person who’d normally ask you. Watch what they do with it before you correct anything.
What happens if you don’t
You keep taking trips you never actually leave. You come back from vacation more tired than when you left, because you spent it running the business remotely instead of resting. Every year you tell yourself this is the year you finally step back, and every year the SOPs are still half-finished when the next busy season swallows the time you set aside to write them.
Or you finish one. You test it the way the question demands, hand it off, and watch someone else run it without you. You go on the next trip, leave the phone in the safe, and come back to find the business held the line without you narrating from a beach chair. That’s the whole bet: one finished piece of the business, run by someone else, while you’re somewhere your phone can’t reach you.
You already knew you should write it down. Sitting still long enough to actually do it is the hard part, which is exactly why I built KyberFive: a thinking partner that runs the interrogation for you, on the actual thing in front of you, instead of waiting for a someday that doesn’t come.