Weekly Review is the core method in Gollius for moving from intention to stable next action. It sits between daily planning and longer-term direction, giving a reliable checkpoint so your week closes as a learning loop instead of a collection of unfinished efforts.
What Weekly Review is
At method level, Weekly Review means:
- collecting evidence of what happened;
- identifying patterns across work, attention, and friction;
- deciding what to keep, stop, or delegate;
- setting a small set of explicit anchors for the next week.
The result is not more information. The result is better selectivity.
Where it fits in the Gollius atlas
This method connects directly to:
- habits, because consistency is mostly about clear repetition;
- productivity focus, because attention is finite and often misallocated;
- wellbeing and self-regulation, because review without regulation can become rumination.
Related method pages are often used together:
- implementation intentions,
- habit systems,
- self-monitoring.
A practical model
Think in four layers:
- Load: what did I actually do?
- Meaning: why were those actions relevant?
- Friction: what repeated and blocked progress?
- Direction: what will I prioritize next week?
If you review only load, it becomes a completed-task list. If you review only meaning, it becomes narrative. If you review only direction, it becomes wishful.
The generic weekly flow
1) Capture
List outcomes and incomplete efforts in plain language with dates.
2) Group
Classify entries into:
- focus loss,
- dependency bottlenecks,
- repeated decisions,
- emotional load points.
3) Decide
For each cluster choose one path:
- keep and simplify,
- stop,
- defer with a clear condition,
- delegate with ownership.
4) Assign
Set 2 to 4 anchors. Each anchor gets:
- one action,
- one trigger or scheduled time,
- one completion check.
5) Align
Tell at least one person what changed, especially what you are dropping.
Running time and cadence
Use a 45- to 60-minute review on a fixed day.
- 10 minutes capture
- 15 minutes pattern grouping
- 15 minutes decision pass
- 10 minutes anchor setting
- 5 minutes communication and close
This cadence keeps the method practical when workload increases.
Distinguishing it from overload systems
Weekly Review is not a productivity identity project. It is an orientation method.
It is not motivational storytelling. It is a decision method.
It is not a place for self-punishment. It is a place for removing false commitments.
What can change after repeated use
Over 3 to 6 weeks you should see:
- fewer unresolved carry-overs,
- clearer boundary between urgent and important,
- fewer implicit promises,
- stronger consistency in what gets started and finished.
If you see no change, check if:
- anchors are too many,
- you skipped decision pass,
- boundaries are missing,
- carry-over list is unmanaged.
Misuses to avoid
Too many categories
When categories become a taxonomy, complexity is often hiding indecision.
Too much self-judgment
Review notes should describe behavior, not assign identity.
Substitution with shiny ideas
Replacing one stalled commitment with another exciting item often creates motion without progress.
Ignoring dependencies
Some outcomes fail because timing and external constraints changed, not because of effort alone.
Safety boundary
Do not use this method as a stress amplifier. If reviews trigger strong anxiety, sleep loss, compulsive checking, or social withdrawal, run a short version with:
- one anchor,
- one risk boundary,
- one external support action.
If distress remains elevated, simplify further and use qualified support.
Starter script
Use this opening sentence:
This week I will identify what actually moved me forward, remove what did not, and carry only 2 to 4 commitments into next week.
Then answer quickly:
- What was the highest-value result?
- What pattern consumed the most repeated attention?
- Which three commitments will I protect next week?
Do not wait for a perfect entry. The method improves by repeating cycles.
Mini example
In practice, start with one real cycle:
- capture 8 outcomes and 4 unfinished items,
- map two friction patterns,
- keep only two anchors and one boundary.
At week end, review whether you still have the same two anchors and whether one pattern was reduced in frequency. If not, simplify the anchors before adding any new method.
Closing
Weekly Review is a practical orientation method. Its value comes from recurring limits, not complexity.