The first video I made for this studio was one clip. The next was a set of eight. By the third project I wasn’t writing separate ideas anymore — I was writing one description, locking it, and changing exactly one thing per piece. That’s the moment a project quietly stops being a thing you make and starts being a system that makes things. This post is about how to notice that moment, and what to do when it arrives.
The tell: you’re repeating a decision, not making one
Here’s the signal to watch for. If you find yourself re-deciding the same thing every time you start a new piece — the same color rules, the same layout logic, the same “how big should the margin be” — you’ve found something that belongs in a system, not in your head.
In the Heroes, Off Duty series — nine miniature scenes of legendary characters — the description of the village itself (the materials, the single warm light, the muted palette) is identical across all nine. I didn’t write nine descriptions of a place. I wrote one, and nine reasons to point a camera at a different corner of it. The creative work was designing the world once, carefully. Repeating it by hand nine times wouldn’t have been more creative — it would’ve been nine chances to accidentally contradict myself.
Why this raises your floor, not just your speed
The real payoff isn’t doing less work. It’s that the quality of everything you make afterward gets set by the system, not by your mood that day. A tired version of you and a sharp version of you write roughly the same locked specification. They do not reliably invent equally good ideas from scratch on demand.
| Making one thing | Building the thing that makes things | |
|---|---|---|
| Where the effort goes | Into this specific output | Into the rules every output inherits |
| Quality depends on | How good you feel today | A decision you made once, carefully |
| Cost of the 10th piece | Same as the 1st | Near zero |
| Biggest risk | Inconsistency across pieces | Over-building before you know the rules |
| What you’re really producing | An artifact | A standard |
This site runs the same way, one level up. Every case study — a video, an image gallery, an embedded clip — is a text file plus a shared set of rules, not a hand-built page. Adding a new project means writing content, not building a new layout. The portfolio, honestly, isn’t the collection of finished pieces anymore. It’s the small, unglamorous configuration that turns a folder of writing into a consistent set of pages.
The trap: building the system too early
There’s a failure mode on the other side. If you build the machine before you’ve made anything by hand, you’re systematizing guesses. You don’t yet know which decisions are stable enough to lock. The honest sequence is: make a few by hand, notice what you keep re-deciding, then extract that into a system. Systematize the pattern you’ve proven, not the one you’re hoping for.
How to Proceed
- Look at your last three projects. Write down every decision you made in all three that came out the same way. That list is your system, waiting to be extracted.
- Pick the single most-repeated decision and write it down once, explicitly, as a rule. Not in your head — on paper or in a file.
- On your next piece, change only one variable from the last one. Notice how much faster it goes when the rest is locked.
- Resist systematizing anything you've done fewer than three times. If you can't point to the repetition, you're guessing.
- Once a month, ask: what am I still doing by hand that I've now done enough times to trust? Promote it into the system.