How to build a board development plan that actually gets used

Board development is one of those phrases that gets used a lot and acted on very little. Most executive directors and board chairs agree it matters. Fewer can point to a clear plan or even a shared definition of what it means for their organization.

This article is meant to slow things down. Not to add another framework or checklist for its own sake but to give you a practical way to think about board development as an ongoing responsibility tied directly to where your organization is headed.

If you are leading a nonprofit board or supporting one you do not need perfection. You need clarity, follow through, and a willingness to adjust as the organization changes.

What board development actually means in practice

At its core board development is anything that helps the board do its job better. That includes formal training but it also includes how information flows, how decisions get made, and whether board members understand what is expected of them.

Development is not a single event. It is not solved by an annual retreat or a new handbook. It shows up in how prepared people are for meetings, how confident they feel asking hard questions, and how well the board stays focused on strategy instead of drifting into operations.

If development feels vague on your board that is usually a sign that expectations have never been clearly stated.

Start with direction before skills

Many boards jump straight to skills matrices and recruitment targets. That can be useful but only after the board agrees on where the organization is going.

Your mission may be stable but your strategy is not. Growth, contraction, new programs, mergers, funding shifts, and leadership transitions all change what the board needs to contribute.

Without a shared view of vision and strategy it is impossible to know what experience or perspective is missing from the boardroom. You end up recruiting based on generic ideas of what a “strong board” looks like rather than what this organization needs right now.

Written role descriptions are not optional

It is still surprisingly common for boards to operate without written role descriptions. Or with documents that exist somewhere but are rarely referenced.

A role description does not need to be long. It does need to be explicit. What decisions belong to the board. What belongs to staff. What individual board members are responsible for between meetings. What the chair’s role is versus the rest of the board.

When role clarity is missing board development efforts tend to backfire. Training adds knowledge but not alignment. New members bring energy but also confusion about boundaries.

Define the skills the board actually needs

Once direction and roles are clear you can look honestly at board-level skills. This is not about turning your board into a management team. It is about identifying the expertise and lived experience that help the board govern well.

Sometimes the gap is obvious. Financial oversight during a period of volatility. Legal insight during a merger. Community representation when credibility is at risk.

Other gaps are quieter. Comfort with ambiguity. Ability to challenge assumptions respectfully. Experience leading through change.

The important thing is to think in terms of the board as a whole rather than individual résumés.

Conduct a skills audit without making it personal

A board skills audit should feel descriptive not judgmental. The goal is not to rank members but to see the collective picture.

Map current skills against what the board needs to fulfill its role over the next few years. Patterns will emerge. Strengths to lean on. Areas where no one feels confident speaking up.

This exercise often reveals development needs that can be addressed internally without recruiting anyone new.

Advertisement

Address gaps in ways that fit real board life

Formal training has its place but it is only one tool. For many boards the most effective development happens in small doses tied to real decisions.

A focused learning segment before a meeting. A facilitated discussion during a retreat that connects strategy to governance responsibilities. Briefing papers that explain a complex issue without overwhelming people.

When choosing how to address gaps consider how many people need the same development, how urgent the issue is, and how realistic it is to get everyone in the same room.

Board development that respects volunteers’ time is far more likely to stick.

Make the plan visible and shared

A board development plan that lives only with the chair or governance committee will not change much.

Everyone should know what the priorities are and what is expected of them. If there are training sessions scheduled people need to commit to them. If there are expectations around preparation or peer learning those should be named.

Development is a collective effort. Transparency helps reinforce that.

Induction is part of development not a separate task

Bringing in new board members is one of the most effective ways to strengthen board capacity. It is also where many boards stumble.

An induction program should go beyond history and bylaws. New members need context for how this board operates. What good participation looks like. How disagreement is handled. Where the organization is confident and where it is uncertain.

A strong induction shortens the learning curve and reduces frustration on both sides.

Use refreshers to recalibrate expectations

Even experienced board members benefit from periodic refreshers. Not because they have forgotten the basics but because the organization has changed.

Short sessions woven into regular meetings can be more effective than standalone training days. The goal is to reconnect governance responsibilities to current realities.

When refreshers feel relevant people engage. When they feel generic people tune out.

Annual reviews should feel developmental not punitive

One of the most underused tools in board development is the annual conversation between the chair and individual board members.

These conversations do not need to resemble corporate performance appraisals. They should focus on contribution, expectations, and support.

Advertisement

What has been working. Where the board member feels stretched. What development would help them be more effective.

Handled well these reviews strengthen relationships and surface issues early.

Board development is never finished

Strong boards do not arrive fully formed. They evolve alongside the organizations they serve.

The point is not to check every box but to build habits of reflection and adjustment. To notice when the board’s needs are changing and respond before problems harden.

Development is less about programs and more about attention.

The NPD Perspective

We see board development fail most often when it is treated as a project instead of a responsibility. Plans get written. Workshops get scheduled. Then attention moves elsewhere.

The boards that make progress keep things simple. They tie development to strategy. They clarify roles early. They talk openly about what the board needs next.

If your board is asking better questions than it did a year ago you are probably on the right track.