The Install
Hi. My name is...
Most of you thought Slim Shady. You didn't choose to. Your brain finished the line for me.
That's not a memory. That's a file. Eminem put a .mp3 on enough devices that 27 years later the phrase auto-completes in your head before you've had time to decide whether to finish it. You are the evidence. Before I've made any argument, you've already proven the thesis on yourself.
The .mp3 isn't the song. The .mp3 is the install. And the install is what survives everything else. Not the tour. Not the interviews. Not the chart position. The file on the device. The thing that kept traveling after the moment that made it was long over.
I've been building things long enough to have a folder full of projects that didn't travel. Launches that landed for a week and then went quiet. Work I thought was strong that didn't earn a second look. And other things, scrappier things, that ended up everywhere. That people I'd never met knew about. That came back to me years later in the form of "I've been using this since forever."
The difference wasn't quality. It was distribution.
Not distribution like marketing. Not "post more content." The kind of distribution that puts your format on someone's device and leaves it there. The kind that becomes part of a workflow before anyone has consciously decided to adopt it. The quiet install. The format that gets kept even after its creator has stopped thinking about it.
Here's the thing about quality versus distribution: the best version of something that no one has isn't better than the good-enough version of something that everyone carries. The PDF isn't the most elegant document format. It won because it ended up on more devices than anything else. Same with the .mp3. Same with the .jpeg. The format that earned a life was the format on the most machines. Not the most correct. The most installed.
Distribution earns legacies. Distribution IS the legacy.
What I keep going back to
There's a notes format I've been using for three years. Not because it's the best one available. Because it's become part of how I think. The structure has got into my head. I open it before deciding to open it, which means it won. The format earned a place in my process before I had any real opinion about it.
There's a community I check before anything else in the morning. Not because I made a decision to prioritize it. Because it became the room I go to first. The people there have earned attention I didn't consciously budget. It installed itself.
There's a file format I've been shipping work in for a couple of years. Not because it was the obvious choice at the time. Because once I started, I noticed what got opened and what didn't. The files that traveled were the files in that format. Not because the format was technically best. Because it spread.
The thing in common: I didn't decide to keep going back. The format made the decision for me.
That's what earned distribution looks like from the inside. Not "this is objectively the best tool." Not "I consciously chose this." More like: it's already loaded. I'm already inside it. The switching cost has disappeared without me noticing. The thing didn't win a competition. It became load-bearing.
The .mp3 isn't the song. The .mp3 is the install. Once it's on the device, the song plays every time without a decision. The device is the distribution. The format is the mechanism. The install is the legacy.
When I think about what I want the things I build to do, it's not "get praised." It's not "win the award." It's: end up on enough devices that it starts completing things for people. That it loads before they've had time to decide. That someone three years from now can't tell you when they started using it, because it's been load-bearing long enough that the install date doesn't register anymore.
The output folder is what survives
I spent a long time charging for the hours.
Which sounds reasonable until you think about it from the other side. The client doesn't experience the hours. They experience the file. The deliverable. The thing they put in a folder and reference six months later when the person who commissioned it has moved on.
The 2am call where I figured out the real problem. The three rounds of direction before the brief got tight. The rough version I had to make before I could make the right version. None of that is in the folder. None of it travels. The thing that travels is the output.
I had a project once where I spent the better part of a week on the front half of the process and a focused afternoon on the actual deliverable. The client never knew. Why would they? What they received was an afternoon of value. What they kept was an afternoon artifact. The rest existed only in my working files, and working files don't travel.
This is not a complaint about clients. It's a correction to how I was thinking about what I was selling.
Once I understood that the output is what survives, I stopped centering the engagement on the path to it. The deliverable became the thing I designed the work around, not the thing at the end of it. The brief got written backward from the output folder: what's in it, what does it need to do once I'm not in the room, what format does it need to be in to travel past this job?
The hours are the overhead. The folder is the product.
You can love the process and still price the output. I do. The 2am thinking is where the real work happens. But no one is buying my thinking. They're buying the thing my thinking makes. And the thing my thinking makes is the thing that earns a life past the invoice.
The line you can't get out of your head is the line that earned a life.
Not because it was the sharpest writing. Not because the production was the cleanest. Because it got on enough devices, early enough, and stayed. The brain that kept replaying it didn't choose to. That's the signature of something that genuinely installed.
The question isn't whether something is good. The question is: what's in your output folder right now that someone, somewhere, can't get out of their head? What did you ship, in a format that could travel, on a day someone needed it? That's the thing with a life past your invoice.
I name my work like a file format on purpose. .PushingSquares isn't a brand. It's a bet that something is worth installing. I've been making that bet for a while now. Some of the bets paid off. Some didn't. The ones that did ended up on devices I'll never count.
I wrote up the doctrine over on Pushing Squares if you want the systematic version. Or keep making files. Either way.
Make more files. Get them on more devices. That's the whole game.