The strategic plan is adopted. It is approved, designed and published on the organization's website. And in practice, the work of the teams keeps living somewhere else: in departmental spreadsheets, project lists and meeting minutes.
This is almost never a question of willingness. It is a question of joints. Between the strategic document and the work of the week, a precise attachment point is missing. That is where the chain breaks, and that is where it can be repaired.
Two distinct objects are in play. The strategic plan carries the strategic directions and objectives that were adopted, over a horizon of several years. The work plans, or action plans, carry a department's concrete actions for the current year, each with an accountable person, a deadline and a weight. One gets voted on, the other gets kept current. The whole question is what connects them.
Following a strategic direction to someone's desk
Take an ordinary strategic direction: improve quality of life in the community. Under it, an objective: reduce response time to resident requests. Under the objective, a means: redesign the intake process for service requests.
So far, everything holds. The document says it clearly and no one disputes it. But ask someone in the organization what they are doing this week for that direction, and the answer does not come right away. Not because no one is working on it, but because the link between their work and the text of the plan was never written down.
That last step is what matters. A strategic plan becomes real the day a person opens their work list and sees which element of the plan each of their actions supports. Everything else in the exercise exists to make that step possible.
The joint sits on the action, not on the strategic direction
A common mistake is to attach an entire work plan to a strategic direction. It is the highest level, and therefore the most comfortable: everyone agrees and no one objects. The problem is that a strategic direction is too broad for a progress figure to mean anything.
The useful joint sits lower. Each action in the work plan attaches to the most precise element it serves, usually a means or an objective. A department can perfectly well contribute to three different objectives under two different strategic directions. That is normal, and even desirable: it is proof that the plan runs across departments rather than alongside them.
It takes discipline at the start. For every action on the list, one question: what does this action move forward in the adopted plan? If there is no answer, there are only two options. Either the action belongs to day-to-day operations and does not belong in the strategic work plan. Or the plan has a blind spot, which is valuable information to bring back to the senior leadership team.
Weighting is what gives a percentage meaning
When several actions attach to the same objective, they do not all carry the same weight. A process redesign that occupies a team for eight months is not worth the same as a brochure update delivered in two weeks. Without weighting, the progress figure on display becomes a misleading average.
Weighting does not need to be sophisticated. It needs to be deliberate and written down. The committee that assigns the weights is running a prioritization exercise in disguise: it says out loud what counts most toward reaching the objective. That conversation is often worth more than the number it produces.
Once the weights are set, progress on the strategic plan is calculated from the actual progress of the actions, not from a year-end impression. And when a department updates an action, the movement travels up to the objective without anyone having to chase it.
One accountable person per element, not a department
An action assigned to the communications department is assigned to no one. It is the most common trap in work plans, and the easiest to fix. A department does not answer an email, does not update an indicator and does not appear before a committee. A person does.
This does not mean the accountable person does all the work. The useful distinction separates the person who answers for progress from the people who contribute. Both roles are necessary, and blurring them produces plans where every element carries four names and no owner.
The test is simple. If an element of the plan has not moved in a quarter, do you know who to talk to? If the answer is a generic inbox or a department name, the element is an orphan.
When the vocabulary changes from one department to the next
The adopted plan speaks of strategic directions and means. The public works plan speaks of projects. The chief administrative officer's plan speaks of initiatives. Each has good reasons to use its own words, and no one wants another department's vocabulary imposed on them.
The answer is not to force a single language, but to agree on a shared lexicon for the organization. The levels stay the same everywhere, and the words that name them are the ones the organization chose. That choice is made once, it applies to every plan, and it is exactly what allows several plans to live in the same environment without anyone having to translate.
What it changes at reporting time
It is at reporting time that the chain gets measured. An organization whose work plans are attached to the strategic plan produces its report from data already entered, through the year, by the people who did the work. An organization whose plans live apart rebuilds its report in the fall, through reminders and follow-ups, with the gaps that implies.
The difference does not show in the final document. The two reports look alike. It shows in how long it took, in how much the numbers can be trusted, and in the ability to answer a follow-up question without going digging.
It also shows the following year. A plan whose chain holds keeps the history of its trajectory: not only where each element stands today, but how it got there. That history is what makes an annual review possible, and what keeps the conversation from restarting at zero every cycle.
Where to start, concretely
If you are picking up an existing plan, there is no need to rebuild everything. Take a single work plan, from a willing department, and attach each of its actions to the element of the plan it serves. The exercise takes half a day. It usually reveals two things: actions that serve nothing in the adopted plan, and objectives to which no action is attached.
Those two findings justify the exercise on their own. They give the senior leadership team a conversation it would not otherwise have had, and they get resolved before the next reporting cycle makes them visible to council or to the board.
Frequently asked questions
At what level should a work plan be attached to the strategic plan?
At the most precise element the action serves, usually an objective or a means, never a strategic direction. A strategic direction is too broad for a progress percentage to mean anything.
Can one department contribute to several strategic directions?
Yes, and it is desirable. A department contributing to three objectives under two different strategic directions is proof that the plan runs across departments rather than alongside them.
Should every department use the same vocabulary?
No. Agree on a shared lexicon for the organization, in the words the organization chose. The levels stay the same everywhere, which is what allows several plans to live in one environment without anyone having to translate.
How long does it take to attach an existing work plan?
Half a day for one department's work plan. The exercise almost always reveals two things: actions that serve nothing in the adopted plan, and objectives to which no action is attached.
Connecting your work plans to your strategic plan
Our three-part guide series on strategic execution covers the cadence, the structure and the indicators that keep the chain intact.
Free Guides to Execute Your Strategic Plan
To see how Planivore connects strategic directions, objectives and action plans in one place, book a 30-minute demo.
