Build the mental model
Most productivity failures are not caused by laziness — they are caused by patterns that feel productive in the moment but quietly drift time from doing real work toward maintaining the system.
- Using too many apps — each new tool needs its own capture/review/login, one more place a task can die
- Building elaborate dashboards — decorating a tracker moves no task closer to done
- Capturing everything without filtering — the inbox becomes a chore and capture stops
- Never reviewing notes — a write-only archive is pointless
- Keeping tasks inside notes instead of a task manager — breaks retrieval
- Keeping calendar events inside a task list — muddles time-specific commitments
- Changing systems every week — resets the familiarity that actually compounds
- Copying someone else's system exactly — imports their constraints, not their actual problem
The same underlying mechanism repeats across all of them: time drifts from doing the actual work toward maintaining the system.
THE ORGANIZING SPIRAL
---------------------
THE ORGANIZING SPIRAL
-----------------------
week 1: [########## doing][# organizing]
week 2: [######## doing][### organizing]
week 3: [##### doing][###### organizing]
week 4: [## doing][######### organizing]
time spent maintaining the system keeps growing while
time spent doing the actual work quietly shrinksConnect it to a real scenario
Weekly, honestly compare time spent on real work versus organizing the system — if organizing exceeds roughly 15-20%, something on the mistakes list is happening.
- List every app holding a task, note, or calendar entry — consolidate past four or five
- Count tasks without a next action
- Count notes untouched for over a month
Resist fixing this by switching tools — process the inbox to zero, archive stale notes, and give every new task a next action.
Try the working example
function checkOrganizingRatio(weekLog) {
const totalOrganizing = weekLog.reduce((sum, d) => sum + d.organizingHours, 0);
const totalDoing = weekLog.reduce((sum, d) => sum + d.doingHours, 0);
const ratio = totalDoing === 0 ? Infinity : totalOrganizing / totalDoing;
let verdict;
if (ratio > 0.3) verdict = "unhealthy: too much time spent maintaining the system";
else if (ratio > 0.15) verdict = "watch: organizing is creeping up";
else verdict = "healthy: organizing stays in support of doing";
return { totalOrganizing, totalDoing, ratio: Number(ratio.toFixed(2)), verdict };
}
const week = [
{ day: "Mon", organizingHours: 1.5, doingHours: 6 },
{ day: "Tue", organizingHours: 2, doingHours: 5 },
{ day: "Wed", organizingHours: 3, doingHours: 4 },
{ day: "Thu", organizingHours: 1, doingHours: 6.5 },
{ day: "Fri", organizingHours: 2.5, doingHours: 4 },
];
console.log(checkOrganizingRatio(week));{
totalOrganizing: 10,
totalDoing: 25.5,
ratio: 0.39,
verdict: 'unhealthy: too much time spent maintaining the system'
}
Organizing hours (10) come to 39% of doing hours (25.5), above the 0.3 threshold, so it lands on "unhealthy."5-minute try-it
Log your own organizingHours and doingHours for five real days and run checkOrganizingRatio(). If it lands on "unhealthy" or "watch", identify which mistake on the list it connects to.
One important caution
Mistaking time spent decorating a dashboard for actual productive work
Trying to fix a worsening ratio by adding yet another new tool
Wikipedia: Time management — Productivity Systems