Your Team Already Knows the Answer

Issue #30
3-minute read

At our Thursday Level 10 meeting, a direct report raised an important prospect strategy question.

“How should we move forward with this relationship?” he asked.

I almost answered. The strategy felt obvious. We’d navigated similar situations before.

Instead, I asked, “What’s your recommendation?”

He paused, then outlined a thoughtful approach. Relationship timeline. Cultivation steps. Ask strategy. It was impressive.

I turned to the group. “What would strengthen this?”

The team built on his ideas, refining the timeline, suggesting a different entry point, and flagging a connection he’d missed.

By the time I weighed in, the strategy was already 95% there.

That’s when it clicked: my job isn’t to have all the answers. It’s to build a team that can solve these problems together.

Why Delegation Systems Break

Most delegation systems focus on what you get off your plate.

Tasks. Decisions. Meetings.

But handing things off doesn’t build capacity. It just redistributes work.

Real delegation builds three things:

• Independent judgment.
• Shared problem-solving.
• Trust in each other’s thinking.

What System Two Actually Is

Last week, we covered System One in the Chief Fundraiser OS. It’s the rhythms that keep priorities alive.

System One protects what gets discussed. System Two determines who does the thinking.

System Two is the Delegation Operating System. You see it most clearly in meetings, when decisions stop flowing up the org chart and start getting worked through together in the room.

It teaches your team to make decisions without you. Not because you’re unavailable, but because they’re capable.

The Three-Question Delegation Protocol

When someone brings you a decision, try this sequence.

1. “What’s your recommendation?”

This shifts the focus from asking permission to proposing a solution.

2. “Who else should weigh in?”

This encourages peer consultation before escalation.

3. “What would make this even stronger?”

This invites refinement before you add your perspective, reinforcing their ownership.

What Changes

After a few months of using this consistently:
Your team starts consulting each other first.
The questions you get are sharper.
Decisions improve.

Meetings stop being approval queues and become real strategy sessions.

Try This 4-Week Delegation Reset

Week 1: Ask for the recommendation. Wait through the uncomfortable pause.

Week 2: Add peer input. Let them build on each other’s thinking.

Week 3: Ask what would strengthen it. Train them to refine their own thinking.

Week 4: Notice when you add nothing. That’s not failure. That’s success.

Scale Check

Your team asks for your opinion on nearly everything.

You may think that means respect.

What if it means they don’t trust themselves yet?

Coming Next Week

You’ve built rhythms that protect your work. You’ve built decision-making capacity. But what happens when your revenue depends on hundreds or thousands of smaller donors instead of a few major ones?

Next Sunday: System Three, the Pipeline Stability System.

Your Turn

Name one decision that lands on your desk repeatedly.

What’s the decision?
Who brings it?
Why does it escalate?

Reply with your answer. I’ll suggest a framework to help them own it.

Until next week,
​Christine​

P.S. If this was useful, share it with another fundraiser who’s trying to scale without burning out.

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.