You can measure the bottleneck by what happens when you take a day off.

The work does not stop. It waits for you, lurking in your inbox or text threads. More likely than not, it interrupts your day at the lake with persistent phone calls until you eventually pick up.

A decision rights map is how you fix that.

A one-page document that lists each recurring decision, names the owner, and sets the threshold below which that owner acts without asking. It pulls routine calls off your desk, and it becomes the norm the first time someone appeals a call and you send it back through the owner.

The three moves below get you started this week. The rest of the issue covers the seven signs you have become the bottleneck and how to build the map in full.

Three things you can do this week

Growth gets heavy when every meaningful decision comes back to the founder. Jobs wait, managers stall, and the week fills up with approvals that should have been handled two levels down.

That pattern is a design problem. The company never defined which decisions the team can make without asking. The missing piece is a clear decision rights map.

You are working hard but the business still feels slow. The team stays busy, yet work piles up around approvals, exceptions, and clarifications that only you can give.

A pricing exception, a vendor issue, a schedule change, a customer credit call. None of them look huge on their own, but together they turn you into the routing point for the company.

People say they need your judgment because the judgment has never been written down. They know you know the right call, but they do not know where the edges are or when they can move without asking.

The issue reaches them, they assess it, then it still comes to you. That usually means authority and accountability were never tied together in a way the team can trust.

Capable managers stop acting like owners when every visible mistake gets pulled back to the founder. They begin protecting themselves by asking first, even when they already know the right move.

A day out of the office produces a backlog. A week out produces a stack of pending calls, delayed commitments, and projects waiting for release.

Everyone can describe the job status. Fewer people can say who decides on scope changes, write-offs, discounts, hiring approvals, or customer recovery steps. When ownership stays fuzzy, escalation becomes the default path.

A decision rights map is a working document that lists recurring decisions, assigns an owner, and defines the threshold below which that owner can act without asking permission. It turns judgment from a founder habit into an operating rule.

That matters because most founder bottlenecks are built one exception at a time. Someone asks a question, the founder answers it, and the answer stays verbal. The next time the issue comes up, the team asks again. A map breaks that cycle by giving the team a rule they can use in real time.

The simplest version has three columns.

The decision is the recurring call that keeps surfacing. The owner is the person or role who closes that call. The threshold is the limit, condition, or rule that tells the owner when they can move alone and when the decision must move up a tier.

A good map also works in tiers. In most founder-led businesses, the three practical tiers are team-owned decisions, manager-owned decisions, and founder-owned decisions. The purpose is to route the decision to the lowest level that can handle it well.

Most teams make this too abstract. They write down broad responsibilities and call it done. That misses the point.

The map should begin with the actual calls that repeatedly land on the founder's desk. Think in concrete terms.

Pull these from your calendar, text threads, Slack messages, and last two leadership meetings. If a decision came to you more than once in the past month, it belongs on the first draft.

Aim for 10 to 20 recurring decisions in version one. That is enough to expose where the founder is still carrying hidden operating weight.

Once the decisions are listed, assign each one to a role. Use the seat's title, "Operations manager" or "Project manager," so the rule survives turnover when the person in the seat changes.

Ownership should follow the seat closest to the decision with enough context to judge it well. If every item still lands with the founder after this step, the map is documenting dependence. Keep pushing decisions downward until you reach the lowest level that can reasonably own them.

The right owner is wherever the context to judge the call and the standing to be held to it sit together. Sometimes that is the front line. Sometimes it is the manager one tier up.

This is where the map becomes real. Without thresholds, ownership stays vague and people keep asking.

A threshold can be a dollar amount, margin floor, customer type, timing window, staffing level, or risk condition. The team should be able to read it and know whether they can act.

Here are illustrative examples.

Each rule should be specific enough to act on and plain enough to remember. If the threshold reads like policy language from a legal department, nobody will use it under pressure.

Do not stretch this over six meetings. The first draft should be built fast while the recurring pain points are fresh.

Get the founder and two or three key leaders in a room for 45 deliberate minutes. Open with one question: "What decisions keep bouncing back to the founder?" Capture the list, group similar items, assign owners, and set first-pass thresholds.

You are building version one. The goal is to create enough structure that the team can start using it this week.

A simple table is enough. Keep the language operational. If a manager has to interpret what the line means, revise it.

A decision rights map fails when it lives in a slide deck nobody opens. It needs to be visible inside the normal flow of work.

For some teams that means a shared operations document. For others it means a page in the project management system, a pinned item in the leadership channel, or a printed sheet used in weekly manager meetings.

The point is access. If a supervisor is standing in the yard, on the floor, or at a job site, they should know where to check the rule before they call the founder.

Visibility also prevents selective memory. Once the map is published, everyone can see the same operating rule.

A map becomes useful when people practice with real decisions. Take ten recent decisions that came to the founder and walk them through the map.

Ask three questions for each one.

This exercise does two things fast. It improves the document, and it teaches managers how to use it under pressure. Within one session, the team starts to see the difference between a true escalation and a routine operating call.

This is also where weak thresholds show up. If people cannot tell where the line is, the rule needs to be sharper.

This is the moment that determines whether the map has teeth.

Someone will disagree with a manager's call and go directly to the founder. When that happens, the founder has to send the issue back through the owner unless the decision clearly sits outside the threshold.

If the founder overrides the map casually, everyone learns the real rule. The real rule becomes "ask the founder if you do not like the answer." From there, the document becomes decoration.

The founder's job is to back the structure in public and improve it in private. If the manager made a poor call inside the threshold, coach the manager after the fact and tighten the rule if needed. Do not strip the seat in front of the team.

The first version will have gaps. That is normal. What matters is reviewing those gaps quickly.

For the first month, bring the map into the weekly leadership meeting and look at three categories.

Revise the language while examples are still current. Over time, the map becomes more precise and the number of founder touches should drop.

This weekly review also surfaces role problems. If the same category keeps escalating after the rule is clear, the seat itself may lack the skill, context, or capacity to own it.

A decision rights map cannot carry the load alone. People act with confidence when they also have the numbers and meeting rhythm that support the decision.

A service manager can own customer credits more effectively when service failure data shows up each week. A sales manager can own pricing exceptions more effectively when margin reporting is current. An operations manager can own overtime more effectively when staffing and schedule data are visible.

The map tells people who decides. Reporting tells them what the decision is doing. Weekly cadence gives the team a place to tighten rules, review edge cases, and correct drift before it spreads.

In week one, the founder usually feels relief and discomfort at the same time. Relief comes from fewer interruptions. Discomfort comes from watching someone else make a call that you would have handled yourself.

That discomfort is useful. It shows where ownership has been verbal, personal, and dependent on founder presence.

By week three, one of two things usually breaks.

The first break is threshold confusion. The team uses a line that sounded clear in the room and finds out it does not hold up in the field. Fix that by rewriting the rule with a real example attached.

The second break is founder bypass, the appeal covered earlier. Someone wants a different answer, so hold the route and back the owner in public.

Neither problem means the map failed. Both are signs the map is now touching live work.

A strong map is short enough to use, specific enough to trust, and current enough to guide work this week. It covers the recurring decisions that create founder drag, and it puts those calls in the hands of the lowest sensible owner.

You should be able to hand the document to a manager and ask, "What can you decide today without asking permission?" If the answer is immediate and concrete, the map is doing its job.

If the answer is still vague, the team needs sharper thresholds, clearer ownership, or stronger founder follow-through.

Founders get stuck when every call routes to one desk. A decision rights map changes that by defining which calls stay with the team, which rise to managers, and which truly belong with the founder.

If you are running a founder-led business and too many decisions still depend on you, LightPath Advisory helps install the operating cadence, reporting, and decision rights that let the company run with clearer ownership. If that is the work in front of you, let’s have a conversation about it.