The Scarcity Trap
your problem may not be a prioritization problem
\Why do so many teams treat every release like it might be their last?
Look for products that ship infrequently and you’ll see it everywhere. Features get packed in because the next release feels far away. Cleanup gets deferred because there’s no room for it now. Conversations with stakeholders turn into data dumps because who knows when the next one will be. Every interaction carries the full weight of everything that’s been saved up since the last one. It’s an exhausting way to operate, and it’s almost impossible to see from the inside.
I saw this up close on one of my last teams at Microsoft, less than ten years ago. Our front end would “ship” every week, and every week teams would come to me demanding that we make some exceptions to get their feature out now. Even though the next train was leaving the station in seven days, it wasn’t enough - they rushed things and made poor decisions because they thought customers needed their shiny new thing now. Then the week-long cycle would reset and they’d do it all again. I’ve seen this pattern over and over in software teams, in relationships, and in myself.
Nobody on that team thought of themselves as making bad decisions. They were doing exactly what the system incentivized. When the next release feels even a week far away, you maximize the current one. While it feels like dysfunction, it’s not. It’s a completely rational response to scarcity.
What Scarcity Does to Decision Making
The psychologists Sendhil Mullainathan and Eldar Shafir wrote about scarcity as a cognitive pattern. When any resource feels scarce, whether money, time, or opportunity, it captures mental bandwidth in ways that distort decision making. You focus intensely on the scarce thing and neglect everything else. You maximize instead of flow. You pack instead of prioritize. The resource doesn’t have to be a release. It can be time, access, proximity, or any interaction that feels too rare and too precious to waste.
In software, the scarce resource is usually the release itself. Or the stakeholder meeting. Or the planning session. Or access to the team that owns the dependency you need. Whatever it is, when it feels rare and precious, people stop making good decisions about it and start making desperate ones.
The irony is that the maximizing instinct makes everything worse. Bigger releases are harder to ship, harder to test, and harder to recover from when something goes wrong. Packed stakeholder meetings produce less alignment than focused ones. Planning sessions that try to resolve everything resolve nothing well. The attempt to make the most of a scarce opportunity consistently produces the opposite of what people intend.
This pattern shows up at every level of the organization. Teams that meet infrequently pack their meetings. Teams with rare access to leadership pack every conversation. Teams that don’t integrate continuously pack their branches until integration becomes a crisis. The scarcity of the interaction creates the dysfunction, not the content of it.
Abundance
The fix for most software teams is to change the frequency.
I remember walking an executive who came from gaming through something most SaaS companies already know. He was talking about shipping “regularly”, “even as fast as weekly”.
I told him that I’d rather ship ten times a day than once a week. At first, he didn’t understand. Later, when I ended up working for this exec, when we were shipping dozens to hundreds of times a day, he understood completely. Releasing new functionality stopped being an event and became a rhythm, and he watched it happen in real time. The same thing happens in any relationship where scarcity gets replaced by trust in continuity.
Abundance changes behavior without changing people.
Continuous delivery works because it dissolves the scarcity mindset entirely. When releases are cheap and regular, no single release needs to be everything. Teams stop maximizing and start flowing. The things that got crowded out, the cleanup, the small improvements, and the conversations that didn’t feel urgent enough to fight for space in the last release, suddenly have room to breathe.
The same logic applies to stakeholder communication. A team I worked with had quarterly business reviews that ran three hours and left everyone exhausted and misaligned. When we moved to monthly thirty minute check-ins, the dynamic changed completely. Stakeholders stopped treating every meeting like a deposition. The team stopped preparing decks that tried to answer every possible question in advance. Conversations got shorter and more useful because nobody was trying to make them carry ten weeks of accumulated tension.
Your Team
Scarcity thinking is hard to see when you’re deep in it. Packing a release feels correct. Preparing thoroughly for a stakeholder meeting feels professional. Deferring cleanup until after the release feels pragmatic.
If your team treats releases like precious and finite events, it’s probably not a prioritization problem. It’s why releases feel precious and finite in the first place. If your planning sessions try to resolve everything, it may not be because your meetings don’t have agendas. It’s why access to planning feels scarce enough that people try to resolve everything while they have the chance.
The scarcity is structural. It was designed in, sometimes deliberately, more often by accident, and it can be designed out, if you’re paying close enough attention.
What feelings of scarcity on your team are leading to bad decisions while trying to maximize? The answer will tell you exactly where to look.