Our board keeps adopting strategies as goals. What's wrong with that, and how do we fix it?

When your board adopts strategies as goals, it makes genuine accountability impossible — and it quietly takes on work that belongs to your CEO. A strategy describes something your organization plans to do. A goal describes a condition you want to be true for the people you serve. When the board blurs that line, you can complete every item on your list without the people you serve being any better off. That's the failure mode: full compliance, no impact.

Here's why the confusion matters: if your "goal" is to "implement a community health worker program," you can complete that goal without improving a single patient's health. You hired the workers, you ran the program — goal achieved. But the people you serve aren't better off. Contrast that with a genuine goal: "reduce preventable emergency department visits by 20% among uninsured residents by December 31." Now the community health worker program is a possible strategy, but the CEO can also pursue other approaches, and either way, you know whether you succeeded based on what actually happened in the world.

Strategy-as-goal also tends to lock the board into yesterday's solutions. When you adopt a strategy as a goal, you've implicitly decided that strategy is the right one — before seeing results, before the landscape changes, before better options emerge. You've constrained management's ability to adapt, and you've taken on responsibility for a decision that should belong to the CEO.

How to spot strategies masquerading as goals

The diagnostic is simple: does the statement describe what you want to be true for your beneficiaries, or does it describe something your organization plans to do? Anything that starts with a verb like "implement," "launch," "develop," "expand," "hire," or "create" is almost certainly a strategy, not a goal. Goals, properly written, describe a state of the world — they answer the question "what will be different for the people we serve?"

Making the shift in practice

When your board is tempted to adopt a strategy as a goal, ask one question: what outcome do we believe this strategy will produce? That outcome — measurable, time-bound, and focused on beneficiaries — is your goal. The strategy is how you get there, and it belongs in the CEO's work plan, not the board's resolution.

This shift can feel uncomfortable at first, especially for boards used to reviewing and approving programs. But it actually gives your CEO more room to operate, not less. Once the board has named the outcome it cares about, the CEO can adjust the program, supplement it, or replace it with something better — and the board evaluates results, not compliance with a predetermined method. Most boards find this takes several revision cycles before the language feels right. That's normal. The practice of asking "is this a condition of beneficiaries or something we plan to do?" gets easier each time you run it.

Steps to correct course

1. Pull your current goals list and apply the verb test: any goal that starts with "implement," "launch," "develop," "expand," or "create" is almost certainly a strategy. Flag every one.
2. For each flagged item, ask: "What would be true for the people we serve if this strategy worked?" That answer is your candidate goal — make it measurable and time-bound.
3. Move the original strategy language into the CEO's implementation plan, where it belongs. Your board resolution should name the outcome; the CEO's plan names the approach.
4. Set a monitoring schedule: board reviews goal progress at least four times per year, never on the consent agenda. That cadence keeps the board focused on results rather than program approval.
5. When a board member proposes a new goal, run the same test before adopting it. Building this check into your governance calendar prevents the strategy-as-goal pattern from creeping back in.