Strategy Only Works If Something Changes
Capabilities and management systems: the two choices that turn strategy into something your organization actually does.
In Part I, I talked about the difference between strategy and planning, and why mission-driven organizations so easily confuse the two. In Part II, I walked through the first three choices of the Playing to Win framework: what winning looks like, where to play, and how to win.
Those choices are the hard part, but they aren’t strategy yet. They’re intentions. Strategy becomes real when something in the organization actually changes, such as when the budget actually changes, when a meetings take a different shape, or when a leader says no to something good (which is hard!) because the strategy made the answer clear.
This post covers the final two choices in the cascade: the capabilities your organization needs to build, and the management systems that keep the whole thing from dissolving into business as usual.
Capabilities
This is where mission-driven organizations too often fool themselves. We confuse values with capabilities, good intentions with competence, and the contributions of gifted individuals with an organizational strength.
A capability is something you can do again and again, with normal staff, in a normal week, without depending on one person’s talent to make it work.
Nice slogans such as “We value community” is a value statement. Whether your team can consistently create environments where community actually forms, week after week, with whoever is on the schedule then that’s when you see a capability. The difference matters because your “how to win” choice is only as strong as what sits underneath it.
Now let me be clear, every strong organization has personalities that shape it. You might have a visionary leader or a creative thinker or even that linchpin who holds a department together through tried and true relational instinct. Organizations should be shaped by the people in them.
The problem starts when that person’s contribution takes on a shape of its own and the organization can’t continue without them in that role. If you’re building initiatives that only one personality can run, you’re building a dependency, not a capability. That person may be the creative driver behind the idea, but unless systems are in place to make it repeatable, it stays fragile. Fragile things don’t survive leadership transitions, which you will inevitably have
So when someone says “we’re good at X,” push on it. Ask whether it’s a system or a personality. Does that actually show up in the budget? Does it just survive on one or two all-star volunteers that dedicate so much of their free time on that program? Is it improving based on specific metrics or do you just have some sort of “gut feel” that it is going well? If the answers aren’t there, you’re looking at hope and a feel good story...not a capability.
If you call something a core capability, it has to show up across the organization, not just in the flagship experience. For example, if you claim you’re a teaching church but your children’s ministry runs on last-minute videos and functions more as Sunday morning babysitting then teaching is a brand line, not something the church can actually deliver. You can build capabilities. You just can’t pretend you already have them.
Management Systems
Most strategies die here, and usually it’s not because the choices were wrong but because nothing in the day-to-day really changed. The meeting stayed the same, the budget hasn’t changed in years, and the calendar keeps forcing decisions rather than your strategy forcing the calendar. The strategy became commentary.
If you want to know what an organization is actually committed to then look at what it protects. What does the leadership team spends time talking about? What keeps getting funded without debate, and what gets squeezed first when things get tight? That’s your strategy in practice, whether you meant it or not.
Management systems do a few things when they’re working. They shift attention toward lead measures, which are the behaviors and conditions that tend to produce results later, rather than just tracking lag measures like enrollment or giving that only tell you what already happened.
Management systems also do the hard work of forcing subtraction, which is especially hard in mission-driven organizations. Every program that you have has a constituency, every legacy effort has a story, and without a recurring moment where leaders decide what gets reduced or paused, nothing ever ends. And at the operational level, they clarify where you need tight standards (child safety, financial controls, compliance) versus where people need room to use judgment inside clear boundaries (pastoral care, student support, relationship building).
The Whole Cascade
This series started with a confession: I say “we need to be more strategic” more often than I want to admit, and most of the time what I mean is that we need a clearer plan. The plan was never the problem. The missing step is the set of choices the plan is supposed to serve.
Each choice in the cascade constrains the next. Together, they do something that mission and planning alone cannot: they force an organization to choose, and then to live with the choice long enough for it to matter. That’s hard in mission-driven work, where the moral pressure to say yes is constant and the needs are always real. But spreading thin is not faithfulness. It’s how good organizations slowly lose the ability to do anything with excellence.
If you’ve followed this series, you don’t need another framework. You need five answers on a single page. Then look at your calendar, your budget, and your next hire, and ask whether those answers actually show up anywhere.