Module 5: The Weekly Review
Plans rot without maintenance. This module installs the Friday Reset — a 30-minute weekly ritual that scores the week honestly, rolls work forward on purpose, and keeps your 90-day goals connected to your Tuesdays.
The Friday Reset
The Friday Reset is a 30–45 minute appointment with yourself, every Friday afternoon, that never moves. Not Monday — Monday is for starting, and starting without reviewing means repeating last week's mistakes with fresh enthusiasm. Friday closes the week properly so Monday starts clean.
The ritual has five steps, same order every week: 1) empty your head — write down every open loop, commitment, and nagging thought; 2) review the calendar — what happened, what got missed, what needs follow-up; 3) score the week's outcomes (next lesson); 4) roll work forward deliberately (lesson 3); 5) draft next week's outcomes and anchor map while this week is fresh.
Put it on the calendar as a real event and defend it like a client call. The first month feels optional; by week six it's the load-bearing wall of your whole system. The review is the difference between a system and a wish. Skipped reviews are how good plans quietly die by March.
The Friday Reset — five steps, same order every week
Empty your head
Write down every open loop, commitment, and nagging thought.
Review the calendar
What happened, what got missed, what needs follow-up.
Score the week's outcomes
1–5 each, with one line on why.
Roll work forward deliberately
Recommit, re-scope, or release — no drift.
Draft next week's outcomes
Outcomes and anchor map, while this week is fresh.
Score the week honestly
Take each weekly outcome and score it 1–5: 5 = done and done well, 3 = partial, 1 = untouched. Then write one line on why — not to punish yourself, but to debug the system. "Sales page draft: 2 — power blocks kept getting eaten by support tickets" is gold. It tells you exactly what to fix next week.
The review judges the system, not the soul. A bad week isn't a character flaw; it's data about a broken design. Maybe the container was unrealistic, maybe Thursday's anchor day collapsed, maybe the outcome was too big for one week. You're an engineer inspecting a machine, not a judge sentencing a defendant. Shame makes you avoid the review; curiosity makes you run it.
Track scores in one running note, week after week. After a month you'll see patterns no single week reveals: the same outcome rolling forward, the same Thursday collapse, the same over-ambitious Monday. Patterns are where the real fixes live.
Judge the system, not the soul
Score the week 1–5
Build brief
When did you last do a real weekly review of your business? What slipped through the cracks because you didn't?
Saved
Roll it forward — on purpose
Unfinished work needs a decision, not a drift. Every open item gets one of three verdicts. Recommit: it still matters, so it goes on next week's outcomes with a specific slot — not "try harder," a calendar block. Re-scope: it was too big; shrink it to a version that fits one week. "Launch course" becomes "film module 1." Release: it doesn't matter enough — kill it and feel the relief.
Watch for the zombie: the item that rolls forward three weeks running, never quite dying, never quite happening. Apply the two-week rule — if an outcome rolls twice without real movement, it gets re-scoped smaller or released. No third roll. Zombies eat planning energy every single week they shuffle along.
Rolling forward deliberately is also how you stay honest about capacity. If every week ends with five rolled items, your container math is wrong (Module 3) — you're planning 50 hours of outcomes in a 35-hour container. The roll-forward list is a capacity diagnostic. Read it.
A decision, not a drift
Three verdicts for unfinished work
| Verdict | Means | Example |
|---|---|---|
| Recommit | Still matters — give it a real slot | On next week's outcomes, with a calendar block |
| Re-scope | Too big — shrink it | “Launch course” → “film module 1” |
| Release | Does not matter — kill it | Feel the relief |
Build brief
What is one outcome that keeps rolling forward unfinished in your business? Should it be recommitted, re-scoped, or released?
Saved
The quarterly life check
Every 90 days, zoom out past the business. The weekly review keeps the machine running; the quarterly life check asks whether the machine is going somewhere you actually want to be. Ninety minutes, once a quarter, with a coffee and no phone.
Score five areas 1–10: business momentum, money, health and energy, relationships, and rest. Write one paragraph on each: what's working, what's not, and what one change would lift the lowest score. Then the big question: are my business outcomes serving my life, or is my life serving my business outcomes? Founders usually discover the drift here — the business grew exactly as designed, but the design forgot the person. A 7 in business and a 3 in health is not a 5 average; it's a warning light.
End by setting the next quarter's 3–5 outcomes (Module 1) and re-measuring the container (Module 3) — capacity changes with seasons, kids, launches. A system that never gets questioned becomes a cage. Question it quarterly.
Ninety minutes, once a quarter
The quarterly life check
Example for illustration — not real results.
Friday reset
This week's 3 wins: ___, ___, ___ What didn't work: ___ Next week's Big Three: ___, ___, ___ Calendar blocked: ☐
Lena has done her Friday Reset for a month. Every week, "redesign homepage" rolls forward untouched — it's week four. What should she do?