Why Small Teams Win

I’ve worked in teams of three and teams of thirty. The small ones are almost always more fun — and more productive.

That’s not a coincidence. There’s something structurally different about how small teams operate, and it goes beyond just having fewer meetings (though that certainly helps).

Less coordination, more building

Every person you add to a team increases the number of communication channels exponentially. With three people, you have three channels. With ten, you have forty-five. The overhead is real, and it eats into the time you spend actually making things.

Small teams don’t need standups to know what everyone’s working on. They don’t need Jira boards with seventeen columns. They talk, they build, they ship.

Ownership changes everything

On a small team, there’s nowhere to hide — and that’s a good thing. Everyone owns their work. Everyone sees the impact of their decisions. That ownership creates a level of care that’s hard to manufacture in larger organisations.

When you know that the thing you’re building is going to be used, and that you’re going to be the one maintaining it, you build it differently. You build it better.

The right kind of constraint

Small teams force you to make choices. You can’t do everything, so you have to decide what actually matters. That constraint is a gift — it cuts through the noise and focuses you on the work that moves the needle.

I’ve seen small teams outship organisations ten times their size, simply because they were clear about what they were building and why.

That’s the kind of environment I love working in, and the kind of team I love working with.