The Weekly Review Workflow

What problem does this system solve?

The Weekly Review Workflow solves the accumulation problem: the tendency for unresolved decisions, incomplete tasks, and unexamined commitments to compound week over week, consuming increasing cognitive overhead and degrading decision quality.

Before implementing this system, my Mondays began with a 60-90 minute excavation: reviewing the previous week’s notes, checking half-finished tasks across multiple platforms, reconstructing the context I had lost over the weekend. This re-orientation was not productive work. It was the cognitive tax of a system that had no formal close-of-week process.

The issue compounds over time. Each week’s unresolved items carry forward, mixing with the new week’s demands. Within a month, the backlog of unexamined commitments is large enough to produce persistent low-grade cognitive anxiety, the sense that something important has been forgotten without knowing what. I needed a system that forced a weekly reckoning: not a productivity ritual but a structural checkpoint that prevented accumulation.

How does the system work?

The system operates in 4 sequential stages, completed every Sunday in approximately 45 minutes: Collection, Evaluation, Planning, and Archival.

Stage 1: Collection (10 minutes)

1. Open every active platform (task manager, email, calendar, notes, project boards).
2. Extract every open item, commitment, or loose thread into a single staging document.
3. Do not evaluate anything at this stage. The goal is completeness, not judgment.

Stage 2: Evaluation (15 minutes)

1. For each collected item, ask three questions:
   • Is this still relevant? (If not, archive it.)
   • Is this still mine? (If not, delegate or communicate.)
   • Can this be completed in under 5 minutes? (If yes, do it now.)
2. Items that survive evaluation are categorized: Active (requires action this week), Deferred (valid but not urgent), or Someday (interesting but not committed).

Stage 3: Planning (15 minutes)

1. From the Active list, select the 3 most important outcomes for the coming week.
2. For each outcome, identify the first concrete action required.
3. Block time on the calendar for each action. If it is not on the calendar, it is aspirational, not planned.
4. Review the coming week’s calendar for conflicts, preparation requirements, and energy management (no back-to-back deep work sessions).

Stage 4: Archival (5 minutes)

1. Move completed items to the archive with a completion note.
2. Move deferred items to the deferred list with a review date.
3. Clear the staging document completely. The staging document should be empty at the end of every review.
4. Write a single sentence summarizing the week: what was accomplished, what was learned, what carries forward.

What tools does this require?

The system requires deliberately minimal tooling: a task manager, a calendar, and a plain-text staging document, avoiding tool proliferation that itself creates cognitive overhead.

• Task manager (Todoist): For tracking Active, Deferred, and Someday items. The choice of tool matters less than the discipline of using one tool consistently. I chose Todoist for its simplicity and keyboard shortcuts.
• Calendar (Google Calendar): For time-blocking the three priority outcomes. The calendar is the commitment mechanism. Tasks on a list are intentions. Tasks on a calendar are scheduled.
• Staging document (Obsidian): A single markdown file that serves as the weekly collection point. I chose Obsidian because it is local-first, plain text, and searchable across notes. The staging document is ephemeral by design: created on Sunday, emptied by the end of the review.
• Archive (Obsidian vault): Completed items and weekly summaries are stored in a searchable archive. This archive serves two purposes: accountability (what did I actually accomplish?) and pattern detection (what keeps appearing in my deferred list?).

What are the results?

After 6 months of consistent weekly reviews, the system reduced my decision backlog from 23 unresolved items per week to 4, cut Monday re-orientation from 90 minutes to 15, and surfaced 7 recurring deferred items that I ultimately removed from my commitments entirely.

• Decision backlog reduction: From an average of 23 unresolved items entering Monday to 4. The remaining 4 are genuine complexities that require the coming week’s context to resolve, not carryover from neglect.
• Monday re-orientation: From 60-90 minutes of excavation to approximately 15 minutes of reviewing the plan created during Sunday’s review. The Monday start is now an execution session, not an orientation session.
• Deferred item pattern detection: The archive revealed that 7 items had appeared on my deferred list for 8+ consecutive weeks. This pattern meant they were not deferred, they were declined but not acknowledged. I removed all 7 from my commitments, freeing cognitive space that had been consumed by guilt rather than productivity.
• Weekly summary value: The single-sentence weekly summaries, accumulated over 6 months, provided a narrative of actual focus that was strikingly different from my perceived focus. I thought I was spending most of my time on AI engineering. The summaries showed I was spending most of my time on operational coordination. This insight drove a deliberate reallocation of my weekly schedule.