Test 'busywork' by asking what breaks if you stop for a month — eliminate or relabel
For every operational task you currently frame as 'busywork,' write one sentence describing what would break if you stopped doing it for a month—if nothing breaks, eliminate it; if something breaks, relabel it as infrastructure.
Why This Is a Rule
"Busywork" is a label that simultaneously acknowledges a task's existence and dismisses its value. But the label is often wrong in both directions: some "busywork" genuinely has no value and should be eliminated. Other "busywork" is invisible infrastructure — it feels tedious but its absence would cause cascading failures.
The one-month test distinguishes the two. "If I stopped doing this for a month, what would break?" produces one of two answers: Nothing — the task has no downstream dependencies and can be safely eliminated. Something specific — the task maintains a system, relationship, or capability that would degrade without it. In the second case, the task isn't busywork — it's infrastructure, and it deserves to be treated as such (scheduled intentionally, given adequate time, not resented).
The reframe from "busywork" to "infrastructure" changes how you relate to the task. Busywork is something to minimize and resent. Infrastructure is something to maintain and optimize. The task hasn't changed; your understanding of its role has.
When This Fires
- During a productivity review when looking for tasks to eliminate
- When you resent a recurring task and want to know if cutting it is safe
- Categorizing your task list into high-value and low-value work
- Any moment of frustration where you think "why am I doing this?"
Common Failure Mode
Labeling everything as "would break something" because you can imagine a scenario where it matters. The test is realistic: what would actually break in the next month, not what could theoretically break in an extreme scenario. A task that would matter in a once-a-year edge case but not in a typical month is probably eliminable — or at minimum reducible to annual rather than weekly frequency.
The Protocol
For each task you label as "busywork": (1) Write one sentence: "If I stopped doing this for a month, [what would break]." (2) If the answer is genuinely "nothing" → eliminate the task immediately. You've been spending time on a zero-value activity. (3) If the answer is specific and real → relabel the task as "infrastructure maintenance." Give it a proper schedule and appropriate time allocation. It's not busywork — it's keeping something running. (4) Respect the infrastructure tasks; eliminate the actual waste.