Nobody Told Me Songs Could Breathe: How I Learned to Stop Cutting Them Short
Photo: Xerostomus, CC BY-SA 4.0, via Wikimedia Commons
Somewhere between my second and third project, I internalized a rule I never consciously agreed to: keep it under three-thirty, hook by thirty seconds, out before anyone gets bored. I didn't read it in a contract. Nobody sat me down and said it plainly. It just seeped in — from the industry conversations I half-listened to, from watching which songs got pushed on playlists, from the quiet anxiety of seeing a track's average listening duration in my streaming dashboard and doing the math on how early people were bailing.
I was writing songs engineered for survival in an attention economy. And for a while, I told myself that was just smart.
The Invisible Editor in the Room
The thing about platform conditioning is that it doesn't feel like a cage while you're inside it. It feels like discipline. You trim a verse here, cut a bridge there, decide that the emotional resolution you wanted to build toward isn't "essential" — and you call it editing. You call it respecting your audience's time.
But there's a version of respecting your audience that's actually just fearing them. And I was deep in that version.
I started noticing it when I'd sit down to write something that genuinely moved me — a memory, a complicated feeling, something that didn't resolve neatly — and I'd immediately start compressing it. Not because the song needed compression, but because I was pre-emptively apologizing for taking up space. I was writing songs the way you talk when you're not sure you deserve to be heard: fast, efficient, and already halfway out the door.
The music suffered for it. Not obviously — some of those tracks performed fine. But they didn't stay with anyone, including me. A week after release, I'd listen back and feel almost nothing. They were competent little objects. Polished. Forgettable.
What Happens When You Let a Song Sprawl
The shift started with a song I almost didn't finish. I was writing about something personal — a relationship that ended slowly, the kind that doesn't have a clean moment of rupture, just a long, quiet unraveling. Every time I tried to fit it into a conventional structure, it lied. The shape of the song kept contradicting the shape of the experience.
So for the first time in years, I just... let it go where it needed to go.
The song ended up around five and a half minutes. There's a section in the middle that doesn't have a traditional hook — it's more like a conversation with myself, melodically loose, lyrically dense. When I played it for a few people I trusted, nobody told me to cut it. What they said instead surprised me: that middle part is the whole reason the ending lands.
That's when I understood what I'd been sacrificing. I'd been cutting the very tissue that made the payoff feel earned. I was handing people a conclusion without the journey that gives it weight.
The Myth We Agreed To Without Voting
The three-minute song isn't some ancient, sacred truth. It's a byproduct of radio formatting that dates back to the technical limitations of early vinyl singles. A 7-inch record at 45 RPM could only hold so much. That was a hardware constraint, not an artistic one — and yet it calcified into an unspoken law that outlived the technology that created it.
Streaming was supposed to liberate us from that. And in some ways it did — there's no physical limit on song length now, no radio program director deciding what fits the hour. But what streaming introduced instead was a different kind of pressure: algorithmic performance metrics, skip rates, completion percentages. The cage got rebuilt out of data instead of vinyl.
I'm not saying every song needs to be an epic. Length for its own sake is just self-indulgence with a runtime. But there's a meaningful difference between a song that's short because it's complete and a song that's short because the writer was scared to find out what came next.
Learning to Trust the Listener
One thing I had to genuinely reckon with was my own condescension. Because underneath the fear of losing listeners was an assumption that they couldn't handle complexity — that the moment something required patience, they'd be gone.
That assumption is wrong, and honestly, it's a little insulting.
Listeners who find music that matters to them will sit with it. They'll replay it. They'll let it play in the background of their whole Tuesday and then wake up Wednesday with the bridge in their head and not know why. The songs that have done that for me personally — the ones I return to years later, the ones that feel like they know something about me — none of them were three minutes and out. They were the ones that took their time. They were the ones that trusted me to stay.
I wanted to make music like that. I just had to stop writing music designed to avoid being skipped.
What Changed in the Work
Since I made this decision — to let songs be as long as they actually need to be — a few things shifted in how I write.
First, I stopped treating the hook as an emergency exit. It doesn't have to appear before the listener gets restless. It can arrive when the song is ready for it, and it hits harder when it does.
Second, I started writing bridges that actually go somewhere. Not just a key change to signal we're almost done, but a real departure — a place where the song questions itself, or admits something it hadn't admitted yet.
Third, and maybe most importantly, I started finishing songs I would have previously abandoned. Because I wasn't constantly asking is this too long — I was asking is this true. Those are very different questions, and only one of them leads somewhere worth going.
The songs I've written since making this shift are the ones I'm most proud of. They're not all long. Some of them are actually quite short, because that's what they needed. But they're not short because I was afraid. And that difference — between brevity as intention and brevity as apology — is everything.
I'm done writing songs designed to be forgotten. I'd rather make one thing that stays.