If You Got Hit by a Bus Tomorrow
Your team could survive you taking a vacation. Nobody's tested what happens if it's permanent.
Nobody plans for that. Everybody assumes there's more time.
Ask an owner what happens if they vanish tomorrow and most of them laugh it off. Ask a follow-up, who runs payroll, who actually knows what's in the contract with your biggest client, whose cell number is the only way anything gets ordered from your main vendor, and the laugh stops fast.
None of that got hidden on purpose. It just never got written down. You built the process while you were the only one doing it, it worked, and there was never a slow week where writing it up felt more urgent than the fire in front of you. Three years later it's still living in your head, in a format nobody else can access, because the format is you.
The scenario doesn't have to be a bus. It's a resignation with two weeks' notice. It's a surgery that turns into six weeks instead of two. It's you being unreachable for four days because you finally took the trip you'd been putting off. The business doesn't need you gone forever to feel this. It needs you gone long enough that someone else has to guess.
And guessing is expensive. Not because the process was complicated. Because reconstructing it under pressure, from memory, while the thing it supports is already late, always costs more than writing it down would have.
I watched an operations manager go out for a scheduled procedure, expecting two weeks. It turned into seven. Nobody else knew how the month-end close actually worked, step by step, and the business ran almost two weeks blind before someone rebuilt it from a folder of old emails and a lot of guessing.
Issue 1 sorted what's actually worth doing. Issue 2 got you comfortable handing pieces of it off. Issue 3 killed the work that shouldn't have existed at all. None of that holds if the parts you kept still only exist in your head. You can have the clearest task list and the cleanest team in the world, and if none of it is written down anywhere but you, you've built a business that runs exactly as long as you're personally available. All three are in the archive if you joined late. Next week prices what all of that costs.
This week, one small move. It won't document your whole company. It'll show you how exposed one piece of it already is.
First Move
One small move. Complete on its own.
Pick one process that only lives in your head. Write down every step, in the order you'd actually do them, the way you'd explain it out loud to someone who has never touched it before. No shorthand, no "you'll just know."
If you can't finish it in one sitting, you've found the most exposed process in your business. That's useful information on its own, before you write another word.
Below this line is what subscribers get once the paywall goes live at Issue 5: the deeper exercise and a three-prompt pack. Map every process where you're the single point of failure, turn what's in your head into something someone else could actually follow, and get a usable SOP out the other end. For now, through Issue 4, it's yours free, no catch.
Field Application
The exercise. Every issue ends with one of these.
The First Move wrote up one process. This finds every process only you know, ranks them and writes up the worst one, so if the process you picked turns out to be the worst, step 03 is already done. Plan on about three hours of your own time, plus however long your reader takes in step 04.
01. Map It
List every process, task, or decision where you are currently the only person who knows how it's done.
02. Rank the Exposure
For each one, rate what happens if you're unavailable for a week: nothing, a delay, or a real problem.
03. Start With the Worst One
Take the highest-exposure item and write it up the way you did in First Move: full steps, plain language, no assumed knowledge.
04. Assign a Reader
Name one specific person who should be able to run it from your write-up alone. Hand it to them and find out if they actually can.
AI Edge
Writing it down is the easy part to skip and the hardest part to do well from scratch. Do the steps by hand first. Where Prompt 1 says [paste your notes], paste the write-up from step 03. If you skipped a step, the AI asks you for what's missing. Then paste these three prompts into ChatGPT, Claude, or whatever you're using, in order, in the same chat. Each one builds on the last.
Prompt 1. Process Documentation Builder.
"Here is a rough description of a process I run: [paste your notes]. Turn this into a clear, numbered, step-by-step process document a competent new hire could follow with no prior context. Flag any step where you had to guess at something I didn't fully explain, and ask me to fill in the gap before finishing."
Prompt 2. Knowledge Transfer Template.
"Using the process document above, build a one-page knowledge transfer sheet: what this process is for, who currently owns it, what tools or access it requires, the three most common ways it goes wrong, and who to ask if something breaks. Keep it to one page."
Prompt 3. SOP First Draft Generator.
"Combine the process document and the knowledge transfer sheet into a first-draft SOP formatted for our team's standard SOP layout, or a simple Google Doc if we don't have one yet. Include a version date and a placeholder line for 'last reviewed by' so it doesn't go stale the way everything else has."
Issues 1 through 4 are free. That stays true.
Starting with Issue 5, every issue splits at the line you crossed above. The narrative and the First Move stay open to everyone. The step-by-step exercise, the prompt pack, and a new tool every month go to paid subscribers, $47 a month. The first 50 paid subscribers pay $27 a month, for as long as they stay.
Join at any point and the paid half of every issue from 5 on opens up. Nothing to catch up on, nothing to unlock one at a time.
If these four gave you something worth doing, the next ones give you the harder version. Or skip it. The free half still lands every Monday.
That's Issue 4. Every Monday, one problem, one week to act on it.
Work with Eliv8
If any of this sounded like your business, Ground State is the fix. It's a fixed-fee diagnostic that finds where the structure is leaking and puts the answer in writing. See how it works.
If the problem isn't figuring out what needs documenting but actually writing it, that's what GBTC does. See what GBTC does.
