The real test of a system is whether the work moves when you've left the desk.
A week away, not too many meetings, and the clients' work kept moving — because the mechanical parts run on their own. On building systems that outlast your presence, and the judgement that can't be automated.
I'm writing this from Italy. It's the tail end of a week I blocked off on purpose — family, sun, and a rule I set for myself in advance: campaign checks only, no meetings. The kind of week that, a few years ago, I couldn't have taken without something quietly breaking behind me.
Nothing broke. And the reason is the only part worth writing down.
The work kept moving without me at the desk
The companies I look after didn't pause because I did. Every morning a system I built runs a reconcile of my inbox, my tasks and my calendar and hands me a short brief: here's what's waiting, here's what closed itself, here are the one or two things that actually need you. The ad accounts get a fresh pull of real numbers on a schedule, not when I happen to remember. This very post is publishing itself, on a morning I'm nowhere near a keyboard, because the machinery that drafts and schedules the week's writing was set up to run whether I'm there or not.
None of that is glamorous. All of it is the point.
The real test of a system isn't whether it's clever. It's whether the work keeps moving when you've left the desk.
The trap is being the system yourself
The seductive failure mode in this kind of work — fractional, founder, anyone whose value is their attention — is to become the system. To be the person who holds it together by being reachable. It feels wonderful. You're indispensable, you're in every loop, nothing happens without you. And then you can't take a Tuesday off, let alone a week, without a small avalanche waiting on your return.
I spent years there. The shift wasn't working harder — it was moving the mechanical parts of the job out of my head and into things that run on their own, the slow conversion of "what's in your head" into "what the system does." I've written about teaching an assistant to prep my week and about closing a whole quarter's books without a single missing receipt. Those weren't productivity tricks. They were me refusing to be the load-bearing wall.
What the machine does, and what it still can't
I want to be honest about the limit, because "it all runs itself" is a line people sell and rarely mean. The systems handle continuity — the fetching, the reconciling, the surfacing, the publishing. They do not make the decisions. When the morning brief flags that a campaign's efficiency has slipped, or that a client has asked a real question, that still comes to me, and I still make the call, from a café table if I have to.
That's the right division of labour: automate the reachable, keep the judgement. The machine is superb at making sure nothing falls through the cracks. It is not good at knowing which of the things it surfaced actually matters. That part doesn't travel to a scheduler. It stays with the person who's done the reps — which, conveniently, is the whole argument for having one of those people in the first place.
Why this is what "fractional" should mean
There's a version of fractional work that's really just expensive hourly help: rent the person, and when the person's off, the work is off too. I don't think that's worth much, and I've argued that showing up in person still matters enormously — but showing up is not the same as being the only thing keeping the lights on. The version I try to leave behind is the opposite: systems and habits that keep a smaller team pulling the right levers even when I'm on a beach. The company isn't buying my presence by the hour. It's buying a way of working that outlasts any given week.
It's healthier for them, too. A business that only moves when one person is watching isn't really a business — it's a maintenance trap with a pulse. The good ones survive their key people taking a break.
The measure was never how much I could hold in my head. It was how much kept moving the week I put my phone down. This week, nearly all of it did.
Sources & further reading
External
SYSTEMology — Business systems guide: turning tacit knowledge into documented systems
Kevin Anye — How to build a business that runs without you
Related posts
I taught my assistant to prep my week. The hard part was making it stop starting over.
For the first time ever, I closed a quarter without a missing receipt.
Why travel matters (a lot) in fractional executive work
The maintenance trap and the project-driven future