The Fix Nonprofit Boards Keep Skipping
Why programming committees drift, and how to bring them back
Every nonprofit programming committee faces one foundational decision, and most never make it: Does this committee exist to evaluate programs or to inform them? That single unresolved question explains nearly every dysfunction these committees produce. Without a clear answer baked into the charter, the committee has no governing identity. And a committee without a governing identity does not stay neutral. It drifts, and it can be costly.
BoardSource, the leading authority on nonprofit governance, identifies programming committees as among the most commonly misused board structures in the sector. The pattern is consistent: the closer a committee gets to operations without a defined mandate, the greater the risk of undermining staff authority and morale. The result is a committee that quietly undermines the staff it was designed to support.
When the Committee Has No Identity
Without a defined identity, the drift is not random, and programming committees reliably collapse into one of three failure modes.
The Idea Factory: Members do what engaged people do in a vacuum: they generate ideas. New programs are floated at every meeting, rarely filtered through the strategic plan or assessed for capacity. Staff spend cycles responding to proposals that were never viable. I have seen organizations spend three full board meetings debating a program idea that staff knew from week one could not be funded, did not fit the strategic plan, and would require a staff hire that was not in the budget. Without a clear committee mandate, there was no mechanism to say so early, and no clean way for staff to redirect the conversation without appearing uncooperative.
The Rubber Stamp: The committee becomes entirely passive. Staff present updates, members nod, nothing substantive is challenged. The committee exists on paper but contributes nothing to organizational decisions. Board members disengage, attendance drops, and the seat becomes a formality.
The Micromanager: The committee reaches past governance into operations, making it harder for staff to lead, plan, or push back. The result is staff fatigue, mission creep, and executive directors who spend more energy managing committee expectations than building community impact.
Writing in Stanford Social Innovation Review, nonprofit leader Alex Counts describes both the rubber-stamp and the micromanaging board as predictable failure modes and also details another mode: a “balkanized board,” a board consisting of people who are concerned only with one part of the organization, often the program they support financially. According to BoardSource's Leading with Intent 2020 report, 63% of nonprofit leaders cite board micromanagement as a source of frustration.
All failure modes share one root cause: the absence of a clear governing identity.
There is an uncomfortable truth worth naming here: Executive directors are not always passive bystanders in this dynamic. Some allow programming committees to default to one of these modes because it is easier to go along with engaged, well-meaning board members than to push back. Redirecting an enthusiastic but off-mandate trustee requires political capital that many EDs would rather preserve. The result is a slow accumulation of unresolved expectations on both sides.
Two Models That Actually Work
High-functioning programming committees most often operate in one of two clearly defined models. The distinction between them is not stylistic. It is structural.
Model One: The Strategic Lens
In this model, the committee's primary function is evaluative, not generative. Its job is not to create programs but to assess them. Members are equipped with clear criteria drawn directly from the strategic plan, and the committee serves as a standing internal auditor: Does this program align with our mission, our strategic plan, our current capacity, and our impact data? Is there evidence it works? Can we fund it sustainably? Members ask hard questions of staff rather than offering soft suggestions. This model works because it gives the committee genuine authority to challenge and interrogate, without pulling it into operational territory.
In my experience, this approach appears frequently in community impact committee structures, where members assess programs against defined outcome criteria before recommending continued investment. The rubric is the charter. It converts opinion into process.
As BoardSource's Recommended Governance Practices make clear, the board has a substantive role in developing, approving, and supporting organizational strategy, but staff is responsible for developing the annual budget and operational plans. Evaluation, not creation, is where the board's authority properly lives. This model works especially well for organizations with a defined program portfolio and a mature strategic plan. Good evaluative questions do not require program development expertise. They require curiosity, discipline, and mission alignment.
The ideal strategic lens committee member asks good questions under pressure: a former auditor, a policy analyst, a data-driven program officer from a foundation, or a senior manager who has evaluated business unit performance. What they share is comfort with evidence, tolerance for ambiguity, and the discipline to interrogate a recommendation without needing to replace it with their own.
Model Two: The Community Intelligence Engine
In this model, the committee's value is explicitly external. Members are selected because they have deep roots in the communities the organization serves, and their primary function is to bring field intelligence back to staff: What are residents saying? What service gaps are emerging? What are peer organizations piloting? Staff then translate that intelligence into programming decisions.
The committee is not a decision-making body. It is a structured listening post. This model works because it plays to an asset that board members genuinely have: community relationships and lived proximity to the people being served, without asking them to do something they are not equipped to do, which is design programs.
The ideal community intelligence committee member is embedded: a neighborhood association leader, a school principal, a faith community pastor, a small business owner on the block where the organization operates, or a former program participant. Their value is not analytical. It is relational. They know things that staff surveys cannot capture, and can surface emerging needs before they show up in data. Recruiting for proximity, not prestige, is what makes this model work.
Some organizations effectively blend both models, using community intelligence to surface emerging needs and the strategic lens to evaluate whether proposed responses are appropriate. The key is that the blend is intentional, documented, and understood by everyone involved.
Structural Fix: Separating Governance from Expertise
Some organizations have solved the problem by separating the function from the board structure entirely through program advisory councils: bodies that sit outside the formal board committee structure and are populated specifically with program expertise and community representation.
These councils can be more diverse, more community-facing, and more operationally relevant than a board committee. They can include service recipients, frontline practitioners, academic partners, and peer organization staff. Advisory councils advise staff directly and carry no formal governance authority, which means staff can receive input without being managed. The separation is clean, and it preserves the integrity of both bodies.
The board's programming committee, if retained, then occupies the Strategic Lens role: reviewing the advisory council's findings alongside staff recommendations and applying the governance filter that is appropriately theirs. It stops asking board members to be experts they are not, and it creates a legitimate home for the program expertise the organization actually needs.
A word of caution: Adding an advisory council is not a low-effort fix. It creates a new relationship to manage, a new body to convene, and a new communication channel between staff and the board. For lean organizations, the overhead can outweigh the benefit. This structure is most worth the investment when programming is genuinely central to the mission, when the board lacks community proximity, and when staff have the capacity to engage the council meaningfully rather than treat it as one more meeting to prepare for. For smaller organizations still building that capacity, starting with a redefined committee charter and a clear evaluation rubric will often get them further faster.
The One Question Worth Asking
Every executive director with a programming committee that feels rudderless should go directly to the board chair and ask: What is this committee's job, specifically?
If the answer is vague, that is the structural problem worth solving, and it belongs on the governance agenda, not the programming one. The National Council of Nonprofits recommends that committee assignments be based on the experience, skills, interests, and available time of board members, and that each member make a serious commitment to participate actively. That standard is impossible to meet when the committee has no defined purpose.
Here is where to start:
Define the committee's role. Is this committee a strategic evaluator or a community intelligence source? Write that answer into the committee charter. If the answer is both, choose one as primary and build explicit protocols around the secondary function.
Build the rubric before the agenda. Strategic Lens committees need evaluation criteria derived from the organization's strategic plan and impact framework. Without a rubric, every meeting defaults to subjective preference.
Recruit for the role you have actually defined. If the committee will operate as a Community Intelligence body, prioritize members with community proximity over members with impressive titles. If it will operate as a Strategic Lens body, prioritize analytical thinkers who can interrogate program logic.
Separate governance from operations in every meeting. Staff should present. The committee should interrogate. Neither should be doing the other's job.
Consider the advisory council structure. If programming is central to the mission and staff have the capacity to engage it, a program advisory council separate from the board may serve the organization better than a committee constrained by governance norms.
Name the political reality. Redefining a committee's charter mid-stream requires board capital. If raising the issue directly feels risky, bring it in through a governance self-assessment or a board retreat agenda item. The conversation is easier when it is framed as organizational improvement rather than individual critique.
Nonprofit organizations do not fail because their boards lack commitment. They fail, incrementally and sometimes dramatically, when structure cannot convert commitment into useful action. A programming committee without a defined mandate is not a neutral presence. It is an active risk to staff capacity, to strategic focus, and to the trust that executive directors need to lead effectively.
The solution is not to eliminate these committees. Many organizations need exactly what a well-designed programming committee can provide, whether that is rigorous program evaluation or grounded community intelligence. The solution is to stop treating committee formation as an act of governance and start treating it as an act of strategic design.
Lexicon Strategies Partner Ryan Roemerman provides strategic communications, public affairs, and business development for clients. He helps brands and changemakers tell their stories, build impactful programming, and move the needle with key audiences and decision makers.
Ryan has successfully launched programs and campaigns with partners like NBCUniversal, Delta Air Lines, the Atlanta Braves, The White House, The Coca-Cola Foundation, the National Center for Civil and Human Rights, George W. Bush Institute, Freedom House, and the American Medical Association Foundation, among others.