the difference between a group of good people and a squad that delivers is the same as between talented musicians and a band. The musicians can be brilliant alone — but if each plays a different song, the result is noise. A squad doesn't exist to write elegant code. It exists to move a business number.

When a director asks for “one more dev,” the problem is almost never a shortage of hands. It's a shortage of clarity about what to move and who answers for it. More headcount on a poorly defined problem just speeds up delivering the wrong thing.

§ 01 / ThesisOutcome, not output.

A traditional team gets requirements and ships features. A strategic squad gets problems and ships solutions. It sounds subtle; it's fundamental. Ask for “a login system” and you get a login system. Ask to “reduce friction in conversion” and you might get social login, leaner onboarding — or the removal of signup altogether.

A good squad questions the problem before jumping to the solution. Often the best technical delivery is to build nothing new, and instead remove something that already exists and gets in the way.

§ 02 / CompositionBeyond devs and QAs.

A team of only developers and QAs is a leftover from when technology was a support department, not the core of the business. The mistake isn't having devs and QAs — it's having only that. A squad that delivers value needs:

  • A product owner who decides, prioritizes ruthlessly, and answers for the result — not a translator of requirements into tasks.
  • Someone who knows the domain. In healthcare, someone from healthcare. In finance, someone from finance. That prevents building something technically perfect and practically useless.
  • Embedded data reading, to decide with numbers and not gut feel — questioning the metric, not just reporting it.

§ 02 / SizeSmall for effectiveness, not for economy.

With five people there are ten communication channels. With ten, forty-five. With twenty, one hundred and ninety. Complexity grows on a curve; human capacity doesn't. A good squad is small enough that everyone knows what each person is doing, and complete enough to have the competence it needs. Usually five to nine.

A squad isn't a fungible resource you move like a chess piece. It's an organism with accumulated context — disband and rebuild it and you reset months of delivery.

§ 03 / MeasurementValue is a business number that changed.

The industry is obsessed with activity metrics: story points, lines, commits. All of it measures motion, not progress. Real value is a measurable change attributable to the squad: not “we shipped the recommendation system,” but “recommendations raised engagement by X.” Without that explicit bridge between technical work and result, the squad can't justify its own existence.

Noûs principle
Every squad we set up starts with an agreed business KPI — and an owner. If no one on the client side can say which number we'll move and who answers for it, we don't form the team. Building a squad on a vague problem is selling speed in the wrong direction.

§ 04 / ClosingStability pays compound interest.

Most companies disband squads before they mature, resetting the cycle constantly. It's planting a tree and pulling it up before the fruit. A squad that works together over time develops shared language, trust, and a pace no new team has. Leadership's job isn't to manage the squad — it's to create the conditions for it to thrive: rich context, stable priorities, and the discipline not to micromanage.

Don't count heads. Count clarity of purpose and ownership. The rest is productivity theater.

end  ·  field note #49  ·  noûs / may 26