How Many Songs Should You Work On at Once?
Published · updated · by Loopin
There's no universally correct number, but there is a real, predictable tradeoff between focusing deeply on one song and losing momentum, versus juggling several and never finishing any of them.
The case for working on one song at a time
Deep focus on a single song tends to get you to a finished result faster, since you're not constantly re-loading context every time you switch projects. If you're someone who finishes things reliably, single-tasking a song through to completion is often the most efficient path.
The risk is getting stuck — if a song hits a wall and you have nothing else to work on, momentum stalls entirely until you solve that specific problem.
The case for two or three in rotation
Having a small number of songs in progress means you can switch to a different one when you're stuck, rather than staring at the same problem repeatedly. Distance from a song, even briefly, often reveals a fix that wasn't visible while staring directly at it.
Two or three tends to be the practical sweet spot for most people — enough to have somewhere to go when stuck, not so many that none of them get real attention.
Where it breaks down: too many at once
Beyond four or five simultaneous projects, most people start losing track of what each song actually needs, and total finished output tends to drop even though total time invested stays the same or increases. This is when a graveyard of half-finished ideas starts accumulating.
If you notice you have many songs at a similar, stalled stage of completion, that's a sign to intentionally narrow focus rather than start anything new.
Match the number to where you are in the process
Early-stage idea generation benefits from having several loose ideas around, since you're not yet deep into any one of them. As a song moves toward finishing — final mix, final lyrics, mastering — narrowing focus to one or two at that stage usually produces a better, faster result.
The right number isn't fixed — it can shift depending on whether you're mostly generating ideas or mostly finishing them at any given time.
Use a finishing rule to force resolution
If a song has been sitting untouched for a long period, decide deliberately whether it's still active or should be set aside — rather than letting it quietly occupy mental space as "in progress" indefinitely. An explicit decision, even to pause something, is more useful than an ambiguous stall.
This keeps your active project count honest and prevents the slow accumulation of songs that are technically "in progress" but not actually receiving any attention.
Frequently asked questions
Is it better to work on one song at a time or several?
It depends on your working style, but two or three tends to be a practical sweet spot -- enough to switch to when stuck on one, not so many that none get real attention.
How many songs in progress is too many?
Beyond four or five simultaneous projects, most people start losing track of what each song needs, and finished output tends to drop even as time invested stays the same or increases.
Should I work on more songs when starting ideas versus finishing them?
Yes, it's reasonable to shift. Early idea generation benefits from having several loose ideas around, while finishing stages -- final mix, lyrics, mastering -- usually go better with narrowed focus on one or two.