Note-taking methods

The weekly review: twenty minutes that keep a system alive

Fifty-two chances a year to notice what you have quietly stopped doing.

The method: David Allen's habit, borrowed by everyone since

What you get
Whatever you set up in January is still running in June.
From
2001
Best for
Keeping whichever system you picked alive
Upkeep
Twenty minutes, same time each week

Every note-taking system in this series dies the same death, and it is never the one people expect. The notes do not get messy. The tags do not go stale. What happens is simpler: nobody reads them back.

A system you write into and never read from is a diary with extra steps. The weekly review is the smallest habit that fixes it, and it is the reason Getting Things Done, PARA and the bullet journal all contain one — under different names, doing the same job.

Twenty minutes, same time every week

The specifics matter less than the two constants: it is booked, and it is short.

Booked, because a review that happens when there is time never happens; there is never time. Put it in the calendar on a Friday afternoon or a Sunday evening and treat it like a meeting with someone you respect.

Short, because a two-hour review is one you will cancel next week. Twenty minutes with a hard stop is small enough to survive a bad week — and a bad week is exactly when the review is worth the most.

The four questions

What actually happened? Read the week back before you write anything. Not what you meant to do — what the days actually contained.

What did I say I would do and not do? No excuses in this answer, just the list. Most weeks it is three or four things, and two of them turn out never to have been real commitments.

What am I carrying into next week? This is the migration step, and it is the one that keeps every other list honest. Anything carried three weeks running deserves the question: is this a task, or a wish?

What should I stop? The hardest question, and the only one that ever improves anything. Systems accumulate; nothing prunes them but this.

Why writing the answers matters

A review done in your head is a review you will repeat next week, word for word, because nothing was recorded to argue with. Written down, three consecutive reviews become something no single week can show you: the same commitment slipping three times, the same "stop doing this" written twice, the week where everything was fine and you have forgotten why.

Reading three of them in a row is the actual product. Everything else is bookkeeping.

Mapped onto an outline

The template has three branches:

  • Daily log — one bullet per day, written at the end of it. Two minutes. This is what makes the weekly pass possible; the review is mostly reading rather than remembering.
  • This week — the four questions, as four bullets with room underneath.
  • Previous weeks — folded. When the week turns, drag "This week" down here and start a fresh one. Nothing is deleted, and the archive is one fold away when you want to read three in a row.

Drag the branch, do not retype it: the notes underneath each answer travel with it, which is what makes an old review worth opening.

What lands in your outline
  • The weekly reviewThe habit under Getting Things Done, PARA and the bullet journal alike. Same time every week, twenty minutes, no tidying.
    • Daily logOne bullet per day. Written at the end of it, not planned at the start.
      • Today
        • What actually happened
        • What I did not get to
    • This week
      • What actually happenedRead the daily logs above before answering.
      • What I said I would do and did notNo excuses in this bullet — just the list.
      • What I am carrying into next week
      • One thing to stopThe hardest bullet on the page, and the one that pays.
    • Previous weeksMove the branch above down here when the week turns. Reading three of these in a row is the real review.
    • How to run it

Folded bullets open with a click; every line is yours to rename or delete. Open it →

Running it alongside the others

If you already use one of the other systems, the review is where they connect:

  • Getting Things Done — empty the inbox, check every project has a next action, read Waiting for, read Someday.
  • PARA — read Projects, and move anything finished into Archive.
  • Bullet journal — the monthly migration is this habit at a larger size.
  • Zettelkasten — read one branch at random and see if the notes below still belong there.

Twenty minutes covers any one of those. It does not cover all four, and trying is how the habit dies.

What to skip

Skip the tidying. This is reading and deciding, not reorganising; if you find yourself renaming branches, you have found a comfortable way to avoid question four.

Skip the perfect template, too. Four questions and a hard stop will outlast any checklist with fourteen items on it.

All nine methods →