Every Project Still Routes Through You.

Written and narrated by Serguei Poppeleer.

A decision sat in my inbox for three weeks once. Not because it was hard. Because I was the only person allowed to make it.

The business was delivering. Clients were happy. And every meaningful call — scope, price, a supplier we had never used — waited for me to land, read, and reply. The work did not stop. It just queued.

Every decision that routes through one person moves at the speed of that one person. That is not leadership. That is a bottleneck wearing a job title.

The belief

More people will fix it

Most founders read the bottleneck as a capacity problem. We are stretched, so we hire. Another project manager, a senior delivery lead, someone to take it off my plate. Six months later the plate is just as full, because the new person also has to route their decisions through me.

You cannot hire your way out of a bottleneck you are the centre of. You can only widen the queue.

The shift

Move the decision, not the workload

The fix is not more hands. It is moving the authority to decide out of your head and into a written rule any competent person can apply. In the 5Cs, that is CLOSE: every open decision gets an owner, a date, and a consequence, and it closes without you in the room.

Field note - Equatorial Guinea

On a remote camp build, I could not be on site for most of it. The project still moved, because the decisions that mattered were defined before they came up: who calls it, by when, and what happens if the date slips. The site did not wait for me. It ran the rule.

That is the difference between founder speed and system speed. Founder speed is bounded by your calendar. System speed is bounded by the rule, and the rule never sleeps.

What to do this week
1 - List the last ten decisions that waited for you

Write them down. Most will not actually need you. They needed someone allowed to decide.

2 - Give each an owner and a threshold

Below a defined line, a named person decides. Above it, you do. Put the line in writing.

3 - Add a decision-by date and a consequence

An open item with no date and no consequence is not a decision. It is a hope.

4 - Leave the room

For two weeks, refuse to be the default. If something breaks, the rule was wrong. Fix the rule, not the habit.

But...
But some decisions really do need me.

A few do. Most do not. The job is to find the line, write it down, and stop applying your judgement to the ninety percent a rule could close faster than your inbox.

But if I let go, quality slips.

Quality slips when decisions are slow and inconsistent, which is exactly what a single-point bottleneck produces. A written threshold is more consistent than a tired founder at eleven at night.

But my team will just escalate everything anyway.

They escalate because escalating is safe and deciding is not. Give them the authority in writing and the consequence of not using it, and the escalations stop.

AI Reality Check

AI can draft the decision log, chase owners, and flag every item past its date before your stand-up. What it cannot do is decide who is allowed to decide. If the authority lives in your head, AI just gives you a faster, tidier queue that still ends at you. Write the rule first. Then let the tool run it.

The business does not depend on you because the work is hard. It depends on you because the decisions have nowhere else to go. Give them somewhere else to go.

Find where delivery still depends on you.

Get your Delivery Score. Fifteen Yes/No questions, about four minutes. It shows which of the five controls is weakest as you scale.