How to Stop Being the Bottleneck: You Are the Routing Table

It sits there until you pick it up.

Last issue closed a series and promised a different shape. Fewer pieces, made properly, aimed at people who can act on them. That starts here. Wednesday is now one claim, in text, and on camera when I get it cut. Saturday stays personal. This is the long one, and for the next three weeks it argues one thing from three positions.

Before the argument, the inbox.

There was a stretch where the first message I read every morning belonged to somebody three levels below me. A pricing exception in one market. A warehouse asking whether to hold a shipment. A finance question about a forecast. Not one of them was mine to answer, and every one of them was addressed to me.

The finance one, in full: "What number are we projecting in our QBR? Our latest projections from the field, or last month's fully cross-functionally vetted number?"

Two numbers, both real. Nothing in the building said which one we were working to.

The argument for the next three weeks

An operation converges on one person even when that person is trying to stop it. Nobody decides this. It happens by construction, and the construction is what I want to take apart, because the usual explanations are all about character. Founders who cannot let go. Managers who will not step up. I held both of those explanations at different times and both were wrong.

This week is the mechanism and the move out of it.

Eleven countries, one inbox

An eleven-country distribution organization. The business doubled in two years, and I was running it through the middle of that.

The escalations came from everywhere at once. Market managers, logistics, the warehouses, finance. Decisions that belonged three levels down landed on my desk, and they kept landing there after I had said, more than once, that they should not.

I read it as a discipline problem. People were not owning their calls. I said so, in reviews and in passing, and I believed that saying it would change something.

It did not, and the reason it did not is the whole of this issue.

They were not escalating because they lacked nerve. They were escalating because they lacked information. Strategy was in my head. The numbers were in my inbox. Nobody three levels down could see what we were trying to do or where we actually stood, so the only reliable way to get an answer was to ask the one person who had both.

Nobody was disengaged. They were correctly reading a system that was never built to receive them.

Something else was happening that I only understood later. A vacuum of information does not stay a vacuum. When the formal channel says nothing, the informal channel becomes the medium, and it manufactures its own content. Issues got bigger on the way up, because on the way up they passed through rooms where nobody knew and everybody guessed. I started calling it escalation inflation. The escalations were not only numerous. They were larger than the problems underneath them.

Where the answer lived

Decisions route to wherever the answer is most reliably found. That is all a decision does. Somebody has a question, they take it to the place that answered correctly last time, and the place that answered correctly last time is the place that gets the next question.

If strategy lives in the owner's head and the numbers live in the owner's inbox, the owner is that place. Not by choice. By construction. A market manager weighing a pricing exception needs to know what the business is trying to do this year and what the margin actually is right now. If the first lives in my head and the second lives in a spreadsheet only I open, the only place in the building that can answer is me. So the question comes to me. So does the next one.

The book puts it plainly. You are the default person for every decision, every escalation, and every strategic question. When I wrote that line I meant it as a description of a burden. It is a description of a routing table.

The book also has the three questions that would have caught this earlier than I did, and I did not use them. For each kind of decision a team faces: Who can make this without consulting anyone. Who can make it after consulting but without approval. Who needs approval before acting. Written down, that is a routing table you can read. I never wrote it down, so the table existed anyway, in the only form an unwritten table can take, which is everybody's memory of who answered last time.

And the people doing the routing are not weak. They are correct. The book names what happens on the other side of it, too: people stop trying because trying does not change anything, the leader will take over anyway. That is not disengagement. That is a rational response to where the answers are.

What I tried first

I tried the person. I pushed escalations back one at a time, each with a note about who held it. Each pushback was a touch. I became the place you go to be told where to go, which is one step removed from the place you go for the answer and costs about the same.

What I did not understand yet is that the condition has two halves, and either half alone leaves it standing.

Put the numbers where people can see them and keep the strategy in your head, and a manager who can see the margin but not what you are trying to protect this quarter still has to ask. Cascade the strategy and keep the numbers close, and people escalate a different question: whether the message still holds, because they cannot see whether it survived contact with the results.

Address one layer and the condition moves. It does not leave.

The number I can stand behind

Mercer asked executives in 2025 whether they could balance long-term strategic planning with short-term operational needs. Eighty percent said they struggle to. My book cites it in the strategy chapter and calls it evidence of a structural problem in how attention gets allocated, not an admission of poor time management.

I want to be exact about what that measures. It measures the balance failure. It does not measure how many of those executives are the routing table in their own operation. I think the two are one condition seen from two angles, but that is my read and the survey does not say it. What the survey says is that four in five say they struggle to balance the two. The mechanism above is one reason why. If every answer lives in you, every question comes to you, and the strategic work is what gets displaced.

One move this week

Count the questions. For five working days, keep a tally of every question that reaches you and could have been answered by somebody else if they had known what you know. Not a judgment about the person. A count.

Then sort the tally into two piles. Questions that needed the strategy, meaning what the business is trying to do. Questions that needed the numbers, meaning where it actually stands. I expect the two piles to come out close to even. If one is empty, that tells you which half is already built.

That is the map of where the answer lives. It lives in you, in two forms, and now you know which two.

What the rails replaced

The move that worked was building both rails at once.

A structured, recurring session where strategy got said out loud, in plain terms, with the reasons behind it. And the numbers, the real ones, in the same session, so people could see how the strategy was holding against them. Same cadence every time, built deliberately against the tendency of every new ritual to fade. The cadence mattered more than the content. A one-off town hall answers the questions people have that day. A session that recurs answers the questions they have not asked yet, because they know where the answer will be when they need it.

The escalations fell. Not to zero. They fell because the place where the answer lived had moved out of my head and into a room that met on a schedule whether or not I was the one speaking.

That is the move. You do not get outside the process by leaving it. You get outside by building the thing that replaces you, and the thing that replaces you is a place where the answer lives that is not a person.

Next issue is what it costs when that place does not get built. Not a feeling. A price.

Oscar

Want to see whether the answers in your operation live anywhere but you? The Resilience Engine Systems Audit maps it: myresilienceengine.com/systems-audit