Day 12 of 100, building The Autonomous Leader in public.
I have been building this company alone for eleven days. Today two people showed up to build it with me. I onboarded my first two editors — one for social media, one for course creation — and the meeting ran just over two hours. There is a version of that meeting where I walk in, present a finished, polished playbook, and make the business look like it has everything figured out. I did not run that version. And skipping it was the most important decision I made all day.
The day: onboarding, and the temptation to look finished
The morning was preparation and filming. I finished the systems I had been documenting for the editors, filmed a batch of content, then sat down with both of them after lunch. We went over what the business does, how it does it, and what we are here to offer. We went over the current brand — what is figured out, and what is still open.
That last part is where most onboarding meetings quietly go wrong. There is a strong pull, when someone new is watching, to present the business as further along than it is. You want to look like the leader who has already solved everything. But we are early in building this company, and pretending otherwise would have handed my editors a map with no legend — a picture of a place that does not exist yet. We would all be better served by being honest about what point in the journey the new hire is actually joining.
So instead of presenting a finished system, I showed them the unfinished one. We identified the processes that still need to be documented, and we divided the responsibility. Each of us — including me — took ownership of specific processes, with deadlines to report back. Then I gave both editors access to every platform, every brand asset, every file they would need. The central location I built two days ago is exactly what made that handoff fast. This is the same principle from Day 10 — build the system before the hire, not after: the work I did before anyone arrived is what let them start without waiting on me.
The move: authorship is ownership
Here is the thing I did not fully understand until I watched it happen in the room. An employee who helps build the process follows it differently than one who is handed a document they had no part in creating. Geoff Woods put it in four words: authorship is ownership. You own what you help create.
When you drop a finished manual on someone's desk, you have given them a rule to comply with. Compliance is fragile — the moment reality does not match the document, they stop and wait for you. When you invite someone to help write the process, you have given them something to defend. They do not just follow it; they improve it, because it has their name on it. That is not a soft, feel-good distinction. It is the difference between a system that needs you standing over it and one that runs when you are not in the room.
Why this is a Grinder problem
People is the pillar that asks whether the business can add a person without adding a bottleneck. At the Grinder level, the honest answer is not yet — the whole thing still runs through me. The instinct at this level is to solve that by hiring, then to protect your authority by handing new people finished instructions and keeping the thinking to yourself. That instinct doubles the bottleneck instead of removing it, because now two more people are waiting on you to interpret the document every time it breaks.
Building the process with my editors is how the bottleneck actually starts to dissolve. Yesterday I decided to bring on both roles at once — Day 11 — marketing and fulfillment have to move together — for exactly this kind of reason: the two jobs are one system. Today I learned that whether that system survives contact with real work depends on who helped write it. A documented process no one owns is just a task you paid for once and still have to supervise forever. A documented process with an author is a piece of the business that finally lives outside your head.
The nameable benefit of Day 12 is short and easy to skip when you want to look impressive: build the process with the people who will run it. Authorship is ownership. The owner who hands down finished playbooks keeps every judgment call routed back through themselves. The owner who shares the pen gets people who defend the system instead of waiting on it.
Tomorrow the team reconnects to confirm everyone has the access they need, and I start mapping the color-grade process so everything we publish looks like one company — more systems, built to be owned, not just obeyed.
Follow along to see me build The Autonomous Leader.
Wondering whether your next hire would actually free you — or just give the bottleneck a bigger line? Take the free 7-Level Assessment — it names the level you are operating at and the constraint holding you there. Or see the ways to work together.