The One Sentence Missing From Most Strategic Plans

Every few years, organizations set aside time to make a strategic plan. Staff, board members, participants, and partners all weigh in. Priorities get debated. And at the end, there’s a document meant to guide the next three to five years.

Nobody really questions the logic behind this. Get the strategy right, and you’ll know what to do.

I used to buy into that too. But I’ve started to wonder if we’re asking strategic planning to do something it was never built for.

I think of a cross-sector health equity collaborative I’ll call Northgate Health Partners. Northgate consists of a health system, a housing authority, and a handful of community organizations working together to reduce ER visits tied to unstable housing. Their strategic plan set a clear goal: cut housing-related ER visits by 20% over three years, built around a new referral pathway between hospital discharge planners and housing case managers. It was in the MOU. It was on the org chart. It looked solid.

A year later, the numbers had barely moved. And nobody could say exactly why…not until they went looking.

Here’s the thing: the world moves faster than strategic plans do. Funding priorities shift. Policies change. Community needs evolve. A key leader leaves. A crisis nobody saw coming shows up. Even the assumptions that felt rock-solid during planning can look shaky a year later.

That doesn’t mean the plan failed. It means we’ve been asking it to predict the future, when its real job is to help us make better decisions under uncertainty.

Picture two different plans

Imagine two organizations, both just finished with strategic planning.

Organization 1 has a binder. It’s well-produced with priorities, goals, a theory of change, maybe a nice pull-quote from the executive director. It goes on a metaphorical shelf, gets referenced in board meetings, and mostly stays untouched until someone decides it’s time to plan again.

Organization 2 has something less polished but more alive. A short list of the bet they’re making and what has to be true for each one to pay off. A standing rhythm (maybe quarterly) where the team looks at what’s actually happening and asks whether those bets still hold. A running record of what they’re noticing along the way, so insight doesn’t evaporate the moment the meeting ends.

Same amount of thinking went into both. But only one of them is built to keep being useful as the ground shifts underneath it.

Let’s go back to Northgate for a second. Their plan was the first kind - a well-built binder. The referral pathway existed on paper, and everyone assumed that was enough. What nobody had built was a way to notice that referrals were getting made and then sitting for weeks, because housing case managers were already at capacity with no way to flag the backlog upstream. Discharge planners assumed the referral did its job. Case managers assumed someone would speak up if the backlog became a problem. Neither side could see the other’s reality, and the plan had no mechanism for that gap to surface until a full year of flat ER numbers forced the question.

A learning-oriented version of that same plan wouldn’t have looked wildly different on day one. Same goal, same partners, same referral pathway. The difference is what happens after launch: a stated expectation for how the pathway should work, a quarterly moment to check it against what’s actually happening on both sides, somewhere for the frontline staff to say what they’re noticing. That’s a small structural different. It’s also the difference between catching a stuck pathway in three months versus twelve.

Picture that version. Three months in, someone runs the quarterly check and sees referral response times creeping past a week. That’s not a crisis; it’s a data point. It prompts one conversation about whether case managers need more capacity or the pathway needs a tweak, and a small adjustment gets made in month four instead of a big one in month thirteen. The ER numbers start moving because the problem got caught while it was still a fixable-sized problem, not a full year of accumulated damage. Same time, same resources, same goal - the only difference is that someone was watching for the gap instead of finding it by accident.

That’s a small structural difference. But it’s the real difference between traditional and learning-oriented strategic planning. It’s not that one has a plan and the other doesn’t. It’s that one treats the plan as a finished answer, and the other treats it as a starting point for an ongoing conversation.

What a learning-oriented approach actually looks like

Traditional strategic planning circles one question: What should we do over the next five years?

It’s a reasonable place to start. It’s also a question nobody can answer with real confidence, no matter how many partner interviews you run.

A learning-oriented approach asks something different: What do we need to learn in order to keep making good decisions?

What might sound like a small shift changes the whole shape of the work. Here’s what it looks like in practice:

Turn your assumptions into if/then statements you can actually test. Every strategic plan rests on a story about how change happens. This new program will meet a need nobody else is meeting. This partnership will strengthen our impact. This funding stream will hold steady.

Left as vague confidence, those assumptions are useless. You can’t learn from something you never stated clearly. Stated as an if/then, they become something you can actually track: If we launch this program, then we’ll see X within six months. If that partnership is working, then we’ll see Y.

For Northgate, the unstated assumption, that case managers would have capacity to act on referrals within a week, is exactly what a quarterly pulse check would have tested. Said plainly, it’s obviously checkable. Left unsaid, it just quietly failed.

A simple exercise: for each major priority in your plan, write the sentence: “If we do this, then we expect _____.” That list becomes your organization’s real learning agenda, which might honestly be more useful than the plan itself.

Build a rhythm for pausing before and after moments that matter. This is where a lot of learning-oriented intentions quietly die. Everyone agrees assumptions matter, and then nobody ever revisits them until the next planning cycle rolls around three years later.

What works better is something smaller and more frequent. Before a major decision or a new phase of work, take 15 minutes to ask: What do we expect to happen, and what would surprise us? After it, ask: What actually happened, and what does that tell us about our if/then statements? Over time, write the answers down somewhere the whole team can see. Even a shared doc that grows over the year does the job. That running record is what keeps insight from disappearing the moment people leave the room.

Bring people together to ask what you know, not just what you want. Most engagement in planning processes amounts to “What do you want us to do?” That’s useful, sure. But it stops at opinion-gathering, and it usually only happens once, at the start.

A learning-oriented process treats engagement as something ongoing, built around a different question: What do we know so far? Gather a mix of staff, participants, and partners (not just the usual leadership voices) and ask it together. What are we missing? Where do you see this differently than we do? What tension have you noticed that hasn’t been named yet? People closest to the work often see the cracks in an assumption long before it shows up in a report, but only if you ask them in a way that treats their view as real data, not just a nice-to-have perspective.

At Northgate, the discharge planners and case managers had sensed the problem for months before it showed up in the ER numbers. Discharge planners joked about referrals disappearing into a black hole. Case managers were quietly triaging through whoever they happened to have a personal relationship with, because there was no other way to prioritize. That’s exactly the kind of signal a “what do we know so far” conversation, held quarterly with frontline staff instead of just leadership, would have caught early.

Why this matters more than it might seem

Organizations tend to judge a planning process by whether it produced a good document. I’d argue that’s the wrong measure entirely.

A better one: did people leave more able to make decisions than when they walked in? Do they have a shared, explicit understanding of the assumptions the strategy depends on? Do they know what to watch for, and have they built a rhythm for checking it?

Those capacities are what make a place useful 18 months in, when half the original context has already changed. The document doesn’t adapt on its own. The people do…if you’ve built that muscle into the process.

The honest tradeoffs

I don’t want to make this sound easier than it is. Most organizations I work with are already stretched thin, and “add a quarterly check-in” can sound like one more thing on a pile that’s already too tall. It doesn’t have to be a new meeting, though. The quarterly pulse can happen inside a staff meeting you already run. The running log can be a shared doc, not a system. The if/then list can live in the same planning session you were already going to have. The shift is less about adding time and more about spending 15 minutes of time you’re already spending differently.

There’s also the funder question. A lot of strategic plans look the way they do because a board or funder asked for exactly that. If that’s your reality, you don’t need to replace the plan they’re expecting. The if/then list and quarterly rhythm can run alongside the “formal” plan as an internal practice, informing how you actually operate even while the external document stays the same. Over time, what you learn from the internal practice often becomes some of the best materials for the next funder report anyway.

And honestly, there’s a vulnerability to this that’s worth naming. Writing down “if we do this, then we expect that” means occasionally having to say, on the record, that a bet didn’t pay off. That’s a harder thing to sit with in front of a board than a plan that just quietly falls out of date. But the alternative costs more in the end. It just costs it later, and less visibly.

Where to start, practically

If a full learning-oriented overhaul feels like a lot, you don’t need to rebuild your whole planning process to start. Pick one:

• Before your next planning conversation, turn your current priorities into if/then statements. Just that list is useful on its own.

• Start a shared, running doc where anyone on the team can drop a line when they notice something relevant. This is the beginning of a real record instead of a memory everyone half-remembers differently.

• Set a single 30-minute quarterly check-in on your calendar for the next year, built around the three questions in the check-in section above.

Small as these are, they shift the posture of the whole process, from get it right once to keep getting it right as things change.

A strategic plan doesn’t need to predict the future. It needs to prepare you to respond well when the future doesn’t cooperate. Which, if we’re honest, it never fully does anyway.