Most weekly review systems are designed by people who enjoy audits. They ask you to score your output, count your wins, tally the tasks you didn’t finish, and then somehow feel motivated afterward. I’ve tried that version for years. It works for about three weeks, and then it becomes one more thing I’m behind on.
The problem isn’t discipline. It’s that the review is asking the wrong questions. If your Sunday ritual is essentially a performance evaluation you wrote for yourself, of course you’ll start avoiding it. Nobody voluntarily sits down for a quarterly review with their own conscience.
So I rebuilt mine around three questions that take about twenty minutes total. What actually happened this week? What do I want next week to feel like? What’s one thing I’m carrying that I could put down? That’s it. No scores, no streaks, no red overdue badges.
### Why the scoring model backfires
When you attach a number to a week, you start optimizing for the number. I watched this happen to my own reading habit. I set a goal of two books a month, tracked it in a database, and within six weeks I was choosing shorter books. Not because I wanted to read them — because the count looked better. The metric quietly rewrote my taste.
The same thing happens with task completion rates. If your review praises you for closing items, you’ll start breaking work into smaller and smaller pieces so more of them get checked. You’ll avoid the slow, ambiguous projects that don’t produce satisfying checkmarks. And those are usually the ones that matter.
A review that measures should be a review that distorts. That’s not a personal failing. It’s just what measurement does.
### The three-question structure
My current setup is a single Notion page with three sections, and I fill it in on Sunday evening with tea and no timer. The first section is a short paragraph, not a list. Writing in sentences forces me to notice things a bullet list would flatten — that a project stalled because I was avoiding a conversation, not because I lacked time.
The second section is a mood, not a plan. I write one line: what do I want the texture of next week to be? Sometimes it’s “quiet and heads-down.” Sometimes it’s “out in the world, talking to people.” Then I look at my calendar and adjust, rather than the other way around.
The third section is the one that changed everything. I list what I’m still carrying — the unfinished email, the lingering guilt about a friend I haven’t called, the draft I keep reopening. Then I decide, deliberately, whether to do it, schedule it, or drop it. Most of the time I drop it, and the relief is disproportionate.
### What to do with the leftovers
Unfinished tasks aren’t failures. They’re information. If the same item rolls over four weeks in a row, that’s not a scheduling problem — it’s a signal that you don’t actually want to do it. I have a running list called “Things I’ve Decided Not to Do,” and it’s one of the most useful pages in my workspace.
I also keep a small archive of past reviews. Not to re-read for motivation, but because once a season I flip back through and notice patterns. The weeks I felt most scattered all had three or more evening commitments. The weeks I felt best had one long unscheduled block. That kind of insight doesn’t come from a dashboard. It comes from reading your own sentences six weeks later.
The template I use for this lives in the Willow Lane library, but honestly the structure matters more than the container. Three questions. Twenty minutes. A warm drink. If you’ve bounced off weekly reviews before, it probably wasn’t you — it was the audit.