Sylvics Apply for the beta
🧭 Weekly review in four stepsFramework
FRAMEWORK

🔂Weekly review in four steps

🚦 Status🗂️ Library
🏷️ Topics
frameworkproductivitysystems
❤️ Favorite⭐ Favourite

🧭HOW IT WORKS

My own procedure. Four steps, always in this order, each answered in sentences in the weekly note.

  1. Collect. Read the seven daily notes. What happened, without judging it yet.
  2. Compare with the plan. What did I say on Monday that this week was for? Was it?
  3. Name one pattern. One thing that happened more than once. A person, a time of day, an excuse.
  4. Change one thing. One, with a day attached. Then write Monday's first task.

Use when: Sunday evening, at about 18:15, for 25 minutes. It runs after 🔹 Sunday money check, because the week's spending is part of what happened, and before the call with Ines at about seven, which gives it a hard stop.

How: I read the four prompts aloud from Weekly review script. A question I only look at gets a nod. A question I hear gets an answer.

Why only one change

Three changes is a new system, and I am not allowed a new system. The better weeks of the year each began with one.

Seen from further off it is a control loop with a seven-day delay: sense, compare, adjust. That thought is parked as 🔍 The weekly review as a control loop.

When not to use it

  • Not for planning a quarter. It looks back seven days and forward seven. A quarter needs a different altitude and a different hour of the day.
  • Not on the Monday tram. Weeks 7 and 28 were reviewed in my head between Fennick and Greywater Docks, and both reviews concluded that things were roughly fine. They were two of the three worst weeks of the year.
  • Not as a verdict on the week. Step 3 asks for a pattern. A score is a different thing, and the weekly note already has one.

🔗LINKED FROM

🕸️CONNECTIONS

Weekly review scriptWeekly review scriptWeekly review in four ste…