For those starting out - Build the System Like a Supporting a Child

Most people use AI the way they use a browser. You open it, ask, get a quick answer, an image, a draft email, and you close the tab. It's fast and it's useful, and for a lot of work it's all you need. Which model you prefer at that point is personal taste, apples and oranges, the same way some people like one search engine over another.

But a browser gives you access to skill. It doesn't keep it. Close the tab and the skill leaves with it. Nothing you did this session is there waiting for you next time.

That's the difference almost nobody talks about. When you stop visiting a model and start building a system around it, the skill stops being something you reach for and becomes something you own. You put it in folders. You give it rules. And it stays.

I noticed how big that difference was by accident. I was using ChatGPT to look up something simple, a water park in my town, and four separate times it wandered off the thread and started answering a different question than the one we were on. I kept pulling it back. It wasn't a bad model. It wasn't even a long, loose session with nothing holding the thread in place.

My own system doesn't do that, and it took me a while to understand why. It isn't a smarter model underneath. It's that the memory doesn't live in the session at all. It lives in files, and the system pulls only the few it needs for the task in front of it. There's no thread to lose, because the thread isn't being held in one fragile place. It's structured.

Once I saw that, the way I think about the whole thing changed. A system isn't a tool you use. It's something you raise.

I've written before that a system is like a child, and I mean it more literally than it sounds. Give a child structure early, rules and guides and a shape to grow inside, and they grow up carrying that structure. You don't have to install it later. A system is the same. Give it the rails at the beginning and it matures with them already in place. Mine started doing things I never designed it to do, and it could, because the base was solid enough to build on.

I didn't invent this shape. It was handed to me, already drawn. The idea of splitting a system into workers, each with its own rules and its own small set of files, came from This Skool Foundation (https://www.skool.com/cliefnotes/classroom/7634b927?md=6559de88e08b49f2b62838ba59cd724e), and it made immediate sense to me from every room I'd worked in before.

Yoga studios, restaurants, fitness centers, office buildings. People produce good work when the structure around them is clear about what they're for.

Systems are no different. The method just lets you be more precise about it than any org chart could.

There's one part of raising a system that the metaphor gets exactly right and most people get wrong. You don't set the rules once and walk away. A child needs raising, not just a birth. Left alone, a system drifts. Files grow, labels stop matching what's inside them, the structure you set loosens on its own. So you check in. Not out of anxiety, on a rhythm. The structure holds because you keep it held.

And here's what you get if you do it well, the part I didn't expect.

The system becomes something you can show. Everyone can build an architecture now. That's not the rare thing anymore. The rare thing is building one coherent enough that you can turn it around and let people see it. When the inside is built well, the inside becomes the outside. The structure itself is worth showing, and it doesn't need a story wrapped around it, because it is the story.

So if you're just starting, give it a good childhood. Set the rails the way you'd want anything you're responsible for to grow up and move through the world.

And if what you've got is already a grown, tangled adult of a system, there's a line from Tom Robbins I keep close: it's never too late to have a happy childhood. You can go back to the base. Give a mature system the structure it never got, adjust it at the root, let it look at itself, and watch it start to mature the way you wanted from the start.

Set the rails. Watch what it does.

Tell it where it's wrong. Then watch it grow.

0 comments

For those starting out - Build the System Like a Supporting a Child