Track daily completion (yes/no) not tool configuration…
Track daily whether you completed your information processing session (yes/no) rather than optimizing configuration, because consistent execution of a mediocre tool outperforms sporadic use of a perfect one.
When This Fires
- When you're spending more time configuring your system than using it
- When the urge to switch tools (Pick a tool with 5 minimum requirements, select the first…) is competing with the need to just process today's items
- When evaluating whether your information system is "working" — check execution days, not feature count
- Complements Pick a tool with 5 minimum requirements, select the first… (90-day tool commitment) with the daily execution metric that matters
Common Failure Mode
Configuration as procrastination: spending 2 hours reorganizing tags, testing plugins, or redesigning templates instead of spending 20 minutes processing the inbox. The configuration feels productive (you're "improving the system!") but produces zero compounding value because no information was actually processed.
The Protocol
(1) Create a simple daily tracking mechanism: a checkbox in your task manager, a streak tracker app, or a physical calendar where you mark each day. (2) Each day, mark yes or no: "Did I complete my processing session today?" Processing means actually triaging, routing, or transforming information — not configuring the tool. (3) Target: 28+ yes days out of every 30. This allows for 2 rest/travel days per month while maintaining the habit. (4) When your streak is threatened, use Start processing habits tiny's minimal version: 5 items in 2 minutes counts as a yes. The streak matters more than the session quality. (5) When tempted to optimize configuration, check your streak first. If you've processed daily for the last 2 weeks, earn a configuration session. If not, process today instead.