ASB

Productivity6 min read

Weekly review in 15 minutes: three questions and a timer

The sixty-minute weekly review is the first gear to stop turning. I recommend the fifteen-minute version: three questions, a timer, and a fixed slot.

The official GTD weekly review checklist has eleven steps, from "collect loose papers and materials" to "be creative and courageous". David Allen suggests working through them early on Friday afternoon.

Nowhere does the document say how long that takes. The sixty minutes everyone repeats is not in the official material — it is folklore that settled on top of it.

That matters, because the duration is precisely what makes the weekly review stop happening.

The gear every system has and almost nobody turns

The weekly review is a fixed appointment where you look at everything you promised yourself, delete what has died, and decide what holds for the next seven days. It is the only part of an organisation system that repairs the system itself.

Without it the lists keep existing, detached from reality. By week three you open the list, see four items already done and two past their deadline, and stop believing it. The system is formally alive and functionally dead.

What fifteen minutes of reflection has already produced in numbers

The best evidence on structured reflection does not come from personal productivity. It comes from corporate training.

Giada Di Stefano, Francesca Gino, Gary Pisano and Bradley Staats tested what happens when you take time away from doing and give it back to thinking. In a lab study with 202 adults, those who wrote about their own strategy between two rounds of a reasoning game solved roughly 18% more in the second.

The number that matters here came from the field. At a call centre in Bangalore, employees in training spent the last fifteen minutes of each day writing about what they had learned. On the final training assessment they scored 22.8% above colleagues who spent those same fifteen minutes working.

Two honest caveats. This is a Harvard working paper, circulating since 2014 and still not peer-reviewed, and the setting is professional training, not your Sunday inbox. What it supports is modest and sufficient: the effect showed up at fifteen minutes.

The second piece is older and more direct. In 2011, Masicampo and Baumeister showed in the Journal of Personality and Social Psychology that an unfulfilled goal intrudes on thinking: people with an open commitment had their minds wander more while reading something unrelated to it. Writing a concrete plan for the commitment made the interference disappear — without the commitment being fulfilled.

That is what the weekly review does when it works. It executes nothing. It gives an address to what was loose.

Why the sixty-minute review is the first thing to fall

It is itself a heavy executive task. It means opening every list at once, holding decisions in parallel, and facing the true size of the backlog. It is the most expensive task of the week, disguised as maintenance.

It has no deadline and no audience. Nothing breaks on Monday if you skip it, and a task that only answers to you loses to any task that answers to someone else.

It is scheduled at the worst hour of the week. Putting the heaviest executive task on the calendar at the point of lowest energy is a design error, not a character flaw.

The entry price is too high. A one-hour review demands a free hour, a suitable place and the will to start, all three at once. Fifteen minutes demand fifteen.

The fifteen-minute script, on the clock

I recommend three questions, a visible timer and no attempt to make the system look tidy. When the alarm goes off, you are done, even mid-sentence.

What fifteen minutes will not cover

Fifteen minutes will not repair a broken system. If your lists have been corrupted for months, that is a clear-out rather than a review, and it wants one full afternoon, once. Nor will they answer the large questions — whether the project still makes sense, whether it is time to abandon something.

And the obvious problem remains: the fifteen-minute review has to start. It still depends on you remembering, on some Saturday, that something was booked for ten. A timer counts the minutes. It does not announce the hour.

Why I built on top of this

I ran the sixty-minute review for three years and managed it, perhaps, one week in four. The fifteen-minute one I have kept ever since, and the difference was not discipline. It was the size of the commitment.

What I wanted to put into ASB is the part the timer does not do. It arrives at the agreed hour, asks the three questions one at a time and writes the answers down — so the review is a short conversation, not one more item waiting on a list.

Meet ASB

Get it all out of your head, in one place

Inbox, tasks, projects, calendar and notes in the same place — fed by conversation instead of form filling. ASB is the second brain that answers back.

  • Every project starts with "To do" and "Done" boards.
  • XP, achievements and streaks for the days motivation does not show up.
  • Web and mobile apps, with the assistant in the middle.
Create my accountStart on the free beta plan.

Frequently asked questions

How long should a weekly review take?

The official GTD material sets no duration; the sixty minutes everyone repeats is convention, not doctrine. Fifteen timed minutes cover the essentials — what fell through, what has a real deadline, and what the one priority is. A short review that happens every week produces more than a complete review that happens three times a year.

What is the best day for a weekly review?

David Allen suggests early Friday afternoon, because there is still time to reach other people the same day. In practice, Friday afternoon is the hour of the week with the least willpower left in it. Friday morning, or Monday before you open messages, works better for most people.

I skipped the weekly review for a month. Do I need a bigger one to catch up?

No. The catch-up review is exactly why people never come back, because it is large, guilt-laden and postponable. Run the normal fifteen-minute review on the week ahead and ignore the backlog; whatever fell behind and still matters will resurface on its own within a fortnight.

Sources

About the author

Matheus Valadares

Founder of ASB

Developer and founder of ASB. He built Sofia after realising the problem was never a missing to-do app — it was having to remember to open one.

Keep reading

Back to the blog