Your weekly review, from the record
Five minutes a week: what moved, what got stuck, what you didn't plan, and three priorities for next week, built from what actually happened.
A review from memory is a story about how the week felt. A review from the record is what actually happened. This guide sets up the second kind, and makes sure its lessons change next week.
What you need
- A week of captures: Capture anything.
- Optional: Project Management connected, if your work lives there.
1. Save the review recipe (5 min)
Weekly-review recipe
Run my weekly review from the record, not from guesses.
1. Read what changed in the last 7 days: finished, started and stuck tasks,
updated projects, and new notes. If Project Management is connected,
include work items and the current cycle.
2. Group everything by goal. Anything that serves no goal goes in its own group.
3. Tell me: what moved, what got stuck and for how long, and what happened that
I didn't plan.
4. Suggest one thing worth keeping as a recipe or template, and one lesson to
save as a note.
5. Propose my top three for next week, each linked to a goal.
6. Ask before changing or creating anything.2. Run it (5 min)
Pick a fixed time, the same every week, and ask:
Do my weekly review.
Read it critically. Accept the suggestions that are right and reject the rest; the recipe asks first, so nothing changes without you.
3. Close the loop (5 min)
A lesson you only think about is gone by Thursday. Make each one land somewhere:
| The lesson is about… | It changes… |
|---|---|
| How to do something | A how-to note |
| How you work | A template in the Project frameworks library |
| The AI getting something wrong | The recipe that caused it |
4. Finish projects properly (5 min)
When a project is done, don't jump straight to finalized. Move it to finished-reviewing and ask:
Close out the Wi-Fi project: what did I plan, what actually happened, and what should I keep or change next time?
Save the answer as a note linked to the project. That's how every project leaves something behind. The full version is Finish a project properly.
Check it worked
- Every line of the review points to a real record.
- It found at least one thing you'd forgotten.
- One lesson landed in a note, a template or a recipe.
Next
Do it again next week. The second review builds on the first, and that compounding is the whole point.
Then give what you've figured out a proper home: Build a how-to library your agents follow.