A watercolour teacher gave himself a development team this week. Four of them, running at once. Here's what changed, and what it costs to do it well.
I am not a developer. I teach people to paint. I run a craft business. The most technical thing in my week is usually whether the card reader will talk to the till.
And this week I gave myself a development team.
Not metaphorically — or rather, exactly metaphorically, which turned out to be the point. Four AI sessions, running at the same time across two machines, each with a job. One building software. One doing the marketing. One writing. And one sitting above the others as a kind of manager: the session I actually talk to, that knows what everyone else is doing and tells me where things stand. A control tower.
I'd been doing it the other way for months: one conversation, me and one AI, trying to make it do everything. Build the thing, then write about the thing, then plan the next thing, all in one long thread. And it works, the way a single very willing employee works when you keep loading more onto them. Eventually they're holding too much. The thread gets long and slow and forgetful. I get long and slow and forgetful, jumping between jobs that have nothing to do with each other.
The unlock wasn't a cleverer AI. It was the realisation that the bottleneck was the shape of the work, not the worker. A builder shouldn't also be doing your marketing in the same breath. So I stopped asking one session to be everything, and I split the day into lanes: a builder, a marketer, a writer, each one a focused mind doing one kind of thing well. And then I gave myself the only job that was ever really mine: not doing all the work, but directing it.
That's the manager session: the control tower. I don't build anything in it. It reads what each lane has produced, tells me what's ready for a decision, and only the irreversible things (sending something, publishing something, taking a payment) wait for my explicit yes. The rest just flows.
Two things surprised me.
The first is how strange and good it feels to review work from a session you've never spoken to. This week the marketing lane (running on the other machine, that I never typed a word into) finished a piece of competitive research and I read it from across the house, on the manager's board, with no idea it was even underway until it appeared. A colleague I'd never met had done good work and filed it. That's a feeling small businesses almost never get to have: someone got on with it.
The second is that I can run the whole thing from my phone. With the mini sitting at home doing the heavy lifting, I can check the board, see every lane's status, and send a new instruction from my pocket on the school run. The office works while I'm at the easel.
I won't pretend it's frictionless, because the honest version is more useful than the brochure. It takes discipline. The AIs don't share a memory, so you need a single shared board they all read and write (I learned that one the hard way; separate post). You need guardrails written down once and applied everywhere, or a fast, capable session will cheerfully do something you'd never have allowed. The more able it is, the more that matters. And you need good briefs; a lane is only as good as the instruction you hand it. The briefing really is the work.
But none of that is developer knowledge. It's management knowledge: the stuff I already had from years of running things and didn't realise transferred. Lanes, hand-offs, sign-off, a single source of truth, knowing which decisions are yours and which to delegate. I've run teams of people. This is the same craft, pointed at a different kind of colleague.
Which is why I'm writing it up. Not the breathless "AI changed my life" version, the practical one. What machine you actually need (less than you'd think). How to set the lanes up. The guardrails that keep it safe. The shared board that keeps it sane. The prompts that get good work instead of confident nonsense. The whole scaffolding, so a one-person business or a five-person one could stand up their own control tower in an afternoon and stop being the bottleneck in their own week.
I'll say plainly where the edge of that is, too. What I've built for myself goes further than the version I'll hand you: there's a layer that knows me personally, my library, my health, my history, that I'm not giving away, because that's the part that took three hundred hours and a lot of my life to earn. But you don't need that to feel the change. The plain control tower — disciplined, multi-lane, coordinated — is already a step-change for anyone who's been trying to be everywhere at once.
I spent a long time believing the answer to "too much to do" was more of me. Earlier mornings. Held breath. It was never more of me. It was a better-shaped us, and me in the tower instead of down on the floor doing everything by hand.
I'm writing up exactly how to stand up your own version (the machine you actually need, the lanes, the guardrails, the shared board, the prompts) as Build Your Own Multi-Lane Claude CoPilot. Want the early version? The signup's at creativepath52.com.
— Damian
