You Trained Them to Ask You Everything (That Is Why You Are Still the Bottleneck)
September 24, 2026 · Brooke Elder · 6 min read
You Trained Them to Ask You Everything (That Is Why You Are Still the Bottleneck)
Your team keeps asking you the same questions because you trained them to. Smart people wait for your nod when the business has no clear decision rights. SOPs help with repeats. Decision rights help with judgment. Track the questions for a few days, write the rule (not one answer), and assign who can decide what. That is how you stop being the approval system.
Here's what we'll cover:
- Why "just write an SOP" doesn't stop the ping storm
- Decision rights vs SOPs (what each actually solves)
- The Ask-You Audit: track, cluster, write the rule, assign the lane
- When it is a hiring problem vs a rights problem
- What calm looks like when the team already has the rule
It's Tuesday at 10:14am. Your phone lights up. "Quick question on the client refund." Then Slack. Then a voice note. Then another Slack because the first answer wasn't enough.
Your team is not lazy. They are doing what worked. Asking you is faster than guessing wrong. You answered once, then again, then again. You became the documentation.
Here's the thing: you did not hire a confused team. You trained a team that waits for permission.
Why does my team keep asking me the same questions?
They ask because the answer still lives with you, and the safe move is to check. Repeating yourself feels helpful. It also teaches them that your nod is the real process.
Consulting blogs already own pieces of this language. Founder-bottleneck pieces talk about being the hub. SOP guides talk about writing things down. Reddit operators say it plainer: you are the documentation, and making the SOP has to be faster than pinging you.
What most of those pieces miss for a seven-figure service owner is the second half. Lisa does not only need checklists. She needs rules for judgment. Spend. Refunds. Client promises. What "good enough to send" means without her sitting in the middle.
I lived the soft version of this. Team of smart people. Still the router. Every exception came upstairs because we never named who owned the call.
SOPs vs decision rights (what each solves)
SOPs solve repeatable steps. Decision rights solve judgment calls. If you only write SOPs, people still ask you every time the situation is "close but not exact."
An SOP says: how we do the refund form, which fields, which email template.
A decision right says: who can approve a refund under $250 without asking you, who owns anything over that, and what must be logged.
Gloria Mark's interruption research (often cited in ops guides like SOPX) is a useful caution, not a shame stick. Context switching is expensive. Every "quick question" is a tax on the person who still holds the map.
Balanced truth: sometimes you hired for relief and got another person who needs you. That is a hiring-fit problem. Often you hired fine people into a business with no lanes. That is a rights problem.
Introducing The Ask-You Audit
The Ask-You Audit is a four-step way out: track the questions for 3 to 5 days, cluster them, write the rule (not one answer), then assign who can decide what. Strategy First. AI Second. Frameworks before tools.
Step 1: Track the questions for 3 to 5 days
Do not fix yet. Capture.
Every ping that needs your nod: who asked, what they asked, what you decided, how long it took. Phone, Slack, email, hallway. Three days is enough to see the pattern. Five is better if your week is weird.
Example: an owner I worked with thought she had a "training problem." The log showed the same four themes: discounts, timeline promises, content publish, and "is this client update ready." Not fifty unique crises. Four missing rules.
Step 2: Cluster the themes
Group the asks. Pricing exceptions. Client commitments. Quality calls. Tool choices. Hiring / firing vibes. Refunds.
If a cluster shows up more than twice, it is not a personality quirk. It is a missing rule.
Step 3: Write the rule, not one answer
This is the move people skip.
One answer sounds like: "For this client, yes, refund $180."
A rule sounds like: "Anyone on delivery can refund up to $250 when we missed a deliverable. Log it in ClickUp. Anything over $250 needs me. Never refund goodwill without a note on why."
Write so using the rule is faster than asking you. If the rule still needs you every time, you wrote a preference, not a right.
Step 4: Assign who can decide what
Name the person (or seat). Name the ceiling. Name where the decision gets recorded.
Then coach the sentence that breaks the habit: "What's your recommendation?" when they still ping you with a blank slate. You are not being cold. You are teaching them to bring a draft decision, not an empty hat.
When is it hiring vs rights?
If the same person cannot follow a clear rule after coaching, that can be a hire problem. If every person asks you the same themes, that is a rights problem. Fix rights before you add headcount that will join the queue.
Hire for leverage after the thresholds exist. Otherwise you pay for another person who waits for your nod, and profit gets thinner while the approval line gets longer.
AI can help later. Draft the rule from your question log. Sort themes. Remind the team where the rule lives. Do not start by buying another chatbot that still routes exceptions to you. Strategy First. AI Second.
What "out" looks like
Out looks like this: the next question already has a home. Your team brings a recommendation. Work moves without your body in every doorway.
You stay the brain. The system holds the rules. People (and later AI) use the lanes.
Frequently Asked Questions
Why does my team keep asking me the same questions?
Because asking you is safer and faster than guessing, and your answers never became lasting rules. Track the asks, write decision rights for judgment, and keep SOPs for repeatable steps.
What are decision rights in a small service business?
Decision rights name who can decide what, up to what limit, and where it gets logged. They cover judgment calls like refunds, discounts, client commitments, and publish approvals.
Will writing more SOPs stop the founder bottleneck?
SOPs help with known steps. They rarely stop "is this okay?" questions. Pair SOPs with decision rights so people can move on close calls without you.
How do I stop being the approval bottleneck without dumping risk on my team?
Start with clear ceilings (spend, refunds, promises). Require a recommendation when they ask. Review the edge cases weekly, then widen the lane as trust grows.
Should I hire a fractional COO before I fix decision rights?
Usually no. A COO cannot install judgment lanes you refuse to name. Build the Ask-You Audit first. Then decide if you need a person to run the system.
Ready to stop being the approval system?
If this hit a little close, you do not need another tool stack. You need community and frameworks for decision rights and crew commissioning so your people (and your AI) stop waiting on you.
Brooke Elder, Co-Founder, True North Strategies
Brooke has built seven businesses and exited two. She cut her own team from 27 to 6, kept the revenue, and got the profit back. Then she crossed the Atlantic on a sailboat with her family while the business kept running. She teaches the operations layer: frameworks, systems, and the AI Crew.