The Laws and Razors That Rule Everything Around Me

Some patterns keep showing up in life and at work. You see them in how teams communicate, how projects slip, how metrics get gamed, and how decisions stall. These patterns are often captured in “laws” and “razors” that people reference in passing without always naming them.

Knowing them by name doesn’t actually fix anything on its own, but it does give us a lens for understanding why things behave the way they do, and might even help prevent the emergence of future pathologies.

Here are a set I keep running into again and again, grouped into a few useful categories:

---

Productivity and Time Management

Parkinson’s Law
Work expands to fill the time allocated to it.
Give a team a week for a task that could be done in two hours and it will usually consume the full week. Deadlines are not neutral; they shape the work.

Hofstadter’s Law
Everything takes longer than you expect, even when you take Hofstadter’s Law into account.
Humans are consistently optimistic about timelines, even after years of evidence to the contrary. (This blog post is an example: I’ve been sitting on this draft for more than a year)

Pareto Principle (80/20 Rule)
Roughly 80 percent of outcomes come from 20 percent of inputs.
A small number of customers, features, or decisions usually drive most of the impact. The hard part is admitting which 20 percent actually matters.

Brooks’s Law
Adding more people to a late software project makes it later.
New people need onboarding. Communication paths multiply. Coordination costs spike. You lose time before you gain any.

Jevons Paradox
When something becomes more efficient, total consumption often increases instead of decreasing.
Make a process faster or cheaper and people will use it more. That new productivity tool you rolled out may end up consuming more total team time than the thing it replaced.

---

Communication and Team Dynamics

Conway’s Law
Your organization’s structure shows up in your systems.
If your teams are siloed, your architecture will usually be siloed. If your reporting lines are messy, your APIs will often be messy too.

Brandolini’s Law (Bullshit Asymmetry Principle)
The effort required to refute nonsense is vastly greater than the effort required to produce it.
A thoughtless ten-second comment can cost hours of cleanup in meetings, Slack, or documents.

Hanlon’s Razor
Never attribute to malice what can be adequately explained by incompetence.
Most painful situations at work are not the result of secret agendas. They are the result of unclear ownership, weak process, or simple mistakes.

Kidlin’s Law
If you can clearly write down the problem, you are halfway to solving it.
A lot of “misalignment” is just people working on different, unspoken definitions of the problem.

Combinatorial Explosion (Coordination Overhead)
Communication complexity grows combinatorially as you add people.
The number of communication paths in a group is roughly n(n − 1) / 2. Each new person increases the number of potential conversations and sync points. Larger teams often move slower, not faster, because they spend more time coordinating and less time executing.

---

Economics and Systems Thinking

Cantillon Effect
New money entering a system benefits those closest to the source first.
The people and teams closest to decision makers and resource allocation tend to see the upside earliest. Distance from the “center” has a real cost.

Goodhart’s Law
When a measure becomes a target, it stops being a good measure.
Turn a metric into a KPI with incentives attached and you will get people optimizing for the number, not the underlying outcome.

Metcalfe’s Law
The value of a network grows roughly with the square of the number of participants.
More users make tools like Slack, LinkedIn, or a partner ecosystem more valuable. At the same time, noise, complexity, and coordination challenges also grow.

Hawthorne Effect
People change their behavior when they know they are being observed.
Performance review season, leadership “visibility,” or big-bet projects often come with a temporary productivity spike that is more about observation than sustainable change.

Falkland’s Law
If you do not have to make a decision, then do not make a decision.
There is value in waiting when the cost of delay is low and more information is likely to arrive. Immediate decisions are not inherently better decisions.

---

Decision Making and Complexity

Hicks’s Law
Decision time increases with the number of choices.
If you want faster, higher-quality decisions, reduce the number of options and present clearer trade-offs. Infinite menus produce infinite indecision.

Gilbert’s Law
Big problems often arise from people trying to avoid small problems.
Dodging minor discomfort now (a hard conversation, a small refactor, an early course correction) is a reliable way to create major pain later.

Sagan’s Standard
Extraordinary claims require extraordinary evidence.
If you are proposing something that sounds transformational, you should bring data, not just adjectives.

---

These laws and razors don’t govern the world, they’re a form of pattern matching shortcut. They provide a shared vocabulary for patterns you’ll see over and over again in teams, systems, and organizations.

Once you see them, they’re hard to unsee.