Day 283 of the Daily · Product Management

Brooks’s Law

5 min read · 4 principles · apply it by lunch

The project is six weeks late and the obvious answer is three more engineers. That answer has a name, and it’s a law.

The question

Think about the last project that ran late on you: when the extra people arrived, who stopped doing their own work in order to bring them up to speed, how many weeks went by before the newcomers were producing more than they were consuming, and did anyone put either of those two costs on paper before the decision got made?

The idea

Fred Brooks managed the development of IBM’s OS/360, one of the largest software projects anybody had attempted, and then spent decades explaining what it had cost him — most of them at the University of North Carolina at Chapel Hill, where he founded the computer science department in 1964. The Mythical Man-Month, published in 1975, is that explanation, and the title carries the argument. A man-month is a unit that assumes people and time trade against each other freely, and they only do that when a task can be split among workers who never need to speak. Brooks’s examples of the genuinely splittable are reaping wheat and picking cotton. Software isn’t either of them. From that he drew the law: ‘adding manpower to a late software project makes it later.’ The added burden, he wrote, has two parts. Training: someone already fluent has to teach the newcomers, and they can’t do their own work while doing it. Intercommunication: if every part of the job has to stay consistent with every other, the coordination between n people runs to n(n-1)/2 channels. Four people carry six of them. Ten carry forty-five. So three more bodies on a team of seven doesn’t buy you three-sevenths more; it more than doubles the conversations that have to happen for the thing to hold together.

In the Daily · 4 principles and a template

Brooks’s Law is Day 283 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 293 · Product Management

The Five-User Test

Have you ever sat behind someone who’d never seen your product, handed them a real task and then stayed silent while they failed at it — or is everything you believe about how the thing gets used assembled entirely from your own hands on your own keyboard?

See the framework →
Day 302 · Product Management

Affordances and Signifiers

Somewhere in your product sits a control that needed a tooltip, an onboarding step and a help article wrapped around it before anybody could work out what it did — so if all three were deleted tomorrow and nothing else changed, how many of your customers would still know where to click? The explaining is the part you can count. The control underneath it is the part somebody would have to fix.

See the framework →
Day 311 · Product Management

Which Side to Subsidise

If you run anything that needs two groups to turn up before either of them gets any value — buyers and sellers, readers and writers, players and developers — can you name which of the two you’re deliberately underpricing, say what the other side is paying extra for the privilege of reaching them, and tell me whether either of those numbers was ever a decision rather than something you inherited from whichever side signed up first?

See the framework →
Day 321 · Product Management

The Persona Spectrum

Take the last hundred people who started with your product and gave up inside a week: you’ve filed most of them under not interested, but how many were holding a baby, standing in a loud room, squinting at a screen in bright sun or working one-handed on a train — and could anyone on your team tell those two groups apart from the data you keep?

See the framework →