When your organization needs to cut programs, the board's job is to decide whether cuts are necessary and to set the criteria that govern them — not to decide which specific programs get eliminated. That second decision belongs to your CEO, who has the operational knowledge to execute it responsibly. Boards that cross into program-selection are substituting their preferences for their executive's judgment, and they almost always make worse decisions as a result. Stay in your lane, make the criteria explicit, and hold the CEO accountable to them.
The board's role is to decide whether to cut, and to establish the criteria by which cuts should be made — not to decide which specific programs get cut. That second decision belongs to the CEO. If the board has established clear goals and has communicated that financial sustainability is non-negotiable, the CEO should be able to develop a reduction plan that the board can evaluate against those criteria. The board approves or rejects the plan based on whether it meets the board's requirements; it does not construct the plan.
This distinction matters practically. The CEO and staff know the operational reality of each program — which relationships would be damaged, which staff hold institutional knowledge, which cuts would destabilize adjacent programs. The board doesn't have that knowledge and shouldn't pretend to. What the board does have is the mission perspective: which outcomes are non-negotiable, which populations must continue to be served, and what financial floor the organization must stay above. That's the frame the CEO needs to work within.
Setting the criteria before the cuts are proposed
The best boards establish cut criteria before any specific program is on the table. This prevents the politicization that happens when criteria seem designed to protect or target particular programs. The criteria should be mission-rooted: programs that directly serve the core beneficiary population and demonstrate measurable impact get protected first; programs that are off-mission, low-impact, or heavily dependent on disappearing revenue are candidates for reduction or elimination.
Before asking the CEO for reduction options, the board resolves: "Any proposed reduction plan must (1) maintain services to our primary beneficiary population at no less than 80% of current capacity, (2) return the organization to a balanced budget within 18 months, and (3) preserve the CEO's ability to continue delivering on the outcomes the board has required. The CEO is authorized to determine how those requirements are met within the program portfolio."
What to do when the CEO's plan doesn't meet the criteria
If the CEO brings a reduction plan and the board believes it doesn't meet the criteria — it cuts too deep into core services, or it doesn't actually close the financial gap — the board should say so and send it back with specific guidance. What the board should not do is start substituting its own program preferences: "Keep the after-school program but cut the counseling program instead." That's management. The board's response should always be framed in criteria, not in specific program decisions.
In genuine financial crises where speed matters, the board may need to authorize the CEO to act with more latitude than usual — approving a range of cuts up to a certain dollar threshold without coming back for a second vote. That's appropriate emergency delegation, and it keeps decisions where they belong: with the person who has the operational knowledge to execute them responsibly.
Practical steps
- Confirm whether cuts are actually the board's call. In most cases, program decisions are management decisions — your CEO can restructure the portfolio without a board vote. The board gets involved when the financial situation requires formal policy action or when the CEO seeks board direction on criteria.
- Set the criteria before any specific program is named. Pass a resolution that establishes what any reduction plan must achieve: minimum service levels for core beneficiaries, a financial target, and a timeline. Do this before the CEO presents options — criteria set after a proposal lands will look like they were designed to reach a predetermined conclusion.
- Ask the CEO for a plan that meets your criteria, not for a list of programs to cut. The question to the CEO is: "Here are our requirements — bring us a plan that satisfies them." The question is never: "Which programs should we cut?"
- Evaluate the CEO's plan against your criteria, not against your preferences. If the plan meets the criteria, approve it. If it doesn't — it leaves a financial gap, or it cuts too deep into core services — send it back with specific guidance about which criterion isn't met. Do not substitute your own program selections.
- In a fast-moving financial crisis, pass a delegation resolution that gives the CEO authority to act within a defined range — for example, up to $500,000 in reductions — without returning for another vote. Set a deadline for the CEO to report back on what was done and what impact is expected. This keeps governance intact while giving the CEO the speed the situation requires.