The 20-minute weekly review system for solo founders

A task manager tracks individual tasks. A milestone tracks cumulative progress. But neither one tells you whether last week's tasks actually moved the project toward the milestone, whether you got distracted by comfortable work, or whether your direction has subtly shifted from where it should be. That gap is where solo projects quietly stall, and a weekly review is what closes it.

Why solo projects drift without a weekly reset

Most founders notice drift only after several weeks of it, when the project feels stuck and the backlog has grown but nothing visible has launched. The week-by-week view is too granular to see it coming. A weekly review creates a forced pause: you compare what you intended to ship against what you actually shipped, and that comparison is usually illuminating in ways that checking off daily tasks is not.

The reason most founders skip weekly reviews is that the ones they have seen at day jobs are corporate theater: long meetings, formatted templates, and questions nobody honestly answers. A solo review needs none of that. It takes 20 minutes, asks three honest questions, and produces one concrete output. That is the whole system.

The invisible cost of no review compounds fast. A week of low-leverage tasks feels productive while it is happening. Two weeks of them feel slow. Four weeks in and the project is psychologically stalled, the backlog is overgrown, and restarting takes twice the activation energy it would have with a consistent weekly reset. The review prevents this by surfacing the problem at week one, not week four.

The three questions that run the whole review

The first question is: what did I actually ship? Not what you worked on, not what you started, not what you moved 80 percent toward done. What finished, shipped, or was put in front of a real person? A feature you deployed counts. A blog post you published counts. A cold email you sent counts. Work you did but did not finish does not count. The constraint is intentionally strict because shipped work is the only output that compounds.

This question is uncomfortable when the week was full of effort but short on output. That discomfort is the point. It tells you the week had high activity and low leverage, which is exactly the pattern the review is supposed to surface before it repeats.

The second question is: did it move my milestone? Not all shipped work is equal. A week can be full of finished tasks that moved your product sideways: refactors no user noticed, landing page redesigns for a page nobody visits yet, infrastructure work that served perfectionism rather than customers. Anchor the answer to your current milestone, whether that is MVP, launch, first customer, ramen profitable, or 10k MRR, and ask honestly whether what you shipped this week brought you measurably closer to that gate. If mostly no, your prioritization algorithm needs recalibrating.

The third question is: what is the single most important task next week? Not a list. One task. The one that, if it were the only thing you shipped, would make next week a success. This is the hardest question because it requires ranking, and ranking requires accepting that everything else on the backlog comes second. It is also the most valuable output of the review: you go into Monday with a precommitted answer to the question that usually kills productive evenings, which is 'what should I work on tonight?'

When to do it and how long it takes

Monday morning beats Friday afternoon. The reason is practical: a Friday review ends with a plan for next week, and then the weekend lands between the plan and the execution. Context evaporates. A Monday review ends with this week's top task immediately actionable. You look back for five minutes, look forward for ten, set the trigger, and start the week without any re-deciding.

Twenty minutes is the upper limit for a healthy review. If it takes longer, the format has grown into template theater. The three questions need honest answers, not long ones. A sentence per question is enough. The task for next week is one line. Total writing time should be under ten minutes; the rest is thinking.

1. Monday, 5 minutes: open last week's completed tasks and read the list, not the effort behind it.
2. Monday, 3 minutes: ask whether those tasks moved your current milestone. If mostly no, your task selection was off.
3. Monday, 7 minutes: rank the backlog by impact-per-minute and identify the single most important task for this week.
4. Monday, 3 minutes: set the trigger by writing the task down, putting it in your inbox, or starting it right now.
5. Friday, 2 minutes (optional): jot down anything you learned during the week that should inform Monday's review.

Use your recap email as the review trigger

The biggest obstacle to a weekly review is remembering to do it. The second biggest is reconstructing what you actually shipped: digging through Git history or a messy task board to build the list from scratch takes time you do not want to spend on a Monday morning. Both problems have the same solution: a trigger that arrives in your inbox with the answer to question one already filled in.

shipsolo sends a Monday weekly recap email showing every task you shipped in the previous week, per project. The email arrives as the review trigger. You open it, you have your shipped-tasks list, and the review can start before your coffee is cold. Pair it with the impact-per-minute ranked board and an email task reminder for the week's top task, and the three questions turn from a 20-minute chore into a five-minute habit.

The weekly review is not a planning meeting. It is a compass check. Twenty minutes to make sure you are still headed in the right direction.

A review is only useful if it changes something

The failure mode of regular reviews is ritual without impact: you answer the three questions, write down the answers, and then reopen the backlog and pick whatever feels comfortable anyway. Reviews have to produce a concrete change to be worth the time.

The minimum output is one changed decision: a different task at the top of this week's priority queue than habit alone would have suggested. If the review confirms that direction is right and prioritization is sound, the minimum output is zero, and that is fine too. What the review cannot end with is a vague intention to 'do more marketing' or 'focus on retention.' That is not a task. A task is concrete, completable, and impact-scored. Leave the review with one.

Start this Monday

You do not need a template, a journal, or a special app to run a weekly review. Open last week's tasks, answer the three questions, identify one task for this week, and set a trigger so you do not forget it by Tuesday. That is the whole system. If you want the review to take under ten minutes, tools like shipsolo automate the lookup step: the Monday recap email hands you the shipped-tasks list so question one is pre-answered. The free tier covers two projects; Pro is 5 euros a month if you want the email task reminders and the impact-per-minute board across more projects. But the method needs none of that to work. It needs 20 minutes, three honest questions, and the willingness to let the answers change what you do next week.