Team & Delivery Laws for Product Managers

The fastest team in the world can be slowed to a crawl by the structure it sits inside. The laws in this category are about the shape of delivery — why adding engineers to a late project makes it later (Brooks's), why the product reflects the org chart that built it (Conway's), why the 'clean rewrite' is usually neither (Gall's), and why a deadline of three months will get used in full, regardless of whether three weeks would have sufficed (Parkinson's).

They also cover the patterns PMs have to actively fight: the rule whose purpose nobody remembers but nobody should remove (Chesterton's Fence), the hype cycle the whole company is currently inside (Gartner, Amara), and the human coordination ceiling that no amount of Slack can raise (Dunbar).

These laws are what you want in your pocket when you're negotiating a deadline, proposing a reorg, inheriting a legacy product, or watching a team sprint toward a rewrite. Most of them are about knowing what not to do — which is, as always, the hardest part of the job.