Weekly Review: From Record to Next Week's Design
A once-a-week pass over the field notes you have piled up, choosing what you learned and what to try next.
- review
- habit
- recording
If you only write every day and never read again, the notebook is not a storehouse, it is a wastebasket. I keep a 30-minute review at the weekend. A review is less about reflection than about turning the accumulated pieces into the design of the next week.
Four review questions
- What was the sharpest scene on site this week?
- In connecting with people, what went well and what was lacking?
- Was there a moment when AI or a tool saved you time?
- If you try only one experiment next week, what is it?
The answers do not need to be long. Three lines per question is enough. If you shape one of them into a public post, the blog fills itself. The review becomes a content pipeline.
How to keep the review going
Do it at the same time, use the same template, and check it off in the calendar when it is done. Do not aim for perfect analysis. Deciding on "one experiment next week" is already a success. As experiments pile up, the way you work changes, and as the way changes, recording gets easier — a virtuous cycle.
A review is not self-blame. It is the design of next week. If this week was blurry, acknowledge that blur in one line and move on to the next design.
The distance between a review and a public post
Posting review notes as they are can be too private. Before publishing, ask two things: "Is this scene useful to a reader?" and "Would a specific person be uncomfortable?" If you post only where usefulness and respect overlap, the blog stays distinct from a diary.
Sometimes the experiment you pick in a review fails. That failure is material for the next review. The fact that you ran the experiment is itself evidence that the work has not stopped.