Ari’s Space*   est. 2026
Skip to content
ari*s space[ a. ]
← Librarythoughts and scribbles / 2026-05-03

The Install

The .mp3 isn't the song. The .mp3 is the install. A personal essay on the formats that earn a life and the output folders that survive.

3 parts / Hover to explore. Click to read.

The .mp3 isn't the song. The .mp3 is the install. A personal essay on the formats that earn a life and the output folders that survive.

Thinking + preparation
          |
      useful deliverable
          |
  format the recipient can open
          |
     keep -> use -> pass on

Design from the output folder.
The deliverable carries the value after the maker leaves. Compatibility, clarity and repeated usefulness give it a chance of a longer life; a busy launch does not establish that.

Hi. My name is...

If your head supplied “Slim Shady”, you already know the feeling I'm talking about. A few words arrive and something familiar starts playing before you've decided to remember it.

I think of that as an install. The file travelled, got played and became part of someone's life. The song is the work; the format is one of the things that lets the work keep travelling after its launch is over.

I've made projects that had a good first week and then went quiet. I've also made scrappier things that turned up years later through somebody saying they'd been using them for ages.

Quality alone didn't explain the difference. I had to look at how the work reached people and whether they could keep using it.

That's the kind of distribution I mean here. A file someone can open, keep, pass on or bring into a workflow. A format that doesn't need its maker standing beside it to explain what to do.

PDF, MP3 and JPEG are useful reminders. Technical elegance isn't the only thing that helps a format last. Being available on the devices people already use matters too.

.pdf
.mp3
.jpeg
.PushingSquares

Notice what you keep returning to

At the time I first wrote this, I'd been using one notes format for three years. It wasn't a daily contest between that format and every alternative. Its structure had become part of how I organised a thought.

There was a community I checked before anything else in the morning. It had become the room I went to first. And there was a format I'd been delivering work in for a couple of years because I could see those files getting opened and passed around.

Different things, similar behaviour. They had earned a place in an existing routine.

That doesn't mean a format literally makes decisions for you. It means repeated usefulness can turn into a habit. You stop evaluating the whole tool every time you use it. It's already there, ready for the job.

When I think about the things I want to build, that is more interesting to me than a burst of praise at launch. I want someone to keep finding a use for the work after I've moved on to the next project.

What would let your file do that? Does it open where the person works? Does its structure make sense? Can they use it again without coming back for instructions?

Those questions belong in the design, not just in the launch plan.

Design backwards from the output folder

I spent a long time thinking about what I sold in terms of hours.

The client receives something different: a deliverable. A file they can put in a folder and refer to months later, perhaps after the person who commissioned it has moved on.

They don't receive the 2am call when I worked out the problem, the rounds of direction that made the brief useful, or the rough version I needed to make before I could make the right one. That work matters. It simply doesn't all travel with the finished thing.

On one project, I spent most of a week on the thinking and preparation, then a focused afternoon on the deliverable. The client didn't need to know that timetable. They needed the result to work.

That changed how I thought about the engagement. I began with the output folder: what has to be in it, what must each file do when I'm no longer in the room, and what format gives it a useful life beyond this job?

The preparation still creates value. Designing around the deliverable makes that value usable by someone else.

You can love the process and price the output. I do. But the output needs enough clarity and completeness to carry the work forward without the whole process attached.

Output folder animationWORKINGOUTPUT

Look at what you've already shipped. Which things are still being opened? Which get forwarded? Which have become part of somebody's working day?

That is more useful evidence than whether a launch felt busy. It tells you what the work can do once it leaves you.

I name .PushingSquares like a file format on purpose. It's a bet that the work is worth installing: something a person can keep and use. Some of those bets have worked. Some haven't. The ones that did reached devices I'll never be able to count.

I wrote the more systematic version of this doctrine on Pushing Squares. This is the personal question behind it: what have I made that still helps somebody when I'm not there?

.PushingSquares icon drag animation

For the next project, decide what belongs in the output folder before you count the hours. Make the file useful enough, and easy enough to carry, that it has a chance of a life beyond the invoice.

[ comments ]

guests welcome. members show first in the list

no comments yet. start the thread_

1 / 5