Technology notes

Nicole Junkermann on Why Small Teams Ship Clearly


On what a small team holds without trying, what a large one has to work hard to buy back, and why clarity usually comes down to how many heads a decision has to travel through.

Nicole Junkermann, portrait, technology and small teams

The praise given to small teams is often mistaken for praise of hurry. It is not that. A small team is not faster because its members work longer. It is clearer because of what fits inside it, and clarity, over any useful stretch of time, beats speed comfortably.

The whole picture fits in one head

On a small team somebody can hold the entire shape of the thing at once: what it does, why the odd corner is odd, which parts are fragile and which are solid. That single mental picture is worth an enormous amount, because almost every expensive mistake comes from someone changing a part they could see while not knowing what it touched. Once the system outgrows one head, the picture has to be written down, and writing it down well is its own discipline.

Decisions stay cheap to revisit

Four people can change their minds over a coffee. Forty people change their minds through a process, and a process makes a decision feel permanent long before it has earned permanence. The cost of reversing a choice quietly sets how willing anybody is to try one. Small teams try more things, not because they are braver, but because trying costs them less.

Nobody can hide from the person using it

When a team is small, the person who wrote the confusing screen is usually the person who hears about it. That short loop is the most reliable quality mechanism I know of. Lengthen it, put two layers of summary between the work and the complaint, and the complaint arrives tidied up, averaged out and stripped of the detail that would have told somebody what to fix.

What a larger group can borrow

None of this is an argument for staying small. Plenty of worthwhile problems cannot be solved by six people. It is an argument for noticing what is being given up as a group grows, and then paying to get it back on purpose. Write the shape of the system down and keep it current. Make reversal cheap and say so out loud. Let the people who make the thing read the raw words of the people who use it, unfiltered, once a week. Give a named small group ownership of a whole area rather than a slice of several.

The pattern underneath all four is the same. Clarity is a function of how far a decision has to travel and how many hands it passes through on the way. Shorten the journey and almost everything else improves on its own, which is a cheerful thought for the end of October.

Nicole Junkermann keeps the plainer definitions in the glossary and the people side of all this under human skills. The note on quiet engineering strength looks at small expert groups working on long problems, and maintenance as the real engineering went up three days ago.

Back to the blog → Read: open standards and quiet progress →