Track daily completion (yes/no) not tool configuration — consistent execution of a mediocre tool outperforms sporadic use of a perfect one

Why This Is a Rule

The PKM and productivity communities systematically overweight tool configuration (which app, which plugins, which workflow setup) and underweight execution consistency (did you actually use the system today?). But the value of any information processing system is a function of daily execution × time — it compounds through consistent use, not through optimal configuration. A basic system used daily for a year produces dramatically more value than a sophisticated system used sporadically for the same period.

The binary yes/no tracking metric — "Did I complete my processing session today?" — is deliberately simple. It focuses attention on the one variable that actually matters (consistency) and away from the variables that feel important but don't compound (which tool, how many features, how elegant the setup). A daily streak of yes/yes/yes/yes is worth more than any amount of configuration optimization applied to a system used 3 days out of 7.

This is the information-system analog of exercise science's finding that the best workout program is the one you'll actually do. A mediocre program done 5 days per week produces more fitness than an optimal program done 2 days per week. Consistency is the multiplier that tool quality operates on, and a multiplier applied to zero (days not processed) produces zero regardless of how large the multiplier is.

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 that meets them, commit for 90 days — satisfice, don't maximize) 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 that meets them, commit for 90 days — satisfice, don't maximize (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: 5 items in 2-3 minutes for 5 consecutive days — initiation barriers determine formation more than execution quality'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.