“It’s faster if I just do it.”
I’ve said it. You’ve said it. It’s one of the most reasonable sentences a business owner says, and it’s the sentence that keeps everything on your desk forever.
Here’s the thing about it. It’s true.
It’s true exactly once. And then it’s false for the rest of your working life, and you keep saying it anyway.
Why it’s true the first time
The reason it’s faster to just do it is that the process is already finished inside your head.
Not written anywhere. Not spoken out loud. Just complete. You know which folder it goes in, you know that this particular client gets a different tone, you know that the third step gets skipped in December, you know that when the number looks wrong it’s usually because of the thing that happened in the spring.
None of that is written down. All of it is instant.
So when you weigh “do it in eight minutes” against “explain it in forty,” the eight minutes wins. Correctly. That day, you made the right call.
The trouble is the ledger. Every task you keep because explaining it is expensive is a task you now have permanently. And your business grows into the shape of exactly what you personally can hold — which is a real shape, with real edges, and you hit them.
The forty minutes never got cheaper. You just kept not spending it.
The thing I got wrong for fifteen months
When I started trying to get AI to run parts of my business, I assumed the barrier was technical. That there was some technique I was missing. That the people getting extraordinary results knew something about the tools that I didn’t.
I spent fifteen months going in circles on that assumption. Reading more. Trying harder. Taking better notes on prompting.
The barrier was not technical.
The barrier was that nothing was written down.
Every time I asked for something and got back generic, mediocre work, the reason wasn’t the model. The reason was that I had asked for “a caption for this” and I was silently measuring the result against a standard that existed only in my head — the one that knows I don’t use exclamation points, that this brand sounds different from that one, that I’d rather say nothing than say something that sounds like everyone else.
I was grading an open-book test and refusing to hand over the book.
Which is exactly what I’d been doing to every human I’d ever tried to hand work to, incidentally. I just hadn’t noticed, because a person will nod, guess, and produce something close enough that you correct it rather than reconsider the whole arrangement.
An operator is only as good as the brief
This is the sentence the whole thing turns on, and it took me embarrassingly long to arrive at it.
An operator is only as good as the brief.
Not as good as the model. Not as good as the tool. As good as the brief — the accumulated, specific, written-down record of how your business actually works and what “good” looks like when you see it.
Once I understood that, I built it into the operators themselves, because I didn’t trust myself to remember.
Atlas won’t organise anything before it runs a preference interview. It doesn’t get to assume a filing structure; it has to find out how you think first. Charter won’t draw a single box until it has answers to ten questions about what the chart is for and who’s going to look at it, because a wrong node is harder to remove than a missing one. Sage will refuse a vague research brief outright and ask you to narrow it, rather than spending an afternoon returning something impressive and useless.
Every one of those is the same design decision, made three times. Get the brief first. Nothing good happens before the brief.
I wrote about what “pre-trained” actually means in this piece, and this is the half of it people underestimate. The operator arrives knowing how to do the job. It does not arrive knowing your business. That part is yours, and there’s no version where it isn’t.
Why the Setup Kit is mostly documents
People are sometimes surprised by what’s actually in the AI COO Setup Kit.
They expect software. What’s in it is a setup guide and a set of documents — a structured conversation your AI runs with you, question by question, one at a time, waiting for the full answer before it moves on. What your business is. What you sell and to whom. What your week actually looks like. What drains you. What you’d never hand off. What your AI should never do without asking you first.
Sixteen questions in the first pass. Then a second, deeper one that fills in the gaps and writes it all into files your AI reads at the start of every session for the rest of its life.
That’s the install. Not the technical part — that’s a handful of steps and it’s over. The install is the conversation.
Which sounds soft until you sit down to do it, and then you find out it’s the hardest part, because you have never once said any of this out loud in a complete sentence.
I have watched capable people stall on “what does your ideal client actually want” for longer than the entire technical setup took them. Not because they don’t know. Because knowing and articulating are genuinely different, and one of them you’ve practised for years and the other you never have.
The reason it was never written down
I want to name this properly, because “just document your processes” is advice that has never once worked on anybody, including me.
The reason it’s all in your head isn’t disorganisation. It isn’t laziness. It’s that documentation with no reader is homework.
Every time you sat down to write a process, some honest part of you knew that nobody was going to read it. There was no one to hand it to. The last person you handed something to left, or you never hired them in the first place. So you’d write a page and a half and stop, and the guilt from that abandoned document became one more reason not to try again.
That’s not a character flaw. That’s a completely rational response to writing for an empty room.
What changed for me wasn’t discipline. It was that there was finally a reader. Something that would actually take what I wrote, use it every day, and never need it re-explained.
Writing the process down stopped being homework and started being the install step. Same act, entirely different weight.
How to start without sitting down to “document processes”
Don’t schedule a documentation session. You won’t go, and if you go you’ll write in the wrong register — formal, procedural, useless.
Do this instead. The next time you catch yourself thinking “it’s faster if I just do it,” do it — and narrate it while you do. Out loud, into a voice note, or typed in a scratch file. Not the steps. The decisions.
Not “open the folder.” Rather: this goes here and not there, because. Not “write the caption.” Rather: this one gets the shorter version, because that audience scrolls.
The becauses are the whole thing. The steps are obvious and mostly not worth writing. The judgment underneath them is what has been trapping the task on your desk, and it’s the only part nobody can guess.
Three or four narrations in, you’ll notice you’re repeating yourself. Those repeats are your actual rules. Write those down and you have a brief.
The first thing I actually wrote down
It wasn’t a policy. It wasn’t an SOP binder. It was a flowchart.
The first one was the customer journey — what actually happens, step by step, from the moment somebody finds us to the moment the work is done and they’ve been properly looked after. Then the admin journey, which turns out to be a completely different path running over the same ground. Then every individual role’s journey, one at a time.
And then the thing I hadn’t expected.
The journeys collide.
You cannot see that while it’s all in your head. In your head each path runs cleanly, because you only ever run one of them at a time and you’re the one holding all of them, so the joins are invisible to you by definition. Drawn out and sitting side by side, you can see exactly where the customer is waiting on a step that belongs to admin, where two roles are each quietly assuming the other one handles it, and where a handoff has no owner at all.
That’s the real argument for writing things down, and it isn’t the one people usually make. It isn’t that you’ll end up with a document. It’s that you cannot see the shape of your own operation while it’s stored in the only place that can’t show it back to you.
Charter is the operator that draws these for me now, and I’ll name it because people ask. But the tool is not the lesson here. The drawing is the install step. Anything that gets the journeys out of your head and onto a surface where you can watch them collide will do the job.
What you get back
You do this once.
That’s the part that took me longest to believe, having re-explained the same things to enough people over enough years to assume re-explaining was simply the cost of having help.
It isn’t. Written down, in files your system reads every session, the context holds. Tomorrow, next month, and after a change of direction you haven’t had yet — you’ll add to it then, not rebuild it.
The forty minutes you kept not spending? Spend it. It was never forty minutes a task. It was forty minutes, once, per thing you’re tired of owning.
Where to start
The AI COO Setup Kit is the version of this I built for myself and then cleaned up. It walks you through the whole foundation in order — the dedicated space, the memory that carries between days, and the conversation that gets your business out of your head and into something that can actually be handed off.
It’s the fifteen months I spent going in circles, turned into a sequence.
Bring the thing you’ve been telling yourself is faster to just do. That’s the one to start with.