← all five

Everything got
slower.

Work that used to take a week takes a quarter. You send the message, you chase the thread, you sit in the meeting about the meeting. And somewhere in the last year or two you started quietly wondering whether the problem is you.

It isn't. Answer four questions and I'll show you exactly what happened to your job — using your numbers, not mine.

Question 1 of 4
Think of a typical project of yours. How many people have to actually do something for it to work?
Not the headcount of your team — the number of humans whose actual effort the thing depends on. Include reviewers, approvers, the one person who owns the config.
10
225
Question 2 of 4
Picture the person you most often need something from. How far up before you share a boss?
Count the levels you'd have to climb before you hit a manager you both report into, however indirectly. Same team is 1. If you genuinely don't know, it's high.
3
same teamthe CEO
Question 3 of 4
How many other things are on your plate right now?
Things you're accountable for that someone would notice you dropping. Be honest; the number is usually worse than the one you'd say in a standup.
6
112+
Question 4 of 4
How often do you start something and find out it wasn't what you thought?
The hidden dependency. The stakeholder nobody mentioned. The "oh, that system doesn't work like that." How much of your work is discovering the work?
Often
rarelyconstantly

Let's start by assuming the best about everyone.

Every one of the people your project depends on is good at their job, wants it to succeed, and shows up 99% of the time. One day in a hundred they're sick, or the thing breaks, or something genuinely more urgent lands. That's it. That's the whole concession to reality.

chance the project lands, with a team of saints

But you have other things on your plate.

So does everyone else. Nobody's slacking — it's that on any given week, the odds that this project is the one that gets your real attention, at the moment it needs it, are no longer 99%. Investing late is the same as not investing.

Each person's reliability on this specific project drops to . A rounding error, per person.

chance it lands now

Now the part nobody counts.

Projects don't just need people to work. They need every pair of people not to seize up — not a fight, just a good-faith disagreement nobody has time to resolve. With people there are such pairs.

Each line is a relationship that has to hold. And the risk on any single one is genuinely tiny — — because you're all adults. But your nearest shared boss is , which means when one does seize up, there's no cheap way to fix it. Escalating that far is a whole political act, so instead it just... sits there.

chance it lands, counting friction

And you don't know how big any of it is.

Every step forward might hide a boulder: a dependency, a disagreement, a system that doesn't work how the docs say. Clearing one costs roughly ten times what the step itself would have. Sometimes clearing it reveals the goal was further away than you thought.

what the work actually costs, versus what you estimated

This is why your estimates are always wrong, and why you feel slow. You are not slow. You are paying a tax that nobody put on the roadmap.

Then it feeds on itself.

Here's the part that turns a bad quarter into a bad year. When a project looks less likely to land, every rational person quietly puts a little less into it. Which makes it less likely to land. Which means everyone puts in a little less.

Nobody decided to abandon it. Nobody ever will. It will just be quietly deprioritized by everyone simultaneously, and then it will be somebody's fault at a retro.

You are operating at
of the effectiveness this exact work would have had in a small, focused, co-located team.

Same you. Same skills. Same hours. of the output.

So it isn't you.

Nothing above required a villain. No bad manager, no lazy coworker, no politics. Every single person behaved well and the arithmetic still ate your year. That's what a coordination headwind is: a force that emerges from the structure itself, invisible because it never shows up as anyone's decision.

Which is also why most of the obvious fixes make it worse. Trying harder adds churn. Escalating burns the one resource that's actually scarce. Demanding everything be perfect makes every action require more coordination, which is the thing that was already killing you.

What's actually in your hands

Shrink the n before you optimize anything else

Every number above is dominated by how many people have to say yes. A version of your project with four people instead of is not 40% easier. Check the number yourself — go back and drag it down.

Aim for good enough, on purpose

Perfection means coordination, and coordination is the expensive thing. "Converging to a decent outcome on a decent timeline" is not settling. It's the only affordable target when the headwind is this strong.

Take the roofshot

Not a straight shot at the moon. Pick a direction worth years, then take the nearest step that's a genuine no-brainer and locks in real value. Then the next one. You'll waste effort. You'll waste less than the leap would have cost.

When someone frustrates you, assume a constraint you can't see

You are about to attribute a systemic effect to somebody's character. Everyone is. That's the ratchet that turns a headwind into a hostile workplace.