12W App advanced use: how to conduct a weekly review (a new perspective)

Most people use 12W App to run a weekly review by opening their to-do list, checking off completed items, and then adding a few tasks for tomorrow. This process may look complete, but it usually answers only "How much did I get done?" It fails to answer the more important questions: Which task keeps consuming time, which kind of obstacle keeps recurring, and what should be stopped next week? A real review is not about counting the work; it turns a week's actions into judgments you can put to use immediately the following week.

Common Mistake #1: Treating the Review as a Roll Call of Tasks

The first common approach is to go through the to-do list item by item on Sunday night. Check off what is finished, move what is not to the following week, and then set priorities based on instinct. This approach has two problems. First, it treats "not completed" as a personal execution failure while ignoring changes in requirements, insufficient resources, or inaccurate estimates. Second, the list records only outcomes, so it usually leaves no record of how long tasks took, what got in the way, or which method you finally used.

When a week produces ten delayed items, ticking them off one by one creates at most one clear impression: there is a lot to do. But if you sort the delays into "unclear goal," "step too large," "dependent on someone else," "inserted at the last minute," and "simply underestimated the time," the problem shifts from an emotional judgment to a structure you can work with. Only a friction point you can categorize is one you can design a process to reduce. Otherwise, next week will probably just repeat the same blocker in a different form.

Common Mistake #2: Writing Reflections Without a Concrete Next Action

The second common mistake is to turn the weekly review into a diary: "It was a busy week," "Communication took a lot of time," "The project fell behind." These statements capture real feelings, but they contain no actionable information. Once the record stops at feelings, next week you have to work out all over again what matters most, what should be deferred, and which bottleneck to tackle first.

An effective review should include at least three parts: what happened, what method was used, and what to change next. The entry should not be "The client took too long to reply," but rather: "While waiting for the reply, I also organized the requirements and prepared a backup plan; next week, if there is no response within 48 hours of the first contact, I will switch to a brief confirmation checklist for follow-up." The former is only a description; the latter includes a time point, a trigger condition, and a replacement action. Without a next action, the review is just commentary on the past.

My Specific Method: A 30-Minute Review Across Four Levels

No personal experience is being claimed here; what follows is a practical operating framework you can apply directly. Step 1 is "look back at the week's outputs." Limit this to 10 minutes and list only what you truly delivered or moved forward that week