Why delegation keeps failing (even with a strong team)


The Delegation Framework That Lets You Grow

Issue #33
3-minute read

You built the team structure. Your strategic operators are in place.

But you’re still the person everyone needs to say yes.

That’s not a people problem. It’s a decision system problem.

The Approval Trap

Delegation isn’t assigning work. It’s assigning decisions.

When I joined my current team, I thought I’d set clear boundaries.

  • The Director of Individual Giving owned prospects under $50K.
  • The Director of Corporate and Foundation Relations owned proposal writing, but not cause alliances.

But I never defined what “owned” meant.

Could they approve a budget variance?
Schedule a donor trip?
Send stewardship without my review?

I hadn’t defined decision authority. So these highly capable leaders did what any reasonable person would do.

They asked permission.

The problem wasn’t them. It was my incomplete system.

What System Five Fixes

System Five is simple: build an explicit decision architecture.

Three parts:

1. Decision Ownership: Who makes this decision without approval?

2. Escalation Triggers: What conditions require an escalation?

3. Approval Boundaries: What dollar amounts, risk levels, or stakeholder relationships require my sign-off?

Without those three, “delegation” becomes reassigning work while keeping control.

The Green, Yellow, Red Model

Green: They Own
Routine, low-risk decisions inside an agreed process and budget.
Examples: stewardship execution, vendor coordination, gift processing, event logistics, portfolio management, and standard donor communications.

Rule: Follow the process, stay in budget, and inform me after.

Yellow: We Discuss
Decisions with real stakes, tradeoffs, or visibility.
Examples: new program moves, budget variances over 10%, staff performance issues, major gift strategy above $50K, cause alliance terms.

Rule: Bring a recommendation. We talk. You decide with my input.

Red: I Own
Enterprise risk and leadership-level commitments.
Examples: CEO and board engagement, crisis communications, major policy positions, significant HR actions, and revenue forecasts shared with leadership.

Rule: I decide. You advise.

What Changes

Before: “Can I do this?”
After: “Here’s what I’m doing. Any concerns?”

Before: decisions waited for my calendar.
After: decisions were made in real time, within clear authority.

Before: I reviewed every proposal and budget line.
After: I review Yellow escalations only. Green moves without me.

The payoff: better decisions once the rules are clear because the system stops forcing them to ask.

The Implementation Test

For one week, track every approval that lands on your desk. For each one, note:

  • What was the decision?
  • What was the dollar amount?
  • What was the risk?
  • Who else would care if it went sideways?

Then sort approvals into Green, Yellow, Red.

Next, define triggers that move a decision up a tier. Most are one of three:

  • Money (thresholds)
  • Visibility (CEO, board, media, top donors)
  • Precedent (first time, policy-setting, irreversible)

Write it down. Share it. Use it for one month. Then revise.

What I'm Still Learning

This model isn’t static.

As capability grows, Green should expand. As risk shifts, Red changes. The discipline is naming those changes out loud.

Right now, I’m testing whether major gift strategy above $100K stays Yellow or moves to Green for experienced directors.

It depends less on gift size and more on relationship complexity and board visibility.

That’s the real shift:

Decisions aren’t assigned by task category. They’re assigned by risk, precedent, and stakeholder impact.

Coming Next Week

When everything feels broken, which systems do you fix first?

Next Sunday: System Six – Systems Investment
A simple ROI framework for choosing what to upgrade when you can’t fix everything at once.

Your Turn

Think of one decision someone asked you to make this week.

If they’d had the Green/Yellow/Red model upfront, would they have asked at all?

Until next week,
Christine

P.S. I’m testing something small: a 30-minute strategy session for five chief fundraisers. If you want to map your decision tiers and triggers with someone who’s been there, reply with “Strategy Session” and one sentence about your situation. First five get a spot.

P.P.S. If you're a new reader, you can find details about System Zero to System Four in our Chief Fundraiser Operating System. It's all here.


I’m Christine Bork, Chief Development Officer at the American Academy of Pediatrics. I write Chief Fundraiser Weekly to share what I’m learning as I lead a growing team and try to do the work in a way that’s sustainable and thoughtful.

Chief Fundraiser Weekly

You know how to fundraise. What you're dealing with now — pressure, the team, strategic decisions — that's not in any newsletter. So I started writing it down. Sundays. Free.

Read more from Chief Fundraiser Weekly

Your Forecast Won't Warn You Issue #394-minute read Hi Reader, Two years ago, we learned something the hard way. A corporate donor surprised us by deciding not to renew a seven-figure partnership. By the time it hit the dashboard, the window for recovery was already closing. The system wasn’t broken. It just didn’t warn us. Most fundraising dashboards are built to measure what happened. Very few are built to surface where you’re exposed. That difference matters when conditions change. Why...

Your Portfolio Is Shaping How Your Team Thinks Issue #384-minute read Hi Reader, Last week, I asked why board connections stall. A — They don't know the prospect well enough and won't admit it. B — They know them, but the ask feels too risky. Here's what those of you who replied said: mostly A. Board connections stall for the same reason portfolios stall. Wrong design. Not wrong people. Let's start with a question. What is your portfolio actually built to produce? Revenue - of course. But, is...

System Nine: Board Leverage Issue #374-minute read Hi Reader, Last week, I asked whether you absorb the CEO's mid-quarter requests or stall for time. I only heard back from one person — and that tells me something. Either the question didn't land, or the answer felt too uncomfortable to put in writing. I've been in both places. So I'll answer it myself. My default used to be absorb. Every time. And it cost me before I built a system that gave ideas somewhere to land. That's what last week's...