12 Rules you wished you knew sooner

Watch this on YouTube or Listen on Spotify Podcast

1. PARKINSON'S LAW

Work expands to fill the time available for its completion.
Give yourself a week to write a report — it takes a week. Every single day of it.

Give yourself two hours — somehow, it also takes exactly two hours.

The task doesn't get bigger. Your deadline just gets looser.
And here's the uncomfortable truth: most of us unconsciously set soft deadlines so we have room to procrastinate comfortably.

The fix is brutal simplicity. Cut the timeline in half. See what actually needs to happen versus what you were filling time with.

Urgency is a feature, not a bug. Build it in deliberately.

2. HOFSTADTER'S LAW

Everything takes longer than you expect. Even when you account for Hofstadter's Law.

It's recursive — you build in buffer time, and you still run over.
Software projects. Home renovations. Learning a new skill. Moving to a new country.

You think: three months. It's nine.
The fix isn't better estimation — humans are structurally bad at this and always will be.

The fix is building systems that absorb the delay. Modular plans. Early milestones. Room to fail on the small things without the whole thing collapsing.

Plan for late. Build for early. And never promise a date you actually care about.

3. HANLON'S RAZOR

Never attribute to malice what can be explained by stupidity.

Or laziness. Or distraction. Or burnout. Or just a bad Tuesday.

Most people aren't plotting against you. They're barely thinking about you at all.

The colleague who didn't reply to your email isn't your enemy — they have 200 unread messages and a meeting in five minutes.

The client who gave you vague feedback isn't trying to waste your time — they don't know what they want yet.

Before you assume someone's your enemy, consider they might just be overwhelmed, underprepared, or having a terrible week.

It saves you a lot of unnecessary wars — and a lot of misplaced energy.

4. THE PARETO PRINCIPLE

80% of your results come from 20% of your efforts.
80% of your revenue from 20% of your clients.
80% of your problems from 20% of your decisions.
80% of the value in any meeting comes from 20% of the conversation.

This isn't a rough estimate. It shows up everywhere, in every industry, at every scale.

The question isn't how to work more hours.

It's which 20% of your actions actually move the needle — and having the discipline to do only that.

Most people know this principle. Almost nobody actually applies it.

Start by listing everything you do in a week. Then ask: which three things actually matter?

5. THE PETER PRINCIPLE

In every hierarchy, people rise to their level of incompetence.
You're good at your job. So you get promoted into a different job.
You're good at that too. Another promotion. Into yet another job.
Until finally — you land somewhere you're not good at. And there you stay.

Organizations are full of people who were excellent — exactly one level below where they currently sit.

The brilliant engineer becomes a mediocre manager. The great salesperson becomes a terrible sales director.

The lesson isn't to avoid ambition. It's to distinguish between what you're good at and what you actually want to become.

Because those two things are not always the same.

6. HICK'S LAW

The more options you have, the longer it takes to decide.
Double the choices — decision time goes up logarithmically. Not linearly. Logarithmically.

This is why great restaurant menus are short. Why the best products have one button. Why the best strategies have one priority.

Every option you add to a decision costs someone cognitive energy — energy they could spend on actually doing something.

We think more choice is better. It isn't. More choice is paralysis with extra steps.

The best designers, leaders, and product builders understand this intuitively.
Simplify ruthlessly. The best decision architecture gives people fewer choices, not more.

7. GOODHART'S LAW

When a measure becomes a target, it ceases to be a good measure.

You start tracking something to understand it. Then you start optimizing for it. And then the metric detaches completely from the thing it was supposed to represent.

Schools teach to the test — and stop teaching students to think.
Companies hit the quarterly revenue number — and quietly destroy long-term value doing it.

Social media optimizes for engagement — and discovers that outrage drives more clicks than truth.

Metrics are maps. They are not the territory.

The moment your team starts gaming the number instead of solving the problem — the number has failed you.

Chase the outcome. Build systems around the outcome. Let the metrics follow.

8. THE DUNNING-KRUGER EFFECT

The less you know about something, the more confident you are.

The more you know, the more you realize how much you still don't understand.
It's a curve. Beginners peak in confidence in week two — they think they've figured it out.

Then reality hits. Complexity reveals itself. Confidence collapses.

And the people who push through that collapse — who sit with the discomfort of not knowing — eventually reach genuine competence. Quieter. More accurate. Less loud about it.

The most dangerous people in any room are the ones who just learned something last week and haven't discovered what they don't know yet.

If you've never seriously doubted yourself in your field — you probably haven't gone deep enough.

9. OCCAM'S RAZOR

The simplest explanation is usually correct.

Not always. But usually.
Before you build a complex theory with seventeen variables — ask if a simpler one with three fits the same facts.

Before you create an elaborate system with fifteen steps — ask if a five-step version produces the same result.

We overcomplicate because complexity feels like intelligence. It usually isn't.
The smartest people I've met are obsessively simple in how they think and communicate.

They make complex things look easy — not by dumbing them down, but by understanding them deeply enough to strip away everything unnecessary.
Complexity is the default. Simplicity is the achievement.

10. CHESTERTON'S FENCE

Don't remove a fence until you understand why it was built.

Someone put it there for a reason. Maybe a good one. Maybe an outdated one.
But if you don't know why it exists — you're not qualified to decide whether it should.

This applies to business processes that seem inefficient. To social norms that seem arbitrary. To regulations that seem excessive.

Before you disrupt something — understand it first.

The most expensive mistakes in business happen when someone smart walks in, sees something that looks stupid, removes it — and discovers six months later exactly why it was there.

Reform before you demolish. Understand before you optimize.
The fence might be protecting something you can't see yet.

11. BROOKS'S LAW

Adding people to a late project makes it later.

It feels wrong. More hands should mean more speed. It doesn't.
New people need onboarding. They ask questions. They make mistakes while they're learning context.

And the people who were already on the project — the ones who actually understand what's happening — have to stop and teach them.

So the project slows down before it speeds up. And it often never fully recovers.

Brooks called this the mythical man-month — the idea that people and time are interchangeable in software. They're not.

The fix for a late project isn't more hands.

It's fewer moving parts. Clearer ownership. Honest conversations about what's actually possible.

And a willingness to cut scope rather than add people.

12. METCALFE'S LAW

(Why adding one person to a team adds ten problems)

There's a formula that every manager should tattoo on their hand before they hire anyone.

It's called Metcalfe's Law. And it goes like this:
Every time you add one person to a team, the number of communication lines doesn't increase by one. It multiplies.
Two people: one connection between them. Simple.
Five people: ten connections. Manageable.
Ten people: forty-five connections.
Fifty people: over twelve hundred.
Same formula: n times n minus one, divided by two.

Every one of those connections is a potential misunderstanding. A meeting. A status update. A "just checking in" message that interrupts someone's deep work.

This is why small teams ship fast and big teams write documents about shipping.
This is why your startup moved faster with six people than your corporation does with six hundred.

It's not motivation. It's not culture. It's math.
Before you scale your team — ask whether you're scaling your communication problem by an order of magnitude.

Sometimes the answer to moving faster is not more people.
It's fewer, better, with clearer ownership and less to coordinate.