The System That Keeps Strategy AliveIssue #40 Hi Reader, I realized something uncomfortable. If I stepped away, our execution would soften. The team would keep working. Meetings would still happen. Revenue would come in. But the strategy would drift because it lived in my head. Not in the system. We didn't have a scorecard. We didn't have a planning rhythm that the whole team could see. We had instinct. That's how a lot of development operations run. The leader isn't weak. The system is just missing. System Twelve fixed that. What Was MissingWe had strategy conversations. Goals in documents. Smart people doing good work. What we didn't have was a rhythm strong enough to carry the strategy forward. That's the quiet failure mode in many fundraising operations. Ideas exist. Nothing connects them to the work happening on a busy afternoon. Strategy floats above the team. Eventually, it fades. System Twelve Connects It AllWe run a modified EOS rhythm. Five layers. Each one does a different job. Vision. The point isn't inspiration. Its direction. Every decision below it points here. Three-Year Targets. What must be true in three years for the vision to be real? Not aspirations. Measurable outcomes. Annual Plan. Every spring (we're on a July fiscal start), we answer two questions. What are we committing to this year? And — just as important — what are we saying no to? Most organizations skip the second question. That's why the year fills with work nobody planned. The Change that Shifted EverythingRocks. The foundation before the pebbles and sand fills your day. Rocks are 90-day priorities. Clear outcome. Every staff member has at least one. I push for only one - something that stretches but is attainable. When Rocks connect to the annual plan, something subtle happens. Strategy stops floating above the team. It becomes the work. The team wasn't less busy. The work just finally had direction. The ScorecardThe weekly scorecard lets us see what's coming. Most development scorecards track lagging indicators. Revenue. Pipeline totals. Closed gifts. Those tell you what already happened. We track two leading indicators for the past seven days: new leads created and proposals submitted. When those numbers move, revenue follows. When they slow, we know before the quarter breaks. That gives us time. Time to adjust. Time to lead. And we track hybrid indicators like pipeline velocity and stuck opportunities that pinpoint where we need to zero in with a prospect. The Weekly Level 10Every Thursday. Same meeting with direct reports. Same sixty minutes. Same agenda. Scorecard review. Rock progress. Issues surfaced and solved. The structure prevents drift. Without it, the week fills with motion. With it, the week moves the strategy forward. How the Systems ConnectThe other eleven systems give you the tools. Pipeline discipline. Delegation. CEO alignment. Portfolio structure. System Twelve is what activates them. Without a planning rhythm, you have a list of good ideas. With one, you have an operating model. Put It Into PracticeLook at your planning rhythm and challenge yourself. If you stepped away for 30 days — would the strategy keep moving? Quarterly planning. Rocks. Scorecard. Level 10. If any of those stop when you step away, the system isn't finished. Unfinished systems eventually cap growth. That's the work.
If this is useful, forward it to a colleague building their fundraising operation. They can subscribe here.
On My RadarIf the EOS rhythm I described sounds like something worth going deeper on, the source material is Traction by Gino Wickman. It's a go-to reference source for me. It's the book that introduced me to Rocks, Level 10 meetings, and the weekly scorecard. We run a modified EOS — but the core architecture is Wickman's. If you've been running on instinct and want a framework that holds, start there. It's one of the few business books that translates cleanly into a development operation. Coming Next WeekOne bonus issue before we close the series. Emotional labor that chief fundraisers carry. It's the system underneath all the systems. Almost nobody talks about it. Your TurnRight now — which one is true for you? A. Most of my week is execution. Strategy is something I get to when there's time. B. I have a planning rhythm. Strategy is built into the week. Reply A or B. Next week I'll share what the group said — and what it reveals about where chief fundraisers are actually spending their time. PS — One issue left in the Chief Fundraiser OS series. If you've been following along and want the full workbook before it goes public, reply "workbook" now. The early list closes when the series does. 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 — pressure, the team, strategic decisions — that's not in any newsletter. So I started writing it down. Sundays. Free.
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...