Leverage and intervention

Constraints

Limitations that shape behaviour - sometimes adding one creates better outcomes than removing one

Also known as: Boundaries, Limiting factors, Enabling constraints

THE IDEA

The fence that sets you free

Our instinct with constraints is to remove them. If something is limiting us, get rid of it. More resources, more time, more freedom, more options - surely that’s always better?

Often it’s not. Constraints don’t just limit behaviour - they shape it. Remove a constraint and you don’t always get freedom. Sometimes you get chaos, paralysis, or drift. A river without banks is a swamp. A conversation without a question is a ramble. A project without a deadline is a hobby.

The idea of an enabling constraint flips the usual assumption. Some constraints don’t restrict what’s possible - they focus it. They narrow the search space, clarify priorities, force creativity, and make decisions easier by taking options off the table. The sonnet form doesn’t limit what a poet can say. It concentrates how they say it. A tight budget doesn’t prevent good design. It prevents indulgent design - which is often the same thing as bad design.

IN PRACTICE

Less room, more life

Twitter’s original 140-character limit was an arbitrary technical constraint based on SMS message length. It turned out to be the platform’s defining feature. The limit forced a particular kind of writing - compressed, punchy, immediate. When the limit was doubled to 280 characters, the quality of the average tweet arguably declined. The constraint had been doing creative work that nobody appreciated until it loosened.

A theatre company has a budget for one set, five actors, and no scene changes. The constraints sound crippling. But the production becomes inventive in ways a well-funded one never would - actors doubling roles, a single table becoming every location, the audience’s imagination doing the heavy lifting. The constraints didn’t reduce what the show could be. They redirected the creative energy from spectacle to storytelling.

A product team has twelve months and unlimited scope. Progress is slow - every feature is possible, so every feature gets debated. A new leader arrives and says: “Ship something in six weeks. Only the three features that matter most.” Productivity triples. Not because people worked harder, but because the constraint eliminated the most expensive activity in the system: deciding what to work on. The bottleneck wasn’t capacity. It was the absence of a forcing function.

WORKING WITH THIS

Choosing your constraints

When a system is underperforming, the reflex is to ask “what’s in the way?” Sometimes the better question is “what’s missing that would force better decisions?”

Before removing a constraint, ask what it’s currently doing. What behaviour does it shape? What decisions does it simplify? What would happen if it disappeared - would people do the right thing more easily, or would they lose the structure that was guiding them there?

And when designing interventions, consider adding constraints rather than removing them. A time limit on discussions. A cap on options before a decision. A rule that forces the team to talk to users before building anything. A budget ceiling that demands prioritisation. These feel restrictive in the moment, but they do the work of focusing attention, which is the scarcest resource in any complex system. The art is choosing constraints that align with your goals - ones that make the desired behaviour easier and the undesired behaviour harder, without creating so much rigidity that the system can’t adapt.

THE INSIGHT

The line to remember

The most powerful constraints aren’t the ones that stop you doing things. They’re the ones that stop you doing the wrong things, so you have no choice but to do the right ones.

RECOGNITION

When this is in play

You’re thinking about constraints when a team with unlimited options can’t make progress. When removing a restriction makes things worse, not better. When the tightest brief produces the most creative work. When someone says “we don’t have enough X” and the real issue isn’t the shortage but the absence of prioritisation that the shortage would force. When a system performs better under pressure than in comfort - that’s a constraint doing useful work.

design structure creativity intervention