You Don’t Have a Delegation Problem—You Have a Decision Design Problem
If you’re a mid-market CEO, you’ve probably said some version of: “Why does everything land on my desk at CEO. I just need to get better at delegating.”
Your calendar is full of decisions. Your team hesitates, checks in, and forwards things “for your review.”
It’s easy to decide the problem is you. In my experience, it usually isn’t.
You don’t have a delegation problem. You have a decision design problem.
The way decisions move through your business is unclear, inconsistent, or unsafe—so they roll downhill to the one place everyone trusts: You.
The Myth of the “Bad Delegator”
Here’s the pattern I see in $20M–$150M companies:
- You were the one who made the early calls
- The business rewarded you for being decisive and in the details
- “Run it by me” slowly became the operating system
- Now you’re the bottleneck—and it feels like a character flaw
You start to think:
- “Maybe I just don’t trust people enough.”
- “Maybe I micromanage.”
- “Maybe I hired the wrong leaders.”
Sometimes there is a leader issue. But more often, people are behaving perfectly rationally inside a system that is:
- Vague about who owns what
- Inconsistent about how decisions get made
- Punishing when someone takes a risk and gets it wrong
So of course they come back to you.
You’re not a control freak; you’re just the only person who knows where the decisions actually live.
How Do You Know It’s a Decision Design Problem?
When a CEO says “I just need to delegate more,” I listen for a few tells:
1. Decisions keep boomeranging back to you
- You push something down… and it quietly floats back up in a different form
- People “just want your take” before they act
2. The same topics show up in multiple forums
- A decision appears in one-on-ones, then exec team, then email
- That’s not healthy caution—that’s unclear ownership
3. Leaders disagree on who should decide
- “That’s ops.”
- “No, that’s sales.”
- “We should bring finance in.”
- The debate never quite ends, so the safest answer wins: ask the CEO
4. People avoid saying “I decided”
- You hear a lot of “we thought,” “we assumed,” “we were thinking”
- Not a lot of: “I decided X because Y.”
5. You’re involved in decisions that surprise you
- Halfway through a meeting you realize: “Why is this on my calendar?”
- But you take it anyway, because someone has to
That’s not a personality flaw. That’s a decision architecture problem.
Delegation vs. Decision Design
Delegation is about tasks:
- “Can you handle this?”
- “Please take this off my plate.”
Decision design is about ownership:
- Who gets to decide what?
- With which inputs?
- At what speed?
- When do we revisit it?
You can delegate tasks all day long, but if people aren’t sure:
- Which decisions are truly theirs
- When to inform vs. ask
- What “a good decision” looks like in your world
…they will keep looping you in.
A healthy mid-market operating model has:
- Clear decision domains (what lives with the CEO vs. the team)
- Named decision owners (by role, not by personality)
- Shared guardrails (how much risk is acceptable, when to escalate)
Without that, “delegate more” is just another item on your to-do list.
The Decision Flow Grid™ (With a Real Example)
When I work with CEOs on this, we build a Decision Flow Grid™ for the business.
Start with your Top 10 recurring decisions—the ones that show up every week:
- Pricing exceptions
- Hiring approvals
- Customer concessions
- Project go/no-go calls
- Capital expenditures above a certain dollar amount
- Priority conflicts between sales / ops / service
For each decision, answer four questions:
1. What is the decision? Be specific:
- “Approve discounts above 12% on deals over $100K.”
- “Commit to a go-live date for enterprise implementations.”
2. Who decides? A role, not a name:
- “VP of Sales”
- “Head of Implementation”
- “CFO”
3. Who’s consulted?
- “Finance confirms gross margin impact.”
- “Ops confirms capacity and timeline.”
4. Who’s informed?
- “CEO informed weekly on exceptions and patterns.”
A real example:
Originally, the CEO personally approved every discount over 10% on deals above $50K. Deals stalled while everyone waited for an answer.
We shifted that decision to the VP of Sales, with:
- Finance consulted for margin below a certain threshold
- CEO informed weekly on all exceptions and trends
Result: faster deals, cleaner visibility, and one entire category of “Can you look at this?” off the CEO’s plate.
When you put your own decisions into a grid like this, the truth usually appears:
- Half your “CEO-only” decisions don’t actually need to be yours
- People are consulting 5–6 roles when they really need 1–2
- Nobody is explicitly owning some of the most painful calls
CASE SNAPSHOT: “Everything Still Comes to Me”
A CEO told me:
“I’ve told my team a hundred times: ‘You don’t need to run everything by me.’ But they still do. I must just be a control freak.”
On paper, the exec team was strong. In reality, we found:
- No shared list of critical decisions
- Each leader had a different mental model of “what the CEO wants to see”
- Past blow-ups made people gun-shy about acting without a check-in
- The CEO said “decide without me,” but the operating model still rewarded caution
We didn’t start with a generic leadership workshop. We started with:
- Listing the Top 15 recurring decisions clogging the CEO’s week
- Sorting them into three buckets: – CEO Must Decide (strategy shifts, major capital, key hires) – Team Must Own (within clear guardrails) – Needs a Better Design (unclear, cross-functional, messy)
Then we built a Decision Flow Grid™ for just five of those decisions.
In 90 days:
- CEO time freed up for strategy and key relationships
- Leaders started saying, “Here’s the call I made and why”
- The team stopped using “What will Jane think?” as the default filter and started using shared guardrails instead
The CEO didn’t suddenly become “great at delegating.” We changed the design so delegation made sense.
Why People Don’t Use the Authority You Give Them
You can hand people “more authority” and still get nowhere. Three common reasons:
1. Past scars
- Someone made a call, it went sideways, and the lesson they took was: “I shouldn’t decide without running it by the CEO.”
2. Inconsistent signals
- One week the message is “move fast.”
- The next week it’s “why did you do that without checking?”
- The safest strategy becomes: ask first, always.
3. No shared decision language
- Some leaders think “inform” = “get approval.”
- Some think “consult” = “they decide.”
- Without a common language, your calendar becomes the arbiter.
Until you address those, “just delegate more” is like telling people to drive faster with fogged-up windows.
A Simple Decision Design Reset
Here’s a 60–90 minute working session you can run with your team:
1. List the decisions that exhaust you
- Ask your assistant or chief of staff: “What are the decisions that show up on my calendar every single week?”
- Put each on its own line or sticky
2. Sort them into three columns
- I must decide these
- I should decide these with input
- My team should decide these within guardrails
3. Choose 3–5 decisions to redesign
- For each, run it through your Decision Flow Grid™
4. Set explicit guardrails
- “You can say yes to anything under $X with gross margin above Y%.”
- “You can commit to dates as long as ops has confirmed capacity.”
- “Escalate if: margin drops below X, risk is Y, or a key customer is impacted.”
5. Practice the language
- Next time someone brings you a decision, try: “This lives in your column now. What’s your call?”
- Then back them up—even if you might have chosen slightly differently
Where to Start: One Decision You Can Give Away This Month
You don’t have to redesign your entire decision architecture. Start smaller:
1. Pick one decision category that keeps hitting your desk
- Discounts
- Hiring below a certain level
- Project prioritization
2. Decide, on purpose, who should own it going forward
3. Define simple guardrails together
4. Commit, out loud, that you’ll support that role’s decisions inside those guardrails
Expect a few shaky reps. That’s normal.
Well, you might be right that “it’s just easier if I do it.” But in my experience, that’s the sentence that quietly caps both your growth and your leadership team’s.
Let’s Make This a Conversation
If it feels like every important decision still finds its way back to you, you’re not alone—and it doesn’t mean you’re bad at delegating.
It means your business is ready for better decision design.
If this describes you, schedule 30 minutes on my calendar and we can talk about:
- Which decisions you should still own—and which your team can own now
- How to use a simple Decision Flow Grid™ to clean up ownership
- How to shift from “What does the CEO think?” to “What do our guardrails say?”
Not quite ready for that? Share this with your leadership team and use it as the agenda for your next working session on how you make decisions as a company.