Time Core · Year Wheel · Module
The review rhythm
Where the organisation’s reviews sit in the year — the mechanism by which the whole framework gets used rather than consulted.
The idea
How it works
Every discipline implies a review cadence. Placed independently they cluster, and the organisation ends up spending one month in every quarter reviewing things.
This is where the framework becomes a practice rather than a document. Each object in each core has a rhythm, and unless they are placed in one calendar most of them do not happen.
Working with it
In practice
- 01
Put every cadence in one calendar
Goals, budget, brand tracking, competitor review, data quality, journey review. All of them, on one page.
- 02
Spread rather than cluster
Reviews landing in the same fortnight compete, and the least urgent is dropped every time.
- 03
Match the rhythm to the thing
Brand perception moves yearly and cash moves weekly. Reviewing both quarterly serves neither.
- 04
Protect the annual ones
They are the easiest to skip and the ones that catch slow drift, which is what nothing else catches.
One level in
The components of the review rhythm
A component is something that exists afterwards which did not exist before — a deliverable or a mechanism, not an intention.
Reviews landing in the same fortnight compete, and the least urgent is dropped every single time.
The other modules in year wheel
The cycle
What actually repeats annually — the demand pattern, the operating rhythm and the planning cycle — drawn rather than assumed.
LearnFixed points
The dates that cannot move: statutory deadlines, contractual dates, industry events and periods when nothing can be changed.
LearnLoad across the year
How work distributes against a capacity that is not constant, and where the year is already over-committed.
Learn