Planning When the Ground Is Moving

Most nonprofit strategic planning assumes the world will hold still long enough for the plan to work. That's a generous assumption in any decade and a poor one in this one.

A better forecast won't fix it. What fixes it is a plan built in layers that move at different speeds, each with a named owner, so that when part of the picture changes you know which part of the plan to open and who opens it. This is the same amount of thinking as traditional planning, organized so it survives contact with reality.

Layer	Reviewed	Who owns it	Example content
Core	Annually, as part of annual planning	Board owns; ED drafts	"We exist so every young person in our community has a safe place after school and a trusted adult who knows their name."
Outcomes (the Bets)	Quarterly, for progress	ED owns delivery; board reviews	"This year we're betting on expanding our mentorship program and diversifying beyond our largest funder."
Triggers (scenarios)	Standing item at every board meeting	Board watches; ED reports	"Any funding change above 15% of budget, or a leadership departure, triggers a targeted plan review."

Layer 1: the Core

Three to five years, revisited annually as part of your regular annual planning. It holds only what's fixed: mission, a small set of non-negotiable values, and the two or three outcomes you exist to move. Keep it short. A Core layer that runs past a page has operational detail in it that belongs a layer down.

The board owns this one. The ED can draft it, but ratifying what the organization won't compromise on is a governance act, and it belongs to the body carrying the legal and mission responsibility.

Layer 2: the Outcomes

Twelve months, reviewed quarterly for progress. This is where the strategy lives: the specific programs, partnerships, and initiatives you're betting on this year to advance the Core.

The ED owns delivery and reports against it quarterly. Looking at it four times a year instead of once means a changed funding relationship or a slipped timeline gets absorbed without the whole plan feeling broken. A missed quarter is information you get early enough to use.

Layer 3: the Triggers

Ongoing, and the layer most organizations skip. Write down in advance the specific conditions that mean the plan needs attention before the next scheduled retreat, then put that list on the board agenda as a standing item. Most meetings it takes ninety seconds. The board asks whether any of these have fired since we last met. The ED answers honestly.

Pick from this menu or write your own:

• A funding change above a set percentage of annual budget, commonly 10 to 15 percent.

• The departure of the executive director, or another role named specifically in your plan.

• A shift in community need large enough to show up in your own intake or referral data.

• The loss or gain of a partnership a program depends on to operate.

• A change in regulation or contract terms from a government funder.

• Two consecutive missed quarterly milestones on the same outcome.

What a review is

When a trigger fires, the instinct is to reopen the whole plan. Resist it. A full rewrite in the middle of a disruption is chaos with a cover page, and it burns board attention you'll need for the actual problem.

The review is narrow. Walk the outcomes layer and mark only the items the trigger touches. Give each one of two dispositions: action, meaning something changes now and someone owns the change, or oversight, meaning it stays as written but the board watches it every meeting until the picture clears. Everything the trigger doesn't touch stays where it is. You should be able to finish in one meeting.

That's what governance is in practice. Are we keeping this plan on the rails, with the executive director as our partner? An ED who expects the board to read every trigger as personal failure will stop surfacing triggers, and you'll hear about the third one instead of the first. A board that treats its ED as an adversary, or as a mercenary hired to deliver outcomes it would prefer not to discuss, gets the plan it deserves.

The five-step scenario stress test

Run this once, in about ninety minutes, on your single most plausible trigger. Board and senior staff together.

1. Name the scenario in one sentence, specific enough to plan against: "our largest state contract isn't renewed in the next funding cycle."

2. Put a number on it. What share of your budget, staff time, or people served is exposed? Write the figure down even if it's rough. Rough numbers change a conversation more than careful adjectives do.

3. Walk the first 30 days. Who calls whom, in what order, by when. Name people by name. This is where most groups discover they don't have an answer, and discovering it now is the point.

4. Sort the outcomes. Go down your outcomes layer and mark each one protect, pause, or rework under this scenario. Disagreement here is the exercise working.

5. Write the two decisions you can make today. Every stress test surfaces something actionable before the scenario arrives: a second person trained on a funding relationship, a reserve target, a conversation with a partner. Assign both, with names and dates, before anyone leaves the room.

Run it once a year on your top trigger, and again any time the trigger list itself changes.

A plan that can't move isn't protecting you...

It's exposing you, and it does it quietly.

Here's the mechanism. A rigid plan makes every change look like a failure, so people stop surfacing changes. The ED softens the quarterly report because the last honest one cost an hour of cross-examination. The board hears about a funding shift a quarter after the ED did. By the time the plan comes up for its scheduled review, the organization has spent months operating off a document that stopped describing reality, and nobody has said so, because saying so would mean conceding the plan was wrong. It wasn't wrong. It was written for a world that moved.

A plan that can move gives a board a legitimate, un-embarrassing way to say the ground shifted, here's the piece affected, here's what we're doing, here's who owns it. Bad news becomes an agenda item. And the protection lands on the mission instead of the paperwork.

The organizations we see handle disruption best did the harder work up front. They decided what they won't compromise on, built enough flexibility everywhere else that a change doesn't mean starting over, and settled who owns which call before anyone had to make one under pressure. Detailed five-year plans have very little to do with it.

If your last plan assumed a stable environment and you're operating in anything but, the plan may not be wrong. It may just need rebuilding around a different question. Not what will happen, but what we hold onto no matter what does, and who decides.