Re-plan over reflection
Weekly review should optimize next-week execution, not just summarize the past.
MethodWeekly OpsReview Template
Weekly Review Template
A practical weekly review template that turns reflection into better next-week execution.
Rules That Make Review Effective
Review should be a decision session, not a long writing exercise.
Use 3 buckets
Complete/incomplete/hold is enough for fast weekly decisions.
Lock 3 behavior changes
End review with three concrete changes: remove, reduce, fix.
20-30 Minute Weekly Review Flow
Fix this sequence as your template to repeat with consistent quality every week.
- STEP 1
Sort into complete/incomplete/hold
A simple 3-bucket pass clarifies what to keep, cut, or revisit next week.
- Failure causes matter more than raw completion rate.
- Set revisit dates for hold items.
- STEP 2
Review A completion and carry-over causes
Diagnose whether delay came from overload or weak block design.
- If A completion is low, reduce next week's A volume.
- If causes repeat, adjust block length.
- STEP 3
Lock three start tasks for next week
Pre-commit Monday start tasks to remove first-day decision fatigue.
- Pair tasks with Monday focus blocks.
- Decide keep/stop for recurring routines.
Key Review Screen
Use this view to set up next week's starting structure quickly.
Common Mistakes
- Reviewing without updating next-week plan
- Repeating same A overload without root-cause fix
- Skipping pre-commit start tasks for Monday
Recovery Steps
- End review with three changes: remove, reduce, fix.
- Adjust next-week A target and place buffers first.
- Lock Monday first block with three start tasks.