The weekly review is not dead, you just do it wrong
My friend Derek was the most organized person in our shared office. He used three calendars, a bullet journal, and a task manager with color-coded labels. Every morning he planned his day down to fifteen-minute blocks. By the end of 2022 he had completed more projects than anyone on his team. He also felt empty and exhausted. The problem was not his system. The problem was that he never looked back. He never asked himself whether the work he did mattered. He never reviewed his own week.
Derek eventually found a way out. He started using a simple structure to stop and think for thirty minutes every Friday afternoon. He told me about a digital notebook he keeps, a personal reflection space he found at baderke us, where he writes down what he learned that week and what he wants to change. That single habit changed how he works. His burnout lifted. His focus sharpened. And the tools he already had started working better because he finally took the time to steer them.
A weekly review is the single most underrated productivity practice. Most people try it once, fill out a template with ten questions, abandon it after two weeks, and call it a waste of time. They are not wrong about their experience. But they are wrong about the method. The standard advice for a weekly review comes from David Allen’s Getting Things Done, and it works for people who already have a clean system. For the rest of us, that ten-step checklist feels like a chore, not a habit. We need a stripped-down version that fits a normal life with a normal attention span.
Why most weekly reviews fail
The typical review asks you to process your inbox, update your project list, review your calendar, and check your someday-maybe list. That is a lot of overhead. For a person who already struggles to keep their task list tidy, this feels like a second job. The failure happens because the review becomes another inbox to empty instead of a moment to think. I have watched dozens of people in workshops start a weekly review with good intentions and quit by week three. They treat it as a maintenance task, not a strategic pause. A review should answer one primary question: what did I learn this week that I can use next week? Answering that takes ten minutes, not an hour.
The four-question method
After experimenting with my own reviews for two years, I settled on four questions. I write them in a text file every Friday at 3:00 p.m. First: what went well this week? I name one or two things and describe why they felt good. Second: what went poorly? I name one or two things and write the specific trigger, not the blame. Third: what did I learn? This can be a technical lesson, a people lesson, or a lesson about my own limits. Fourth: what will I do differently next week? I commit to one change, no more. That is the entire review. It takes about twelve minutes. The action item is always small enough that I do not dread doing it on Monday morning.
How to protect your review time
The hardest part of a weekly review is not the content. It is the discipline to stop working. Many people treat Friday afternoon as a scramble to finish tasks before the weekend. They see a thirty-minute reflection as wasted time. I used to feel the same way. Then I started blocking the slot on my calendar as a meeting with myself. I set a timer. I close my email tab. I put my phone face down. The environment matters more than the format. If you try to review while you are half-watching a meeting or waiting for a build to deploy, your brain will stay in reactive mode and you will skip the real thinking. A clean break works better than multitasking.
A real example from a startup founder
I know a founder named Maria who runs a small team building educational software. She was burning out because she spent every week putting out fires and never stepping back to see the pattern. She started a weekly review based on the four questions. After six weeks she noticed that every time she skipped a team standup, two problems surfaced three days later. She had never tracked that before. She also noticed she said yes to every external meeting because she feared missing opportunities. The review gave her a factual record of her own behavior. She reduced her meetings by thirty percent in the next month. The review did not give her new productivity hacks. It gave her data about her own life, and that changed her decisions.
The hidden benefit of reviewing with others
I also learned that a personal review can be shared. I now do a ten-minute peer review every Friday with a colleague. We each talk through our four answers out loud. The act of speaking forces clarity. The other person notices patterns we miss. For example, I kept saying my worst moments happened on Wednesday afternoons. She pointed out that I always scheduled my hardest task on Wednesday at 1:00 p.m. I moved that task to Tuesday morning and the problem vanished. A shared review also adds accountability. If you tell someone you will change one thing next week, you are more likely to actually do it. The structure is the same. The only difference is you invite one other person to listen. That small shift turns a lonely habit into a human connection that keeps you honest.