A KPI System People Can Stand InsideIssue #45 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 team this functionally diverse. And it didn't reflect our values. We believe every person's contribution matters, and One Number would make some roles invisible. They were right. I put it on my to-do list and left it there for a month. When I picked it back up, the answer was already in front of me. We were already tracking everything that mattered. I didn't need a new system. I needed architecture. Four KPIs. One system. That's what this issue is about. THE FOUR KPIS WORTH BUILDING AROUNDNot all metrics are worth your team's attention. These four follow the natural arc of a donor relationship — and together, they tell you whether your system is healthy or heading for a miss. New Qualified Prospects Identified feeds everything downstream. If this number is soft, we'll feel it in revenue six to twelve months from now. No amount of cultivation skill fixes a thin pipeline. Pipeline Velocity is the engine. It tells us whether prospects are moving toward a decision or stalling in your process. Velocity slows when deliverables lag, proposals are delayed, or meetings are never scheduled. Donor Retention Rate is our back-end health check. Acquisition matters. Retention is what makes the whole operation durable, and it's built one touchpoint at a time. Net Philanthropic Revenue vs. Goal is the outcome. Manage the first three well, and this one follows. If revenue starts lagging, look at the system first. WHY FOUR WORKS WHERE ONE DIDN'TA single department number would have told us whether we hit revenue. These four tell us whether our system is healthy enough to keep hitting it. Your team probably looks different than mine — but the logic holds. More importantly, every function on the team can find itself in this picture that these numbers tell. Frontline fundraisers live in velocity and prospects. Gift processors and stewardship staff live in retention. Communications and data staff connect to all four. Nobody is invisible. That's intentional design. We introduced these to the full team the same way we bring anything new into our culture — as shared language, not as an imposed measurement. We start asking: which of our four KPIs does this affect? Over time, the team will start asking it themselves. That's when you know the system has landed. The next step is to connect individual roles to individual drivers within the system. But I can't build that until the team understands and believes in the foundation. If you know a CDO whose team has metrics but no real ownership, forward this. It might be the right week for them to read it.
And if someone sent this your way, you can subscribe here.
Scale CheckCan every person on your team point to at least one of your KPIs and say, “That's where my work lives”? If you hesitated, you've found this quarter's team development priority. On My RadarI've started using AI as an analyst — feeding it our KPIs, pipeline structure, team roles, and goals so it can work from context. We use Copilot so our data is locked internally. When I bring a real problem, Copilot's recommendations are contextual and getting better at delivering the trend analysis I need. Your TurnPull up your team roster before Friday. Pick one support role — gift processing, data, communications — and write down which of the four KPIs their work feeds. If you can’t answer it in one sentence, that’s your starting point. Reply and tell me: which KPI is hardest for your team to see themselves in? I'll feature the most useful response in next week's issue — with your permission and your city, no names. Coming Next WeekThe donor you should not chase. Every development shop has them. The prospect that looks like a major gift but costs more than it returns. Next Sunday: how to apply opportunity cost thinking to your portfolio, make the strategic no, and protect your team's capacity for gifts that can scale. Until next week, PS — If you're building this system from scratch, start with retention. It's the one KPI your whole team already affects — whether they know it or not. Get that number on the wall first, then build outward. Reply “KPI” and I'll send you my one-page framework. 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. |
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.
When the Problem Isn’t Performance Issue #443-minute read Hi Reader, Last week, I wrote about developing your team one level deep — and promised to come back to what happens when a direct report isn’t doing it. Here’s what I’ve learned: the conversation you think you need to have is rarely the one that moves things. Two patterns show up most often when a direct report isn’t developing their team. The first: a fundraising generalist I promoted to lead a team of specialists. Smart. Committed....
One Level Deep Issue #434-minute read Hi Reader, A CFW reader inspired me with the idea for today's newsletter after we met recently. She said it’s something CDOs wrestle with but rarely talk about. You can be available to everyone. You cannot develop everyone. Those are two different jobs. Confusing them will exhaust you and quietly undermine the people who report to you. Here's the framework I use. Open door. Full stop. My entire team of 16 knows they can come to me. Any time. That's not a...
The Chief Fundraiser Operating System Issue #424-minute read Hi Reader, Fourteen weeks ago, I set out to build an operating system for the Chief Fundraiser role. I thought I knew what it would look like. Twelve clean systems. A logical sequence. A framework you could install and run. Here's what I actually built: something messier and more honest than that. The systems are real. But what surprised me — writing each one, testing the language against what we actually do at my organization — is...