A staff member arrives at the board meeting glowing. There is a chance to launch a new after-school program, or a satellite location, or a fee-based service that could bring in revenue. The energy in the room is contagious, and someone moves to approve it on the spot.
This is exactly the moment a board earns its keep. New programs are how nonprofits grow and stay relevant, but they are also how organizations overextend, blur their mission, and burn through cash they cannot spare. The board's job is not to say yes or no on gut feeling. It is to ask the right questions before anyone falls in love with the idea.
Why New Programs Deserve Board Attention
Adding a program is not the same as tweaking an existing one. It commits the organization to new costs, new staff, new risk, and often a new promise to a new group of people. Once launched, programs are politically and emotionally hard to shut down, even when they underperform.
A new program touches several core board duties at once:
- Mission fidelity. Does this genuinely advance the mission, or is it mission drift dressed up as opportunity?
- Financial health. What does it cost, and where does the money come from after the launch grant runs out?
- Risk. Does it create liability, regulatory exposure, or reputational risk?
- Capacity. Can current staff and leadership actually deliver it without breaking?
Management designs and runs programs. The board's role is to test the case, approve or decline at the right threshold, and hold the organization accountable to what it promised.
Set a Threshold So the Board Sees the Right Ones
Not every program tweak belongs at the board table. Micromanaging small pilots wastes everyone's time and pushes staff to route around you. Draw a clear line in policy for what requires board approval, for example any new program that:
- Commits more than a set dollar amount or percentage of the budget
- Requires new full-time staff
- Extends the organization into a new population, geography, or field
- Involves earned revenue, fees, or a new business model
- Carries meaningful legal, licensing, or safety requirements
Below that line, trust the executive director. Above it, the board weighs in. This keeps the board focused on decisions that genuinely reshape the organization.
The Questions Every Board Should Ask
When a real proposal comes forward, resist the urge to react to the enthusiasm. Ask for a short written business case and press on these points.
Mission and evidence
- How does this advance our mission and strategic plan specifically?
- What need are we responding to, and how do we know it is real?
- Is anyone already doing this well? Should we partner instead of build?
Money
- What is the full cost, including staff time, overhead, and startup expenses (not just direct program costs)?
- What funds it in year one, and just as important, in year three?
- If the launch grant disappears, does this program bleed the rest of the organization?
Capacity and risk
- Who runs this day to day, and what do they stop doing to make room?
- What could go wrong, and what is the plan if it does?
- What licensing, insurance, or compliance obligations does it trigger?
Exit
- How will we measure success, and by when?
- Under what conditions would we wind this down?
That last pair is the one boards skip most often, and it is the most protective. Agreeing on success metrics and an exit trigger before launch removes the emotion later. When a program is struggling, no one has to be the villain, because the board simply follows the plan it set.
Watch for the Common Traps
A few patterns show up again and again when good boards approve bad programs.
- Grant-chasing. A funder offers money for something adjacent to your mission, and the organization contorts itself to qualify. Restricted funding that does not cover overhead can cost more than it brings in.
- The founder's passion project. A beloved leader wants it, so the board waves it through. Enthusiasm is not a business case.
- Sunk-cost creep. A pilot underperforms, but because you already invested, you keep feeding it. Set the exit criteria up front to avoid this.
- Hidden overhead. The direct costs look modest, but the program quietly consumes finance, HR, and leadership attention that never appears on the budget line.
- Scope that only grows. What started as a small test becomes a permanent department with no one ever deciding to make it so.
Approve in Stages, Not All at Once
Boards often frame the choice as approve or reject. A smarter path is to approve in stages, which lets you support innovation while limiting downside.
- Fund a feasibility study or planning phase. Give staff a modest budget to test demand, cost, and partnerships before committing to full launch.
- Approve a time-limited pilot. Set a fixed budget, a defined population, and a review date. A pilot is a real decision with real limits, not a permanent commitment.
- Review against the metrics you agreed on. At the review date, look at the evidence, not the enthusiasm.
- Decide to scale, adjust, or sunset. Only after the pilot proves out does the program become part of the ongoing operation.
This staged approach protects the organization and, frankly, protects staff too. A pilot that ends on schedule is a success of good design, not a failure.
Document the Decision
Whatever you decide, record it well. The minutes should reflect that the board reviewed the business case, discussed cost, risk, and mission fit, and approved (or declined) with any conditions attached. If you set success metrics and an exit trigger, name them. Note who is responsible for reporting back and when.
This matters for two reasons. It demonstrates the board exercised its duty of care, and it creates a clear reference point when the program comes up for review. Good governance is largely the discipline of writing down what you decided and why.
After Launch: The Board Stays Curious
Approval is not the end of the board's involvement, it is the start of oversight. Ask management to report on the new program at agreed intervals, tied to the metrics you set. Keep the reporting light but honest. A one-page update on enrollment, cost, and early outcomes is worth more than a glowing anecdote.
If the program is thriving, celebrate it and fold it into the regular budget and dashboard. If it is struggling, revisit the plan calmly. The board's steadiness here, neither panicking nor clinging, is what lets an organization take smart risks over time.
The Takeaway
New programs are how nonprofits grow, but growth without discipline is how they falter. Set a clear threshold for what needs board approval, demand a real business case with full costs and a funding plan beyond year one, and agree on success metrics and an exit trigger before you launch. Approve in stages, document the decision, and check back against the plan. Do that, and your board can say yes to bold ideas with clear eyes, and say no when it needs to without losing anyone's goodwill.