Glossary

Routing vs Leading

Routing vs leading is the distinction between processing your team's work one item at a time — answering questions, making small decisions, unblocking people — and acting on the system that produces that work: its standards, decision rights, and handoffs. Routing feels productive; only leading compounds.

Routing vs leading is the distinction between two operating modes any manager can fall into in a given week. Routing is processing the team's work one item at a time — answering questions, making small decisions, rewriting work for people, staying in the middle so traffic keeps moving. Leading is the deliberate choice to act on the system that produces the team's work: its standards, its decision rights, the documents it uses, and the patterns it reproduces. The terms are coined in The Control Standard to name a failure mode most growing managers slip into without admitting it.

Why it matters

Routing feels productive because it is — traffic gets processed, items move, people get answers. But every hour spent routing strengthens the team's dependence on you, and every hour spent leading weakens it. A year of routing-heavy weeks produces a team that is competent, responsive, and subtly incapable of moving when you are away. The same reflex is the grown-up version of the heroic habit: it does not look like entropy, it looks like helpfulness, which is exactly why it persists and why the cost is easy to miss.

The one-line test

If your team cannot predict your expectations and act without you, you are routing, not leading. The test is not whether they like you or speak well of you when you are out of the room. It is whether they can move the work forward without you in ways you would broadly recognise as correct when you returned. If they cannot, the system has not yet been built — and no amount of personal availability substitutes for what has not been built.

The move from routing to leading runs through how decisions get made, how work is delegated, and when you step in versus step out. The Control Standard works through each of those — including replacing permission with intent and naming a single owner before you delegate outcomes — as the route out of being the bottleneck.

Frequently asked

What is the difference between routing and leading?

Routing is processing the team's work one item at a time — answering the question, making the small decision, rewriting the paragraph, unblocking the person in front of you. Leading is acting on the system that produces that work: the standards it holds, the decisions it is allowed to make, the documents and handoffs it relies on. Routing clears today's item for one person; leading raises how five people handle their equivalents every week.

Is routing always bad?

No. Acting as a router is the right move in an incident, an urgent commercial escalation, or the first fortnight of a new joiner — any time speed and certainty matter more than learning. The problem is the unconscious drift into routing as your default posture when none of those conditions apply. Transactional behaviour is a tool, not a posture.

How do I shift from routing to leading?

Stop accepting decisions and start accepting recommendations: hand work back with 'bring me two options, the trade-offs, and your recommendation.' Name one owner for each outcome, then delegate the outcome rather than the task. Reserve your time for the work that sits at your own altitude rather than a level below it. See how to delegate outcomes.

Guide

How to Stop Being the Bottleneck Your Team Waits On

You become the bottleneck when too many decisions and too much context route through you alone. The way out is to make your expectations predictable, push decision rights down with clear guardrails, and let people act from their remit rather than waiting for instruction — so work moves when you're not in the room.

Guide

How to Delegate Outcomes, Not Just Tasks

To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.

Topic

Delegation: How to Hand Over Work So It Actually Holds

Effective delegation means handing over an outcome — not just a task — with a clear standard, sensible constraints and the right check-ins, so the work comes back finished rather than bouncing back to you. Done well, it raises a team's capacity and lowers the manager's role as bottleneck.

← Back to the glossary