A weekly review, discussed elsewhere on this shelf, is deliberately narrow — it looks at one week's plan against one week's reality, and that narrowness is a feature, not a limitation, for the questions a weekly review is meant to answer. Some patterns, though, simply aren't visible at a one-week resolution: a gradual upward drift in a specific category's time cost, a seasonal pattern that only repeats every few months, or a habit change that helped in week one but quietly stopped working by week four. A monthly retrospective exists specifically to catch these slower-moving patterns that a weekly cadence structurally can't.
What a monthly view reveals that weekly reviews miss
Comparing four or five weekly summaries side by side — rather than looking at any single week in isolation — surfaces trends that are invisible week to week precisely because each individual week's change is too small to notice against normal variation, but the cumulative direction over a month is not. A category that grew by ten minutes each week looks like noise in any single weekly comparison and looks like a clear, real trend once four weeks are placed next to each other.
A monthly retrospective is also the right cadence for questions a weekly review is too frequent to usefully ask — is the current taxonomy (discussed in the personal-taxonomy guide on this shelf) still capturing the right categories, is a habit adopted a few weeks ago still actually happening, is a recurring meeting or commitment still earning its place on the calendar. Asking these questions every week produces mostly the same answer each time and wastes the review's time; asking them monthly catches genuine drift without the noise of week-to-week fluctuation. A related product reference is available at https://www.monitask.com/blog/crafting-an-effective-employee-write-up-form-a-comprehensive-template-guide/.
A workable structure for the monthly session
A monthly retrospective benefits from being noticeably longer and less mechanical than a weekly review — thirty to sixty minutes rather than five to fifteen — precisely because it's covering a wider, slower-moving set of questions that don't fit a quick checklist format. A useful structure looks across the month's weekly summaries for the largest category shifts, checks whether any habit or system change adopted during the month is still actually in use, and asks whether any recurring commitment on the calendar has quietly stopped justifying its cost since it was first added.
- Compare four to five weekly summaries side by side rather than reviewing the month as one undifferentiated block — the week-by-week comparison is what reveals trend versus noise.
- Reserve taxonomy and system-level questions (is this category still useful, is this habit still happening) for the monthly session rather than re-litigating them weekly.
- Check recurring calendar commitments specifically at this cadence — a monthly view is long enough to notice one that's stopped earning its place, and short enough to catch it before it becomes permanent by default.
- Give the monthly session real, protected time rather than squeezing it into a normal weekly review slot — it's answering a genuinely different set of questions and needs the room to do it.
Why the two cadences need to coexist
A monthly retrospective isn't a replacement for the weekly review — the two operate at genuinely different resolutions and catch different problems. Relying only on a monthly view loses the tight plan-versus-reality feedback loop a weekly cadence provides; relying only on a weekly view loses the ability to see slow drift until it's already become entrenched. The two together, at their respective natural cadences, cover a range that neither one alone reliably catches.
Together with the weekly review discussed elsewhere on this shelf, a monthly retrospective completes a two-tier system: fast feedback week to week, and a slower, wider check for the drift that fast feedback alone can't see. For additional background on this subject, consult Todoist’s productivity methods.