Fifteen principles that explain why your project is late, your inbox is full, your manager is useless, and nothing ever goes according to plan.
Physics has its laws. Economics has its models. And the messy, human world of work, organizations, and everyday life has something perhaps more useful: a set of unofficial laws — observed by soldiers, engineers, economists, and programmers — that predict failure, inefficiency, and chaos with startling accuracy. Understanding them won’t make you immune. But it will stop you from being surprised.
Table of Contents
- Time & Productivity
- Organizations & Management
- Metrics & Decision Making
- Technology & Systems
- Truth & Information
Time & Productivity
Three laws about how we use — and lose — time.
Parkinson’s Law
C. Northcote Parkinson · 1955
“Work expands to fill the time available for its completion.”
Parkinson wrote this in a sardonic essay for The Economist about the British Civil Service, where he noticed that bureaucracies grew inexorably regardless of how much actual work existed. His insight was psychological as much as organizational: given a deadline, people use all of it — polishing, second-guessing, meeting about meetings.
The corollary is productive: shorter, tighter deadlines often produce equivalent or better work. Not because people work harder, but because they make decisions faster and abandon unnecessary refinement.
In the wild: Given two weeks to write a proposal, you’ll spend the first week thinking about it. Given two days, you’ll write it on day one and tighten it on day two. The proposals are roughly equal.
Carlson’s Law
Sune Carlson · 1951
“A task done continuously takes less time than one interrupted repeatedly.”
Swedish management researcher Sune Carlson studied executive behavior for years and found something counterintuitive: managers who appeared busiest were often least productive. The culprit was fragmentation. Every interruption — a call, a knock, a notification — doesn’t just consume its own time. It destroys the concentration required to return to deep work.
Carlson estimated that an interrupted task takes three to four times longer than one completed in a single unbroken session. Open offices, always-on messaging, and meeting culture are Carlson’s Law made structural.
In the wild: You sit down to write a report. By the time you’ve checked Slack, answered two emails, and returned, you’ve forgotten where you were. The report takes all afternoon. Uninterrupted, it would have taken 40 minutes.
Hofstadter’s Law
Douglas Hofstadter · 1979
“It always takes longer than you expect, even when you take into account Hofstadter’s Law.”
Hofstadter included this self-referential observation in his Pulitzer Prize-winning book Gödel, Escher, Bach, and its recursive structure is the whole point. Knowing about the law doesn’t help you escape it. You account for delays, build in buffer time, pad the estimate — and it still runs over. Then you account for that next time, and it runs over again.
The reason is that complex projects contain unknowns that are, by definition, unknown in advance. No amount of pessimism fully captures what you haven’t yet discovered about the problem.
In the wild: Every home renovation ever attempted. You budget for six weeks and $20,000. You finish in four months and $34,000. You knew this might happen. It happened anyway.
Organizations & Management
Four laws about how groups of people succeed — and more often, fail.
The Pareto Principle
Vilfredo Pareto · 1896
“80% of consequences come from 20% of causes.”
Pareto, an Italian economist, noticed that 80% of Italy’s land was owned by 20% of the population. He then looked at his garden and found that 20% of his pea pods contained 80% of the peas. The pattern was everywhere. Business analysts later found it in bug reports, sales pipelines, customer complaints, and wealth distribution.
The principle is not a law of nature — it’s a pattern of imbalance that appears when inputs and outputs are not evenly distributed. Its power lies in focus: find the vital 20% and concentrate there.
In the wild: In most software products, 20% of features are used by 80% of users. The other 80% are maintained, documented, and defended in quarterly reviews.
Conway’s Law
Melvin Conway · 1967
“Organizations design systems that mirror their own communication structure.”
Conway made this observation in a paper about how groups of people build software. If you have four teams working on a compiler, you’ll get a four-pass compiler. The architecture of what you build reflects the architecture of how you’re organized — whether you intend it or not.
This is why tech companies restructure before big platform rewrites. The new system you want requires a new communication structure first. You can’t separate the org chart from the product roadmap.
In the wild: A company with siloed legal, tech, and design departments ships a product where legal, tech, and design feel like three separate products stitched together.
The Peter Principle
Laurence J. Peter · 1969
“In a hierarchy, every employee tends to rise to their level of incompetence.”
Laurence Peter noticed something uncomfortable about how promotions work: they are awarded for performance in the current role, not suitability for the next one. A brilliant engineer becomes a mediocre engineering manager. A great salesperson becomes a poor sales director. The skills that earned the promotion are rarely the skills the new job requires.
The result, Peter argued, is that over time every position in a hierarchy tends to be filled by someone who is not quite capable of doing it — because the competent ones keep getting promoted until they aren’t.
In the wild: Your best teacher gets made head of department and spends their days in budget meetings. The school loses a great teacher and gains an average administrator. Everyone loses.
Brooks’s Law
Fred Brooks · 1975
“Adding manpower to a late software project makes it later.”
Fred Brooks drew on his experience managing IBM’s OS/360 — one of the most complex software projects ever attempted — to formulate this painful truth. When a project falls behind, the instinct is to throw people at it. But new team members need onboarding. Existing members must stop work to train them. Communication channels multiply. Coordination costs soar.
The law applies beyond software. Any complex, interdependent task suffers the same arithmetic. Adding a tenth person to a late project often means nine people spend part of their day explaining things to one new person.
In the wild: The project was supposed to ship in March. In February, the team doubled. It shipped in July. The post-mortem blamed “communication overhead.” Brooks called it in 1975.
Metrics & Decision Making
Two laws about the traps hiding inside measurement and choice.
Goodhart’s Law
Charles Goodhart · 1975
“When a measure becomes a target, it ceases to be a good measure.”
Goodhart was a Bank of England economist who noticed that once the government started using a particular financial indicator as a policy target, banks found ways to game it — making the indicator look good while the underlying reality it was supposed to capture deteriorated. The measure and the thing it measured came apart.
This law now haunts every KPI dashboard, school league table, and performance review in existence. The moment you decide to measure something and reward people for improving it, you’ve given them an incentive to improve the number rather than the thing the number was supposed to represent.
In the wild: A call center measures success by call duration. Agents start hanging up on customers to keep times short. Customer satisfaction collapses. The metric looks great.
Falkland’s Law & Kidlin’s Law
Lord Falkland · Sir Richard Kidlin
“If it is not necessary to make a decision, it is necessary not to make a decision.” — Falkland “If you can write the problem down clearly, you can solve it.” — Kidlin
Falkland’s Law is a plea for stillness in a culture of action. The pressure to decide, to move, to respond — even when doing nothing is the right answer — causes enormous damage. Not every problem requires intervention. Premature decisions close off options that time would have resolved naturally.
Kidlin’s Law is its complement: when a decision is necessary, clarity precedes solution. Most “unsolvable” problems are actually “unclearly stated” problems. Writing forces precision. Precision reveals that the problem is either simpler or different from what you assumed.
Together: Before your next meeting: ask whether a decision is actually needed. If yes, write the problem in one sentence before opening the discussion. Both laws save time.
Technology & Systems
Five laws about how technology grows, spreads, and breaks.
Murphy’s Law
Capt. Edward A. Murphy Jr. · 1949
“Anything that can go wrong, will go wrong.”
Born on an Air Force test site in California, this law emerged when engineer Edward Murphy discovered that a technician had wired every single sensor in an experiment backwards — every possible wrong configuration, achieved perfectly. Murphy’s observation was practical: if there is any way to do something incorrectly, someone will find it.
The deeper truth isn’t pessimism — it’s probability over time. Given enough attempts, low-likelihood failures become near-certainties. Good engineers design for it. They call it “fault tolerance.”
In the wild: You leave early for the airport for the first time in years. The train breaks down. Murphy is not cruel — he is simply patient.
Moore’s Law
Gordon Moore · 1965
“The number of transistors on a chip doubles roughly every two years.”
Intel co-founder Gordon Moore noticed an exponential trend in computing density and predicted it would continue — and it did, for over fifty years. The consequences of sustained doubling are staggering: the iPhone in your pocket is millions of times more powerful than the computers that guided Apollo 11.
Moore’s Law has slowed and may eventually end at physical limits, but it defined the world we live in. It’s also a lesson in how exponential growth is psychologically invisible until it isn’t — then it changes everything at once.
In the wild: The storage capacity of a USB drive that costs $10 today would have required a warehouse-sized mainframe in 1970. And would have cost more than most countries’ GDP.
Metcalfe’s Law
Robert Metcalfe · 1980
“The value of a network is proportional to the square of the number of its users.”
Ethernet inventor Robert Metcalfe observed that a single fax machine is worthless. Two fax machines create one connection and some value. Ten fax machines create 45 possible connections. A million fax machines create an almost incomprehensibly large number of connections — and corresponding value. Growth is not linear; it’s exponential.
Metcalfe’s Law explains why social networks, marketplaces, and communication platforms are winner-take-most businesses. Each new user makes the network more valuable for every existing user, creating a compounding advantage that is nearly impossible for competitors to overcome once it takes hold.
In the wild: WhatsApp is valuable because everyone you know is already on it. A technically superior messaging app with fewer users is, for most people, worth less — regardless of its features.
Gall’s Law
John Gall · 1975
“A complex system that works is invariably found to have evolved from a simple system that worked.”
Gall, a pediatrician and systems theorist, argued that you cannot design a complex working system from scratch. Every attempt to do so produces something that looks complete on paper but fails in practice, because the designers cannot anticipate the full range of real-world interactions. The only path to a working complex system is to start with a working simple system and let it grow.
This is why the internet works and why most enterprise software doesn’t. The internet started as a handful of connected computers. Most enterprise systems were designed as complete solutions from day one.
In the wild: Amazon started by selling books. Google started as a university research project. The systems that now handle billions of transactions daily were not designed to do so — they grew into it.
Zawinski’s Law
Jamie Zawinski · 1990s
“Every program attempts to expand until it can read email. Those programs which cannot so expand are replaced by ones which can.”
Netscape programmer Jamie Zawinski observed this pattern in software with dark humor: applications have an inexorable tendency to accumulate features far beyond their original purpose. A text editor gains a plugin system. The plugin system gains a browser. The browser gains a mail client. Slack, which started as a gaming tool, now contains more features than most operating systems from the 1990s.
The law reflects a real pressure: software that doesn’t grow loses users to software that does. Feature creep isn’t a mistake — it’s a survival strategy. The tragedy is that the thing that made the original software good usually gets buried in the process.
In the wild: Adobe Acrobat began as a simple document viewer. It now includes a PDF editor, e-signature tool, cloud storage, AI assistant, and web forms platform. Reading a PDF requires a 4GB install.
Truth & Information
One law. One uncomfortable truth about the modern information landscape.
Brandolini’s Law
Alberto Brandolini · 2013
“The amount of energy needed to refute nonsense is an order of magnitude greater than that needed to produce it.”
Italian programmer Alberto Brandolini posted this observation on Twitter and immediately made the internet’s most accurate self-description. A single false claim, forwarded in thirty seconds, may require hours of careful sourcing, context, and explanation to debunk — only to be dismissed by people who’ve already moved on to the next false claim.
Brandolini’s Law is why misinformation spreads faster than corrections. It’s why conspiracy theories are sticky and scientific consensus is fragile in public discourse. The asymmetry is not a bug in human nature; it’s a feature that can be exploited.
In the wild: A headline claiming “Scientists say coffee causes cancer” spreads to millions in hours. The actual study — about a specific compound, at extreme doses, in rats — takes a science journalist 800 words to explain. Most readers never see the 800 words.
What to do with all this
These laws aren’t destiny. They’re diagnostics. Parkinson tells you to set tighter deadlines. Carlson tells you to protect your focus. Brooks tells you to resist the headcount reflex. Peter tells you to promote carefully. Goodhart tells you to distrust your own metrics. And Hofstadter tells you that even knowing all of this, you’ll still underestimate the timeline.
Knowing the pattern doesn’t exempt you from it — but it does let you see it coming.
Leave a Reply