How to Prioritize Strategic Initiatives Without a Political Fight

Every leadership team generates more initiatives than it can fund. That is not a planning failure — it is what a room full of capable people does when asked what would move the strategy.

The failure is what happens next: the list gets published intact, everything is nominally a priority, and the initiatives that actually get done are the ones whose sponsors have the most political capital. Prioritization is the step that prevents that.

Here is how it runs inside the Align stage of a planning process.

Start from goals, not from the existing project list

Prioritization is only meaningful if the candidate set was generated from your strategic goals. If you start from the list of projects already in flight, you will end up ranking your current commitments and calling it a strategy.

For each strategic goal, ask what bodies of work would move it. Include options nobody is currently running. Then bring in the in-flight projects as candidates on the same footing as everything else — including the ones that have been quietly underway for two years.

Make sure each candidate is actually an initiative

An initiative has a start, an end, and a definable result. Ongoing functions are not initiatives, and neither are aspirations.

• Not an initiative: "Improve internal communication."
• An initiative: "Stand up a monthly cross-department operating review with a fixed agenda."

If a candidate cannot be described as work that finishes, it cannot be scored, owned, or budgeted — and it will absorb effort indefinitely without ever being reviewable.

Score impact and effort in the open

Two dimensions carry most of the decision:

Impact: how much would completing this move the strategic goal it sits under? Not how important it feels — how much the goal's own metric would move.

Effort: what will it genuinely cost in money, in the time of people who are already fully committed, and in dependency on other work.

Score each candidate on both, as a group, with the numbers visible. The scoring model matters much less than people expect. What matters is that the trade-off is made explicit in the room instead of settled afterwards by whoever controls the resources.

Two things to watch:

• Effort is systematically underestimated for initiatives sponsored by the person doing the estimating. Ask a second function what it would cost them.
• Impact inflation happens when a candidate is scored against how much the sponsor cares rather than against the goal metric. Bring the metric back into the conversation each time.

Fund a short list — and defer the rest explicitly

Once the scores are visible, draw a line. Above it: initiatives that get funded this year, with people and money attached. Below it: initiatives that are deferred.

The word deferred has to be said and written down. Ambiguity below the line is what kills prioritization. If an initiative's status is unclear, its sponsor will keep resourcing it informally, drawing effort away from the funded list without appearing on any plan.

A deferred initiative is not rejected. It is a candidate for the next cycle, and it gets revisited at a quarterly review. That is what makes the deferral acceptable to the person who proposed it.

Sequence what's above the line

A funded list is not a starting gun. Dependencies and shared capacity mean some initiatives have to wait even though they are approved.

Sequence by dependency first, then by which teams are carrying more than one initiative at a time. A team running three funded initiatives simultaneously is really running none of them.

Attach an owner, a measure, and a budget to each

Prioritization is not finished until each funded initiative has:

One owner. A single name, not a committee and not a department. The owner reports progress in the monthly governance review, which only works if there is exactly one person to ask.

A progress measure. Distinct from the goal's KPI. The goal metric tells you whether the outcome is moving; the initiative measure tells you whether the work is happening.

A budget line. Dollars and people's time. An initiative with no budget is a wish that will be blamed on execution later.

Together with the strategic goals, this is what makes up the official strategic plan document — the artifact the governance cycle runs against.

Revisit priorities on a cadence, not at next year's retreat

Priorities set once a year and reviewed once a year are priorities you cannot correct. The quarterly review exists to ask three questions of every funded initiative:

1. Is the goal metric moving?
2. Is this still the right bet, given what we have learned since?
3. What are we stopping?

A governance cycle that never stops anything is not governance; it is a status meeting. Stopping an initiative that is not working is the mechanism that frees capacity for a deferred one — and it is the single most visible signal to the organization that the plan is real.

Why teams avoid this step

Prioritization creates a moment where a named person's proposal does not get funded, in front of their peers. That is uncomfortable, and the discomfort is why so many plans ship with twenty priorities.

It is also the point of the exercise. Research on strategy execution consistently puts failure rates between 60% and 90%, and an unprioritized initiative list is one of the most reliable ways to land in that number: effort spread thin enough that nothing visibly changes, with no way to tell which bet failed.

A facilitator helps here for one structural reason. Someone has to hold the process while the leadership team argues productively, and a member of the team who also sponsors initiatives cannot do both at the same time.