Day 13 of 100, building The Autonomous Leader in public.
On paper I did two unrelated things today: I built a piece of software and reworked a course outline. They were the same project, pointed at one goal — take me out of the work. And both ran straight into the same test I keep coming back to when I decide whether a system is actually done.
The day: I built two systems, and neither one was about me
I started the morning the way I have started a lot of mornings lately — vibe coding. I have managed projects a particular way for years, and I have never found a tool that lets a team operate the way I believe a team should. So instead of bending my process to fit someone else's software, I am building my own. No traditional programming. I describe what I need in plain language and the AI writes the code. What I have at the end of the day is a working project-management tool I built by having a conversation.
Between coding sessions I went back to the outline for the content system course, the one that teaches owners how to build their own content production line. I kept pulling on one thread: how little the owner should have to do. The standard I landed on is that the owner does exactly one thing — get filmed. Everything downstream is handled by the system. Editing is handled. Captions are handled. The research on how to optimize each piece is handled. Outreach to interview or collaborate is handled. Publishing is handled. Engagement is handled. The owner records, and the machine does the rest.
Then, needing a task that asked less of my brain, I set up the digital headquarters for the team — the place where we collaborate and move work between us.
The move: a system that still needs you isn't finished
Here is the test underneath all of it, stated plainly: if the owner has to touch it after they stop recording, the system is not done yet. That sentence is the whole standard. Not "is there a system." Not "is most of it automated." The question is whether the work can cross the finish line without the owner's hands on it a second time.
That is the same idea from the other direction as the work only the owner can do: the owner has exactly one irreplaceable input, and the job of the system is to protect that input by absorbing everything else. On the course it is being filmed. In the business it is whatever only you can actually do. Most owners build the opposite — a process that technically exists but still routes back through them at ten different handoffs — and then call it automation because software is involved somewhere in the middle. Software in the middle is not the test. Hands off at the end is the test.
Why this is a Grinder problem
Process is the pillar that asks one question: does the work run the same way whether or not you are there to run it? At the Grinder level, the honest answer is still not yet — nearly everything runs through me, which is exactly why I spend my days building the things that will not. This is the same work I was doing on Day 10, when I built the system before the hire instead of after, and it rests on the same math as a system that costs you once instead of a task that costs you every time.
The hardest test of that standard comes next. I have to define the principles the editors will work from — what the brand sounds like, the music and sound effects we use, the footage we accept and the footage we do not, and how a file moves across the whole system from capture to published. If I do not define those on purpose, they get defined anyway — by guessing, one decision at a time, until the brand is an accident. And a system built on my team guessing is a system that still needs me to correct it, which means, by my own test, it is not finished. This is why I onboarded the editors by building the process with them rather than handing them a finished manual — but someone has to set the standard the authorship is built on, and that part is still mine.
The nameable benefit of Day 13 is easy to say and hard to hold to: build the system so the only thing left for you is the one thing only you can do. A system that still needs the owner after the handoff is not a finished system. It is a draft wearing the word "automated."
That is tomorrow's work, and it is the difference between a team that is autonomous and a team that is just guessing with confidence — between a business that runs and one that only looks like it does.
Follow along to see me build The Autonomous Leader.
Wondering how much of your business would actually finish a cycle without your hands on it twice — or whether every process still loops back through you? 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.