The part of the job nobody put in the job description


You Can't Systematize This One

Issue #41
4-minute read

Hi Reader,

Last April, budget season handed me a gut punch.

My CEO and CFO have watched us grow 69% without adding a single frontline fundraiser. They believe in the model.

And then the revenue goal for the new fiscal year landed.

Revenue target: up.

Headcount: same.

Strategy conversation: not on the agenda.

They didn’t do it to be dismissive. They did it because that’s how budget math works. Revenue must grow. Expenses need to stay flat. Development is the gap-filler.

I closed my laptop and sat with it for a minute.

That feeling has a name. It’s emotional labor. And it’s the system underneath all the systems.

What Emotional Labor Actually Is

It’s the invisible executive load. The managing of your own emotions in real time so you can keep showing up for everyone else.

It’s absorbing the defeat of a budget number that ignores your strategy, then walking into your team’s Monday meeting and saying, “We can do hard things.”

It’s re-selling your own credibility every budget cycle as if last year didn’t happen.

It’s holding your team’s morale while quietly carrying the weight of a target you didn’t set and weren’t consulted on.

None of that shows up in your job description. But it drains the same cognitive reserves you need for pipeline decisions, leadership judgment, and strategic thinking.

We’ve spent thirteen issues building an operating system.

Emotional labor is what erodes it all when left unmanaged.

Why Chief Fundraisers Carry More Load

Most executives manage anxiety that comes from the outside in.

Chief Fundraisers manage it from the inside out.

We hold the tension between what we know is true about our strategy and what the organization’s financial pressure demands we promise.

We translate donor ambiguity into institutional confidence.

We protect our teams from leadership anxiety while absorbing it ourselves.

And we do most of this without naming it. Because naming it feels like a liability. Because the job description says “manage a portfolio” — not “absorb everyone’s fear about whether the portfolio will hold.”

Every Chief Fundraiser I know has been here. The budget number lands. The strategy gets bypassed. You close your laptop, give yourself 60 seconds, and then you go be the leader your team needs.

That’s not something anyone prepared you for. It’s just the job.

But unmanaged, it compounds.

What I'm Building Right Now

I don’t have a finished system for this. I want to be honest about that. What I’m testing — in real time, this budget season — is a three-part approach.

Name it before it names me. If the defeat comes in the budget meeting this month, when I feel it land, I call it out to myself. “This is emotional labor. This is not a verdict on the strategy.”

Before I respond to the revenue request follow-up email, I'll say it out loud. Then I write the email. Naming it creates just enough distance to respond rather than react.

Separate the feeling from the decision. The budget number is a constraint. It is not a conversation about whether the model is working. I'll hold those two things apart — because they feel like the same thing in the moment.

Choose my disclosure level with the team. I’m honest with my direct reports. Not about everything. But enough. “This is a hard number. I believe we can get there. We do hard things.” That’s not performance. That’s modeling the exact resilience I’m asking them to carry.

What I Know for Certain

The Chief Fundraisers who sustain performance at this level aren’t the ones who feel less.

They’re the ones who’ve built a practice around what to do with what they feel.

The operating system we’ve built over the last thirteen issues creates the conditions for strategy to work. But strategy runs on judgment.

This is System Thirteen. The system underneath the systems.

If you’re prepping for a July 1 fiscal start, you're in budget season right now. You know exactly what I mean.

On My Radar

“What am I carrying right now that isn’t mine to carry?”

Not a tool. Not a framework. Just a question. It surfaces the invisible load faster than any dashboard.

Coming Next Week

The full Chief Fundraiser Operating System. A review of all of the systems and how they connect. It’s the issue we’ve been building toward since December.

Your Turn

Budget season, high-stakes donor conversations, leadership pressure from above.

When the emotional weight lands, what do you do first?

A. You process it privately and show up clean for your team.

B. You name it out loud to a trusted peer before you walk in the door.

Hit reply. A or B.

I’ll share what you said and what it reveals about how Chief Fundraisers carry this load.

Until next week,
Christine

PS — The Chief Fundraiser OS playbook series is coming. System Six is first — a repeatable process for choosing which system to build first. Watch for it this week.

If you’re finding Chief Fundraiser Weekly useful, forward this to a peer who’s carrying the same weight.


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 — the pressure, the team, the strategic decisions — that's not in any newsletter. So I started writing it down. Sundays. Free.

Read more from Chief Fundraiser Weekly

The Ask You Should Not Make (Yet) Issue #473-minute read Hi Reader, Jerold Panas spent decades studying why major gifts succeed and why they don't. His framework was deceptively simple: Ask the right person, for the right amount, at the right time, for the right purpose. People often compress it to three variables. Panas was intentional about the fourth. Purpose is what separates technique from judgment. The real signal isn't just getting all four variables right. It's knowing when one of...

The Donor You Should Not Chase Issue #463-minute read We have a prospect who can't decide. Not because they aren't interested. Not because the mission doesn't resonate. But every time we come back with a program idea, it's not quite right. Too broad. Too specific. Not the right population. Not the right geography. We've generated four or five compelling options. Each one grounded in real need. Each one a genuine fit for what they told us mattered to them. Still not quite right. At some point,...

A KPI System People Can Stand Inside Issue #453-minute read Hi Reader, My management team pushed back. Not hard. Not angrily. But clearly. I'd brought them the final piece of a two-year EOS journey: setting our department's One Number. The structure works in three layers: company, department, and individual. The ask was to pick one number that defines development's contribution to the organization. They couldn't do it. Not because they didn't understand. Because one number couldn't hold a...