You’re ninety minutes into the strategic planning retreat. The flip charts are full. The coffee is gone. Someone has reopened the discussion about whether the mission statement needs a different verb.
You look around the room and have a thought you probably shouldn’t say out loud:
If this is what it means to serve on a board, maybe I’m out.
You joined the board because you care about the mission. You wanted to offer your experience, exercise good judgment, make useful connections, and help an organization you believe in make good decisions. You didn’t join to spend a Saturday writing vision statements by committee.
If you’ve felt this way, or are an executive who hears something similar from your board members, it is worth paying attention.
It may not mean there’s a lack of commitment. It may mean the process is asking everyone to do the wrong work.
Strategic planning isn’t supposed to be easy. Good strategy requires candor, surfaces disagreement, and forces choices that are much easier to avoid than to make.
But there is a difference between work that is difficult and work that is pointless.
A difficult conversation might explore whether the organization should serve one community more deeply or expand into three new ones. A pointless conversation asks eighteen people to improve the wording of a paragraph no one will remember.
Too many planning processes confuse participation with progress. Everyone gets a marker; everyone contributes a sticky note. Unfortunately, all too often the same ideas circle the room, so no real choices are made, and the resulting plan parrots back a polished version of what the organization was already doing.
Leaders who get frustrated by this aren’t necessarily impatient or disengaged. In fact, they are probably the people most aware that everyone’s time is being wasted.
The board has an essential role in strategy. The board should help establish direction, weigh priorities, apply judgment, and hold leadership accountable for results. Board members should understand what the organization is trying to achieve, why it chose that path, and what it decided not to pursue.
That is very different from asking the board to conduct staff-level research, draft every section, design the work plan, or debate every measure.
Ideally, staff leaders bring the research, field evidence, and a point of view on the organization’s direction and priorities to the process.
There are two bad extremes here. At one end, the staff creates the entire plan and brings it to the board for a ceremonial thumbs-up. At the other, the board is handed a blank page and asked to create the organization’s future from scratch.
Neither approach makes good use of the people in the room.
Staff leaders should bring subject matter expertise and familiarity to the work. They understand the programs, people, budgets, systems, and day-to-day realities that determine whether a strategy can succeed. Board members should bring perspective, pattern recognition, community knowledge, professional experience, and a duty to think about the organization as a whole.
These are different jobs, and a good process needs both.
Participation is not the same as engagement. Asking everyone to help write everything is participation. Giving the board enough context to make a consequential choice is engagement.
Most painful planning processes break down in a few predictable ways.
They start with a blank page. Board members are asked broad questions like “Where should we be in five years?” without enough information about what constituents need, what is changing, what the organization does well, or what its finances can support. The answers may be sincere, but they are mostly guesswork.
They avoid trade-offs. Every idea is affirmed; every priority is included. No one wants to tell a passionate board member that a worthy suggestion is not the right direction. So, the plan grows longer while the strategy gets weaker.
They spend more time on words than meaning. Language matters, but wordsmithing is seductive because it feels safer than choosing. It is easier to debate whether a goal should say “expand” or “increase” than to decide which program will receive less funding next year.
They stop at the document. The plan is approved, formatted, distributed, and quietly detached from the budget, the calendar, and the board agenda. Six months later, no one can say what changed because of it.
This is how strategic planning becomes performative: everyone participates, no one decides, and the organization keeps moving in the same direction.
A useful process doesn’t start by asking the board to supply answers out of thin air. It starts with the work required to frame the right questions.
Before the board meets, someone has talked with constituents, gathered input from staff, reviewed relevant data, examined the organization’s capacity, and identified the choices that seem most important. Board members receive enough context to understand the landscape without being buried in a hundred-page briefing book.
Then the board is asked to do board work:
The discussion should be structured around decisions, not topics. “Let’s talk about growth” can fill an afternoon. “Should we deepen our work in two current communities or enter a third next year?” gives the conversation somewhere to go.
The same principle applies after the retreat. Staff can translate the direction into language, priorities, measures, budgets, and work plans. The board can review whether the final plan reflects the choices it made, then use future meetings to examine progress and changing conditions.
Board members should leave the process knowing what they decided, what will happen next, and how they will know whether it worked.
If you are losing patience with a planning process, you do not have to swallow your frustration or deliver a speech about everything that is wrong. Start with a few direct questions:
What decisions does the board actually need to make?
Which parts of this process belong to the board, and which belong to staff?
How will this plan change the budget, the calendar, and future board agendas?
Those are not hostile questions. They are governance questions. Asked at the right moment, they can pull a conversation out of the weeds and back toward the work the board is there to do.
You can also speak privately with the board chair or executive director. Name the pattern plainly: the process feels repetitive; the choices are unclear; the board is doing work better handled by staff; the plan does not appear connected to decisions. Candor before quitting! Before you quit, give the organization a chance to fix what is often a fixable problem.
Of course, sometimes frustration is the sign of a deeper issue. If leaders won’t make choices, clarify roles, or use the plan after it is approved, leaving may be the right decision. A board seat is a real commitment; you are entitled to expect your work to matter.
But before you go, ask the question everyone else may be thinking: What are we actually trying to decide?
The real product of strategic planning is not a document. It's a shared understanding of why the organization is here, what matters most now, and what people will do differently as a result.
A useful strategy connects purpose to choices and choices to action. You should be able to see it in the organization’s calendar and budget. You should hear it in the way leaders explain priorities. You should feel it when a new opportunity appears and the organization can say yes or no without starting the entire debate again.
This kind of purposeful planning reminds people why they agreed to serve in the first place: because the mission matters, the choices matter, and their judgment can help the organization move forward.
If strategic planning makes good people want to leave, don’t assume the people are the problem. Fix the process first.
Is your board planning process creating clarity—or just creating fatigue? Let’s talk about how to make strategy useful, honest, and worth people’s time.