Start weekly reviews…
Begin weekly reviews by stating what your tools helped you produce before reviewing tool configuration or optimization, to anchor tool evaluation in outcomes rather than activity.
When This Fires
- At the start of weekly reviews that include any tool or system assessment
- When weekly reviews consistently produce configuration changes but no output improvement
- When tool tinkering has become a substitute for actual production
- Complements Open weekly planning by reviewing plan vs. actuals… (weekly plan-vs-actual review) with the tool-specific assessment sequence
Common Failure Mode
Configuration-first reviews: spending 30 minutes adjusting Obsidian plugins, reorganizing Notion databases, and testing new Todoist features before ever asking "Did I ship anything this week?" The configuration changes feel productive but have no connection to output quality.
The Protocol
(1) Open your weekly review with: "What outputs did my tool stack help me produce this week?" List specific deliverables, not activities. (2) Rate the output quality: was it good? On time? Sufficient? (3) Only if output quality was below expectations → investigate tools as a potential cause: "Which tool-related friction contributed to the output gap?" (4) If output quality was adequate or better → skip tool configuration entirely this week. The tools are serving their purpose. (5) When tool changes are warranted, make the smallest change that addresses the specific identified gap. No speculative improvements; no "while I'm in here I'll also change...".