In July I released Months, my debut EP under Again and Again, and wrote about it in Shipping Something That Isn’t Useful.
The point of that piece was permission. Not every project has to become a product, make money or justify itself before it’s allowed to exist. Sometimes turning a folder of unfinished tracks into something complete is reason enough.
It ended on a modest hope. Maybe only a handful of people would ever listen, and that would be okay.
Four months later, it’s worth checking whether that held.
What was worth watching
The habit that piece pushed against is one I actually have. Before starting almost anything, I ask who it’s for, whether it’s worth the time, whether it could become a product. Those questions are useful in most of my work, which is exactly why they don’t switch off on their own.
Release is the natural place for them to come back. Once something is out, there are numbers to look at and an easy next question: what now? Promote it. Follow it up. Turn one EP into a project with a plan.
So the open question in July wasn’t whether finishing the EP was worth it. That was settled the day it came out. It was whether it could stay finished.
What actually happened
It stayed finished.
No follow up pressure surfaced. I’ve shown the EP around, it’s on Spotify and Apple Music, and since release it has simply sat there, existing quietly. It didn’t turn into a release schedule. It didn’t start asking for a second EP or a reason to have been made.
Songwriting itself has gone quiet. Sporadic at best right now. That isn’t the EP’s doing, and it isn’t a problem. Writing tends to pick back up when there’s a next project to write toward, in the small shape I described in Not Every Hobby Wants the Same Kind of Structure, where a demo counts and an idea gets recorded before I decide whether it’s good enough. Between projects, it can rest.
Why it held
The decision about what Months was got made at the start, not after release.
When I began working on it, I already knew what it wasn’t. Not a startup, not a product, probably not even something that would pay for itself. The scope was narrow and concrete: take these unfinished tracks and finish them. Once they were finished and out, the project was complete by its own definition. There was nothing left for pressure to attach to.
That’s the same mechanism as in Shipping Experiments Instead of Chasing Outcomes. There, a song counted as shipped once there was a demo, and the EP showed up as a side effect of shipping rather than as the goal. Define what done means before you start, and done has a much better chance of staying done.
Beyond music
This isn’t specific to music.
A lot of work quietly assumes that anything shipped is the start of something ongoing. A v2, a maintenance plan, a growth target. Some things should be ongoing, and those need to be designed that way from the beginning. But plenty of work is better off finished. A tool built for one migration. A prototype that answered its question. A project that did exactly what it was scoped to do.
The judgment is in deciding which kind you’re building before it ships. Otherwise every finished thing slowly picks up obligations it was never meant to carry, and the cost shows up as attention spent on things that already did their job.
Closing
In July I hoped Months could exist without needing to become anything more.
Four months later, that’s exactly what it does.
It didn’t need protecting from follow up pressure. It needed a clear definition of done, set at the start, and that was enough.
One more thing
Months is done. That’s the whole point of this piece.
It just isn’t the last thing.
Something is coming next year. Bigger than Months, and planned from the start as its own project, not a sequel Months owes anyone. Which also means the songwriting that’s been quiet all autumn finally has somewhere to go again.
That’s all I’ll say for now.



