Small Team, Big Constraints: How Limits Make Better Games

There is a fantasy that haunts every game studio: if we just had more time, more money and more people, we could build the game of our dreams with nothing left out. It is a comforting story. It is also, in our experience, mostly wrong. Some of the best games ever made came from teams who could not afford to include everything — and were forced into focus because of it.

The myth of the unlimited game

Unlimited resources sound like freedom, but they often produce bloat. With no pressure to choose, every feature survives, every idea gets bolted on, and the result is a game that does a hundred things adequately and nothing memorably. Scope expands to fill the budget available, and clarity is usually the first casualty.

A small team simply cannot work this way. We have to choose. And choosing, it turns out, is most of the job — the constraint is not an obstacle to the design, it is the design.

Why do constraints spark creativity?

Because a blank page is paralysing, and a tight box is a starting point. When you cannot do the obvious expensive thing, you are forced to find a cleverer, cheaper, often more interesting solution.

The history of games is full of this. Tetris is mesmerising with seven shapes. Downwell built an entire identity around a single narrow column. Thomas Was Alone turned coloured rectangles into characters players genuinely cared about, precisely because it could not afford anything fancier and leaned all the way into the limitation. None of these are great despite their constraints. They are great because of them.

Scope is a design decision, not an afterthought

We try to treat scope as a creative choice made early, rather than a panic that arrives near the deadline. Deciding what a game is not is as much a part of the design as deciding what it is.

A game that knows exactly what it is about — and ruthlessly protects that — tends to feel sharper and more confident than one that tried to be everything. Players can feel the difference even if they cannot name it. Focus reads as intention; sprawl reads as indecision.

How do we decide what to cut?

We hold every feature up against the core loop and ask a simple question: does this make the main thing the player does better, or does it just add more stuff? If it strengthens the core, it earns its place. If it is merely cool but pulls focus and eats months, it goes on the list of things we will happily live without.

Cutting hurts every time. You are nearly always cutting something you liked, something that took real work, something you can picture in the trailer. It is also where the game actually gets good, because what remains is everything that mattered most.

The one-feature rule

When we are tempted to add something new late in a project, we make it pay rent. The rule is roughly this: a new feature has to be worth more than the feature it would push out, because our time is finite and something always has to give.

Most ideas do not survive that test, and the game is better for the ones that do not. It keeps the project from quietly doubling in size one reasonable-sounding addition at a time — the way small teams most often run aground.

Why we have made peace with our limits

Being a small studio inside a wider group means we will never out-spend anyone. So we have stopped trying to. Our advantage is not scale — it is the ability to be specific, to make a tightly focused thing with a clear point of view, and to change direction quickly when a prototype tells us we are wrong.

Constraints are not the thing standing between us and the game we want to make. More often than not, they are the reason it will be worth playing at all. We would rather make something small and sharp than something large and vague — and the limits are what keep us honest about the difference.