How to Run a Weekly Review in 25 Minutes (The Founder's Template)

The weekly review is the single highest-leverage productivity ritual we know about. It compounds, it stays cheap, and the operators who run it consistently out-ship operators with twice the working hours and no review habit. It is also the ritual most operators skip — usually because the published templates take ninety minutes and assume a quiet Sunday afternoon that doesn’t exist.

This is the twenty-five-minute version. It runs every Sunday or Monday morning. It assumes you have a planning surface that holds your hierarchy. It assumes you have a real workweek with real interruptions. It does not assume you have a journaling habit, an inbox-zero discipline, or a quiet office.

We’re going to walk through the six steps in order with timing for each. Run it as written for four weeks. If it isn’t moving the needle by then, you have a different problem and we’ll tell you where to look.

Why the weekly review matters more than the daily routine

People over-invest in the daily routine and under-invest in the weekly review. The daily routine is execution; the weekly review is direction. A week of perfect execution in the wrong direction produces a week of motion you wish you could take back.

Specifically, the weekly review does four things no other ritual does.

It compares intent to reality. What did you say you’d do this week? What actually happened? The gap between those two is the most informative datum about how your system is working. You can’t see the gap without explicitly closing the loop.

It updates the hierarchy. Objectives shift. Problems get solved or reframed. New problems appear. The hierarchy stays alive only if it gets touched weekly. Skip a few weeks and you’ll discover it’s pointing at the wrong horizon entirely.

It primes the next week. A week that starts with a real plan ships more than a week that starts by reading email. The Sunday-evening or Monday-morning twenty-five minutes is what makes Monday’s first deep-work block actually happen.

It catches drift. Most operators who burn out can name, in retrospect, the week where the warning signs were visible. The weekly review is where you would have caught them in real time.

When to run it

Sunday evening or Monday morning. We’ve tried Friday afternoon (too tired, too much of the week’s content not yet processed) and Wednesday (too disruptive). Sunday-or-Monday is where the ritual lives most stably.

The specific time matters less than the consistency. Pick one. Put it on the calendar as a recurring event. Defend it as you’d defend a board call.

If you have kids and Sunday evening is a battle, Monday morning at 7am before the kids wake up is the right time. If you do your best thinking on Sunday afternoons after a walk, that’s the slot. The ritual is portable; the consistency isn’t.

Step 1: clear the inbox (4 minutes)

Open email. Open Slack. Triage anything that came in over the weekend. This is not a real inbox session — it’s a sweep to make sure nothing on fire is sitting in there that you need to know about before you do the rest of the review.

Three rules. Archive aggressively — most weekend email isn’t load-bearing. Reply only to anything urgent that takes under sixty seconds. Convert anything else into a task on the planning surface for the week ahead.

The reason this is step one rather than skipped: the brain can’t review the week with a parallel-processing thread running on “what did I miss?” Clearing the sweep makes the next twenty-one minutes actually thinkable.

Four minutes is the cap. If your inbox needs longer than four minutes on Sunday morning, run an actual inbox session before starting the review.

Step 2: read the past week (5 minutes)

Open the planning surface. Look at last week’s plan — the objectives you said mattered, the problems you said were the constraints, the tasks you said you’d do. Compare to what actually shipped.

The five-minute version of this looks like:

• What did I commit to do this week?
• What actually got done?
• What didn’t, and why?
• What surprised me?

Write it down. Two to four sentences per question is enough. The point isn’t elaborate journaling; it’s making the comparison explicit so it can inform next week.

Pay particular attention to the why question. Tasks that didn’t get done because they got deprioritized are healthy. Tasks that didn’t get done because the day disappeared into Slack are diagnostic of a system problem — see Top 10 signs your productivity system is broken.

Step 3: update the hierarchy (5 minutes)

Now revisit the hierarchy: life goals, objectives, problems, tasks.

Life goals. Skim, don’t edit. You’re not changing the long-arc ambitions every week. The skim is to keep them present in working memory so the rest of the review stays anchored.

Objectives. Three to five for the quarter. Are they still right? Usually yes. Occasionally an objective gets retired (it landed) or replaced (the world moved). Note any changes.

Problems. This is where most of the work happens. Are the named problems still the actual constraints? Are new problems showing up that weren’t on the list? Often a problem gets reframed — what you called we can’t articulate the value prop turns out to be we don’t know which segment we’re serving. Reframing is the high-leverage part.

Tasks. Look at the orphan tasks (anything not connected to a problem). Kill them or attach them. Look at the long-stale tasks. Kill them or revive them. The goal is to leave the hierarchy clean enough that next week’s planning can build on it.

Step 4: pick the week’s three (4 minutes)

The hardest step. Pick the three things that, if accomplished, would make next week count.

The three are not tasks. They are outcomes. Each one is the size of a problem solved or an objective meaningfully advanced. Each one is concrete enough to check at the end of the week — did it happen, yes or no.

For most operators, the three look something like:

1. Land the second customer pilot.
2. Ship the redesigned onboarding flow.
3. Have the difficult co-founder conversation.

Three is the discipline. Two is fine; four is reaching; five is wishful thinking. Operators who pick five outcomes a week consistently ship two; operators who pick three consistently ship 2.5. The math sounds backward and is right — concentration outperforms ambition.

Write the three down somewhere visible. The top of the planning surface. The whiteboard. A sticky note above the monitor. They are the thing you’ll evaluate against next Sunday.

Step 5: decompose to tasks (5 minutes)

Now turn each outcome into the specific tasks that will produce it. Each outcome needs three-to-six tasks. Each task is thirty minutes to two hours.

For Ship the redesigned onboarding flow, the tasks might be:

1. Final design review with the team (Monday).
2. Build the new step-3 flow (Monday-Tuesday).
3. Build the new step-4 flow (Tuesday).
4. Wire the feature flag (Wednesday).
5. Internal test with the team (Wednesday afternoon).
6. Ship to 50% of new signups (Thursday).

Each task is concrete. Each task is finishable. Each task has a rough slot on the calendar (don’t over-engineer this — Monday or Wednesday is enough).

This is also the right moment to ask: what could break this week, and what’s the recovery plan? Most weeks have one or two obvious risks. Naming them now is much cheaper than discovering them on Wednesday.

Step 6: calendar pass (2 minutes)

Open the calendar. Look at the week. Three checks.

Are the deep-work blocks defended? Two-hour blocks on Monday, Tuesday, Thursday at minimum. Move them if a meeting got accidentally scheduled into one.

Are the meeting clusters sane? Meetings should be back-to-back in afternoon clusters, not striped across the week.

Is one day genuinely off? If you’re working a six-day week, schedule the off-day explicitly. If you’ve already worked seven days in a row, the answer is “the off-day is overdue and now is the right time.”

Two minutes. The calendar is downstream of the plan; this step just makes sure the calendar is honoring it.

What twenty-five minutes buys you

Run this ritual every week for a quarter and the cumulative leverage is enormous. You’ll spend roughly five hours a quarter on review. Most operators we know who run it report at least twenty hours of recovered time per quarter, and a meaningful improvement in objectives shipped per quarter.

The mechanism is straightforward: the hierarchy stays alive, the week is intentional, drift gets caught in real time, and the calendar serves the plan instead of the other way around.

For the underlying philosophy, see What is a Personal OS. For the daily companion to the weekly review, see How to organize your day for maximum output.

Common failure modes

The review balloons to ninety minutes. Usually this means you’re using the review to do the work, not to plan it. The decomposition step is where this most often happens — you start thinking about how to ship the onboarding flow instead of just listing the tasks. Park the thinking; finish the review; do the thinking in the deep-work block on Monday.

You skip a week, then skip the next. The streak matters. Missing one week doesn’t kill the ritual; missing two starts the slide. If you’ve missed two, run a quick recovery review on whatever day you have time, even if it’s Wednesday. Get back on the cadence the next Sunday.

The three outcomes are aspirational, not achievable. A common pattern when starting the ritual is to pick outcomes the size of a quarter, not a week. The fix is the post-mortem: at the next review, when one of the outcomes didn’t ship, ask whether it was achievable in five days or whether you were picking an objective by accident.

You stop trusting the hierarchy. This is the system-rot pattern. If two consecutive reviews leave you feeling that the hierarchy doesn’t reflect reality anymore, that’s a signal to spend extra time on Step 3 — usually a problem has been reframed and the rest of the hierarchy is drifting around it.

The minimum viable version

If you don’t have twenty-five minutes, the absolute minimum is ten:

• 2 min: clear inbox sweep
• 3 min: read the past week
• 3 min: pick the week’s three
• 2 min: calendar pass

You skip the hierarchy update and the task decomposition. That’s not great long-term — the hierarchy will drift — but it’s better than skipping the review entirely. The hierarchy update can move to a longer monthly review.

The full twenty-five-minute version is what you should aim for. The ten-minute version is the recovery move when you’ve fallen off.

A small note on the partner review

If you have a co-founder, a spouse, or a close work partner, consider running a parallel weekly review with them — even a short version. Fifteen minutes on Sunday evening comparing notes about the week ahead surfaces aligned priorities and catches the gap between what each person thinks the other is doing. The compound effect over a quarter is real: fewer dropped balls, fewer surprise conflicts, less of the I thought you were handling that tax. It doesn’t replace your own review; it sits beside it.

TL;DR

Twenty-five minutes, six steps, every Sunday or Monday morning. Clear the inbox. Read the past week. Update the hierarchy. Pick the week’s three outcomes. Decompose to tasks. Calendar pass.

Run it as written for four weeks. After four weeks, you’ll know whether it’s earning its time — and it almost certainly will. braindump.work was built so this ritual takes minutes, not hours: the hierarchy is one click away, the past week is right there in the Today view, and the new week’s tasks attach to problems with a drag.