Why Small Nonprofits Can't Skip Succession Planning

Most succession planning advice is written for organizations with a bench. A large staff, a deep leadership team, a board with dedicated committees for exactly this kind of thing. That advice is close to useless for the majority of mission-driven organizations actually doing the work, the ones running lean, where three or four people carry the weight of the entire operation.

We saw this clearly in a recent engagement with a nonprofit supporting tens of thousands of students across its region, with a staff of eight. Eight people, one region, no dedicated HR function, and no formal plan for what happens if any one of those eight people leaves.

This is not a rare situation. It is the default state for most small and mid-size nonprofits. And it is exactly why succession planning gets skipped: the standard playbook assumes resources these organizations don't have. (This post is drawn from our recent succession planning engagement with Summit Education Initiative, where we saw this play out directly.)

The real risk isn't losing a person. It's losing undocumented knowledge.

When an organization is small, institutional knowledge lives in people's heads, not in systems. The Executive Director knows which funder relationships need a personal touch. The Director of Finance knows which vendor contracts are quietly expiring. None of it is written down, because there has never been time to write it down.

This is the actual risk succession planning addresses. Not the dramatic scenario of a sudden departure, though that matters too, but the quiet, ongoing risk that critical knowledge and judgment exist in exactly one place, with no backup.

What a right-sized approach actually looks like

A succession plan built for an eight-person organization cannot look like a succession plan built for an eight-hundred-person one. Three things made the difference in this engagement:

Start with a risk assessment, not a plan. Before writing anything down, we identified which roles carried the most risk if the person left tomorrow, based on how concentrated the knowledge and relationships were, not just seniority. In this case, four roles surfaced as genuinely critical. The other roles, while important day to day, were not where the organization was most exposed.

Build Success Profiles, not job descriptions. A job description tells you what a role does. A Success Profile defines what someone needs to bring to do it well: the experience, the competencies, the measurable outcomes, independent of who currently holds the seat. This reframing matters because it separates the role from the person, which is the entire point of succession planning. You are not documenting what your Executive Director does. You are documenting what the next one will need.

Confirm what's already working before fixing what isn't. Part of this engagement included assessing the board's collective expertise against the organization's strategic goals. The finding: the board's expertise was already well aligned. That is worth knowing and saying explicitly, because succession planning can otherwise feel like an exercise in finding problems. Sometimes the honest finding is that the foundation is solid and the gap is narrower than leadership feared.

The result is not a binder. It's a habit.

The test of a succession plan is not whether it exists. It's whether anyone opens it. In this case, the deliverable was a repeatable framework and toolkit, including an internal readiness assessment and an emergency transition plan template, built specifically so the organization could maintain it without outside help going forward.

That last part is the whole point. A plan that requires a consultant to update it is not a plan. It's a dependency.

If you're running lean, start smaller than you think

You do not need a full leadership pipeline program to reduce your real exposure. Start with one question: if any one of your three or four most critical people left in the next thirty days, what would you lose that isn't written down anywhere? That question, asked honestly, usually points directly at where to start.

---