When the Problem Isn’t PerformanceIssue #44 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. Right person on the bus. But struggling in ways that didn’t make sense on paper. What I eventually understood was that they couldn’t develop what they couldn’t see. They’d never been a specialist. They had no map for what growth in a role they’d never held looked like. They weren’t failing to develop their team out of negligence. They were developing from a deficit. The second is quieter. A manager who was perfectly comfortable. Not looking to advance. Not unhappy. Just… settled. And because they weren’t building toward anything for themselves, they had no framework for building toward something for their people. Development plans felt like paperwork. Growth conversations felt abstract. They weren’t resistant; they were empty-handed. Different situations. Same root problem. Neither conversation needed to start with performance. What the data says — and what it missesA new report from Momentive Software — the 2026 State of the Mission-Driven Workforce — found that nearly two-thirds of nonprofit managers don’t see a clear career path for themselves. The authors frame this primarily as a retention risk. And it is. But there’s a layer the report doesn’t name directly. When your managers don’t have a vision for their own future, they have nothing to transmit to their teams. Career path clarity isn’t just about keeping your people. It’s about what they’re capable of giving while they’re there. The conversation that workedWith the generalist-turned-manager, I had to get specific. What did they want to build? What would they want someone to say about the team they’d grown, not their own career, but the team? Once we got concrete about that, something shifted. They stopped trying to develop their specialists into versions of themselves. They started asking better questions about what each person needed. With the contented manager, I tried something different. I stopped pushing on advancement entirely. Instead, I asked what they wanted to be known for. Not what title they wanted next. What they wanted to leave behind. That reframe changed everything. Legacy isn’t about climbing. It’s about impact that outlasts you in a role. Once they connected to that, developing their team no longer felt like an HR requirement. What this means for the conversation you’re dreadingBefore you sit down with a direct report who isn’t developing their team, ask yourself: Do they have a vision for their own next chapter? Not a promotion timeline. Not a development plan checkbox. A real answer to: what do I want to be known for, and what does the team I build say about me? If they don’t have that, the performance conversation won’t land. You’ll be pushing on a door with no frame. Start with legacy. The accountability conversation comes after. On My RadarStill sitting with Cialdini’s Influence. This week, the chapter on commitment and consistency hit differently in the context of legacy conversations. When you help someone name what they want to be known for, you’re not just clarifying their future. You’re creating a commitment they’ll work to maintain. Your TurnThis week, try the reframe once. You have a direct report who isn’t developing their team. I’ll bet retention is a challenge, too. Before your next conversation with them, which situation fits better? A: I’ve never asked them what they want to be known for. I don’t know. B: I know what they want, but we’ve never connected it to how they lead their team. Either way, that’s your next conversation. Let me know which one resonates, and what happened. If a peer would find this useful, forward it. And if someone sent this your way, you can subscribe here:
Coming Next WeekSometimes, the clarity conversation doesn’t move things forward. The problem really is effort or execution. That conversation looks different. That’s next Sunday. Until next week, PS — Before you can help your managers name their next chapter, it helps to name what's capping yours. The Chief Fundraiser OS Diagnostic is here for you.
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.
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...
You Can't Systematize This One Issue #414-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....