Why constraints make better products, not worse ones.

Constraints force decisions that unlimited resources let you avoid — and avoided decisions are usually where mediocre products come from. A tight deadline, a small team, or a narrow budget isn’t the enemy of good product work. It’s frequently the reason good product work happens at all, because it removes the option of deferring the decisions that actually define a product.

What unlimited resources actually remove

With no real constraint, every feature seems worth including, every audience seems worth serving, and every idea seems worth exploring at once. Nothing forces the question that matters most: what does this product refuse to do? Without that question being answered, forced by a real limit, a product tends to expand to fill whatever resources are available to it — not because expansion is the right call, but because nothing stopped it.

This is a genuinely counterintuitive idea in a culture that treats more resources as an unambiguous advantage. More resources are an advantage for execution. They’re often a disadvantage for clarity, because clarity comes from having to choose, and choosing only becomes unavoidable once something real is scarce.

Constraints force prioritization you can’t fake

A real constraint — two weeks, three people, one platform — forces a answer to that question immediately. You can’t build everything, so you’re forced to decide what actually matters, which is the single hardest and most valuable decision in product work. Every other decision downstream of that one gets easier once it’s been made honestly.

Faking prioritization under unlimited resources is easy — you can claim something is the top priority while still finding time and budget for everything else. A real constraint doesn’t allow that kind of comfortable ambiguity. Something genuinely has to be cut, and the cutting is where the actual thinking happens.

Where this shows up in practice

The products people describe as “focused” or “obvious to use” are rarely the result of unlimited resources. They’re usually the result of someone accepting a real constraint early and building a sharp answer inside it instead of a vague one outside it. Teams given more time and budget than they need frequently produce something less coherent than teams working under real pressure, not because pressure makes people smarter, but because pressure removes the option of postponing hard calls.

This doesn’t mean constraints should be imposed artificially for their own sake. It means real constraints, when they exist, are worth treating as useful information rather than pure obstacles to be resourced away as quickly as possible.

Common questions

Isn’t it better to have more resources whenever possible? More resources help with execution speed and quality once direction is clear. They don’t reliably help with finding that direction in the first place, which is where constraints tend to add real value.

Should teams deliberately impose artificial constraints when real ones don’t exist? It can work as a forcing function, but artificial constraints are weaker than real ones — teams often quietly relax a constraint they know isn’t truly binding, which defeats the purpose.

What’s the risk of too much constraint rather than too little? Real constraints can occasionally prevent a product from doing anything meaningful at all. The goal isn’t maximum constraint — it’s enough constraint to force genuine prioritization without making the underlying goal impossible.

Takeaway: if a product feels unfocused, the problem is rarely a lack of resources — it’s usually a lack of a real constraint.