Last updated: 2026-08-29
My weekly review has survived for more than a decade. I don’t rely on memory.
I use a checklist so the review is a repeatable process: answer the prompts, clear the inboxes, extract the lessons, and move on. I know, a checklist is not glamorous. It is why the habit is still here. The template cuts decision fatigue. Miss a week or two and you still know exactly where to start. You open the same list and go.
A lot of people fall off for a simpler reason. They think a weekly review has to be a 60- or 90-minute ritual. Brooks recommends setting a hard stop before you begin. Even 10 focused minutes is better than skipping it entirely. Constraints create focus. They make the habit easier to restart, because the bar is sitting down for 10 minutes, not clearing an hour you don’t have.
If you’ve been waiting for the perfect hour, try a 10-minute weekly review this Friday instead.
Ask better questions
A weekly review that only asks “what did I do?” is a recap. I want last week’s lessons to shape next week, the same way an agile retrospective does.
These four questions make the review actually useful:
What went well?
Write down the parts worth repeating so you can do them on purpose.
What could I improve next week?
Keep it small enough to try in seven days. One or two tweaks. Leave the life overhaul out of it.
What did I learn?
Capture it while it’s still useful. A lesson you don’t write down is a lesson next week can’t use.
What recurring frustration or annoyance showed up again?
Have you noticed the same irritation two Fridays in a row? Recurring annoyances are productivity signals. If the same friction shows up two or three weekly reviews in a row (poor sleep, a messy inbox, delayed admin work), it is a system problem asking for a small fix.
Does this sound familiar? Same annoyance. Same note to deal with it later. Same Friday.
Identify one recurring annoyance from the last month and design one tweak to reduce it. One tweak. If sleep kept showing up, change one thing about the night before. If the inbox kept showing up, that is a batching problem, which I’ll get to.

Stop dragging guilt into next week
You know the tasks you keep moving from week to week. They sit on the list and create guilt.
The maybe list is a pressure-release valve. Move those tasks to a someday/maybe list where they remain captured but no longer compete with real priorities. Brooks used an optional course as an example: useful, never urgent, always still there. I frame the list as a safety blanket. The idea stays. The week stays clean.
During your weekly review cleanup, move any task you’ve postponed three times to Maybe. You can pull it back later. It just stops competing with this week’s work.
Protect the work that matters
Weekly planning works better when you identify the 20% of tasks likely to create 80% of the impact, then protect those first.
Brooks emphasized that the 80/20 filter is about intentionality. You still do the other work. You give the high-impact tasks calendar priority before the small stuff fills the week.
Choose your top 20% tasks before you open email on Monday. Once the inbox is open, the week starts filling itself.
Then use the Rule of Three. Choose up to three major outcomes for the week, put them on the calendar first, and treat everything else as secondary. Some weeks you only have one or two big rocks. That’s still a win.
Brooks and I both come back to the same reminder. You can still do plenty of other tasks. You are protecting the most important outcomes so they don’t get squeezed.
What are your three big rocks this week?
Small tasks will take over if you let them. Email, texts, admin, inbox cleanup. React to them one at a time and digital clutter owns the week.
Batch them. Schedule buffer blocks where similar maintenance tasks get processed together for speed and focus.
Brooks has seen delayed expense claims become a bigger problem because they were never batched. Tiny items, left alone, until they weren’t tiny.
Add one 30-minute buffer block to next week’s calendar. Put the maintenance in there so it stops leaking into the hours you reserved for the 20%.
Let AI ask. You answer.
Brooks’s take on AI and weekly reviews is the one I want sitting next to the checklist. The future should not be AI silently generating a report while you stay passive. The best version keeps you actively reflecting, while AI helps you notice patterns, connect dots, and summarize next steps.
I still run my review with the checklist. I also let AI interview me.
My prompt:
“Act like my productivity coach. Ask me weekly review questions one at a time. After we finish, summarize everything in a bulleted list.”
I answer verbally while looking at my calendar. Then I use the summary to identify next actions and plan the week. The AI is an interviewer, a synthesizer, and a prioritization partner.
Copy that prompt into ChatGPT or whatever AI assistant you already use. Stay in the chair. Do the reflecting. Let the summary help you plan.
Do this on Friday
Set a 10-minute timer. Hard stop before you begin. Run the four questions.
Ten minutes. Start there.
Recommended for you
Want the full system? 25X is the flagship productivity system we teach.
Explore 25X →