Operating Cadence¶
Most organizations run a stack of direction-setting artifacts. A mission, a vision, a set of values, a strategy, annual goals, quarterly goals, and some weekly meeting where progress is meant to be checked. Each layer has its own ceremony and its own calendar, and almost nobody asks which of them earn their place.
This bundle asks. Every layer gets sorted into one of three grades. The grade is stated in the prose beside the claim rather than stamped on it.
Evidenced means randomised or meta-analytic evidence, or a peer-reviewed study with a disclosed method. Very little qualifies.
Convention means the practice traces to a named person's judgment or to one company's internal habit. Reasonable, widely copied, and never tested. Most of the stack sits here.
Folklore means it circulates everywhere and traces to nothing. A surprising amount of what gets quoted in planning meetings is in this category, including two of the most repeated statistics in management.
The grading is the point of the bundle, not decoration on it. Anyone can find advice on writing objectives. What is hard to find is an honest account of which parts have ever been shown to work. That absence is not accidental. Almost every popular source on this subject is published by a company selling goal-setting software or planning consultancy.
What you will find here¶
The sequence runs downward through the stack and then outward through the year.
The stack itself comes first, because the layers are not what most frameworks claim. The words mission, vision, purpose and strategy are used in mutually exclusive ways, and the two best-known frameworks invert each other's hierarchy. Before fixing a planning system it helps to know the vocabulary is genuinely unsettled, rather than something the team failed to learn.
Then the year. Strategy refresh, annual planning, quarterly goals, the monthly and weekly reviews, and the handoffs between them. The useful finding here is about lead time, and about how little is documented. Only two organizations have published a dated sequence, they disagree with each other, and one is a single-interview case study.
Then the repair. What to do with a system that already exists, has already disappointed people, and cannot simply be replaced.
What this bundle is not¶
It is not an argument against planning. Formal strategic planning has a real, modest evidence base. One mechanic in the whole stack has strong evidence behind it: checking progress often, out loud, in writing.
It is also not a framework. Nobody has published a head-to-head comparison of the named systems. The variables that appear to matter are not the ones the frameworks differ on.
In this section¶
| Page | Last updated |
|---|---|
| How the Planning Stack Fits Together What mission, vision, strategy and goals each actually are, where the definitions contradict each other, and which layers the evidence supports having at all. |
Updated 2026-09-24 |
| Running It When It Is Already Broken How to diagnose a planning system that has already disappointed people, what to change in week one, and what to remove rather than add. |
Updated 2026-09-24 |
| The Planning Year When strategy, annual plans, quarterly goals and the weekly check actually happen, and which parts of the calendar have evidence behind them. |
Updated 2026-09-24 |
| Glossary Plain-language definitions of the terms used across this bundle. |
Updated 2026-09-24 |
| Validation How claims in this bundle are sourced, graded, and checked, and what the grades mean. |
Updated 2026-09-24 |