Two people around the same table say « objective ». The first means an intention for the next five years. The second means what they have to deliver before the holidays.
The instinct is to work out which one is right. That is the wrong question.
Neither is wrong. The problem is that the organization never decided which level that word names. And until it does, the plan will carry the ambiguity for its entire life.
The word is a choice, the level is a decision
There is no official vocabulary for a strategic plan. One municipality says pillars, another says themes, a college says strategic directions, a nonprofit says priorities. All four name the same thing.
That is a good thing. A plan's vocabulary should match the culture of the organization, not an imported template. A council that has always said « workstream » should not have to change words because a tool insists on it.
What is not negotiable is the structure underneath. A plan has levels, and each level answers a different question. The words change from one organization to the next. The levels do not.
That is why vocabulary arguments so often go nowhere: people debate the word when the disagreement is about the level.
The levels, and the words people give them
Here is the map. The terms listed are ones commonly found in public sector plans, not a closed list. Use the one your organization already uses.
Level 1, the direction
The question: where are we headed.
The words: strategic direction, goal, pillar, theme, priority, focus area.
This level is qualitative. It holds for the life of the plan and you never check it off. « Make the municipality an attractive place for young families » sits here, whatever word you put in front of it.
Level 2, the intended result
The question: what will have changed, and by how much.
The words: objective, strategic target, intended outcome, commitment.
This level is measurable and dated. It serves one direction. The test that settles almost every case: if you can answer « done » or « not done », you are at this level. If the only honest answer is « we are heading that way », you are at level 1.
Level 3, the way there
The question: by which path, out of the ones available.
The words: strategy, approach, initiative, workstream, lever, means.
This is the level people skip most often, and it gets its own section below.
The operational floor
The question: who does what, by when, with what budget.
The words: action, project, task, activity, deliverable.
This one belongs to the action plan, not the strategic plan. It is the most misunderstood distinction of the four, and it also gets its own section below.
The three rules that prevent almost all the damage
Once the words are chosen, there are three rules to hold.
One word per level. If « workstream » names level 3, no other word names level 3. No alternating between workstream, initiative and lever depending on who wrote the section.
One level per word. If « workstream » names level 3, it never names anything else. No « major workstreams » at level 1 and « workstreams » at level 3 in the same document.
One lexicon for the whole organization, not one per plan. That is the third rule, the least obvious of the three, and the one that comes due latest.
It sounds obvious written out. Open any adopted plan over forty pages and count the violations.
Why the lexicon has to cut across all your plans
A public organization never has just one plan. There is the strategic plan, and beside it a sustainability plan, a cultural policy, a workforce plan, a digital roadmap. A regional body has its land use plan. A college has its student success plan. Each one is written by a different committee, often two or three years apart.
If every committee picks its own vocabulary, every plan becomes an island. You can no longer compare progress on one against progress on another, or produce a consolidated view for senior leadership or for council. And the person who sits on two of them has to relearn the grammar of the second.
So the lexicon belongs to the organization, not to the committee that drafted one particular plan. Once it is settled, every plan that follows lines up with it. That is what lets them live side by side in one environment rather than in five sealed spreadsheets.
It is also what makes collaboration between plans possible: when an objective in the sustainability plan and one in the strategic plan carry the same name at the same level, you can link them, avoid duplicating an action, and report on both at once. A vocabulary that cuts across plans is not consistency for its own sake. It is the difference between an organization that manages five plans and one that runs a portfolio of them.
Level 3, the one everyone skips
Between the intended result and the concrete work, a floor is usually missing.
Take an objective to increase child care capacity. You can get there by supporting existing facilities, by changing zoning rules, or by building a partnership with the school system. Three different paths, three sets of teams, three risk profiles.
Organizations that skip this level go straight from the objective to a list of forty actions. They then cannot explain why those forty and not others. And on the day something has to be cut, there is no criterion for cutting intelligently: you cut by department or by dollar amount, not by strategy.
Naming the path makes a choice visible. It is also what lets you abandon that choice later without abandoning the objective.
The operational floor is not part of the strategic plan
Here is the most expensive confusion, and it survives any vocabulary.
The action, the project, the task, whatever you call it, belongs to the action plan. It attaches to a strategic level, but it is not one.
The distinction sounds theoretical. It is not. When operational items climb into the strategic plan, the plan swells to two hundred lines, council starts arbitrating projects, and senior staff spend their meetings explaining construction delays instead of talking about direction.
A useful rule of thumb: if the item has a budget, a deadline and a project lead, it belongs to the operational floor. It attaches to the plan, it is not part of it.
How many levels you actually need
There is no right number in the abstract. There is a number your organization can keep current, and that is the right one.
At two levels, you have the direction and the intended result, which suits most nonprofits and small organizations. At three, you add the way there, and that is the structure that fits most municipalities, regional bodies and colleges. At four, a layer of intent slots in between the last two, which earns its place when several tiers of governance have to see themselves in the same plan.
The natural instinct is to take as many levels as possible, out of a sense of rigour. That is a mistake. One more level is one more column to fill in four times a year by people who already have a job.
The exercise that settles the debate in an hour
Take your adopted plan. Pick ten items at random, from different sections. Ask three people from different departments to name the level of each item, separately and without consulting each other.
Compare the answers.
Where all three agree, the vocabulary is shared and there is nothing to do. Where they diverge, you are looking at exactly where the plan will jam at the first review. Take those one at a time, decide the level, and write the decision somewhere the next person will find it.
That page, the one that says which word names which level in your organization, is worth more than any downloaded template. It fits on a single sheet, it survives staff turnover, and it does not serve only the plan in front of you: it serves every plan that comes after it.
Settling on your own lexicon
Our strategic execution trilogy covers plan structure in detail, and what each level has to carry.
Free Guides to Execute Your Strategic Plan
To see how a plan is structured at two, three or four levels using your organization's own vocabulary, book a Planivore demo.
