Prioritize long half-life + high reach outputs over short half-life + narrow reach — when both compete for time, durability × audience wins
Route attention and effort disproportionately to outputs with long half-lives (months-to-years) and high audience reach over outputs with short half-lives (hours-to-days) and narrow reach when both compete for finite production time.
Why This Is a Rule
When you have one hour and two competing outputs — a Slack thread reply (half-life: hours, reach: 3 people) and a blog post draft (half-life: years, reach: thousands) — the Slack thread feels more urgent but the blog post has 1,000x more total impact (lifespan × audience). Urgency bias consistently pulls attention toward ephemeral, narrow-reach outputs because they have deadlines and social pressure, while durable, wide-reach outputs sit patiently waiting without creating any pressure signals.
The half-life × reach formula makes the implicit trade-off explicit. A status update (1 day × 5 people = 5 person-days of impact) competes against a documentation page (2 years × 200 people = 400 person-days of impact). The documentation page produces 80x more total value but generates zero urgency signals. Without a conscious prioritization rule, the status update wins every time because it's "due today."
This is the knowledge worker's version of Eisenhower's important-vs-urgent distinction, made concrete with measurable dimensions. Urgency pulls toward short-half-life outputs; importance pulls toward long-half-life outputs. The rule explicitly overrides urgency with impact when both compete for the same time slot.
When This Fires
- When multiple outputs compete for the same production time and you must choose
- When your calendar is filled with urgent ephemeral outputs at the expense of important durable ones
- When you feel busy but aren't producing anything with lasting impact
- Complements Annotate each output type with its half-life (hours/weeks/months/years) — calibrate investment in durability and polish to actual lifespan (half-life annotation) with the prioritization decision when half-lives conflict
Common Failure Mode
Urgency-first scheduling: "I'll write the blog post after I finish these emails." The emails are always there — they regenerate daily. The blog post never gets written because there's always a more urgent ephemeral output claiming the time. The durable output perpetually loses to the urgent one.
The Protocol
(1) When competing outputs claim the same time block, estimate each output's total impact: half-life × audience size. (2) Route effort to the highest-impact output, regardless of which feels more urgent. (3) For urgent low-impact outputs that can't be deferred: reduce them to minimum viable quality (Define minimum viable output: who receives it, what action should they take, what minimum content enables that action — then ship at that threshold) to free time for high-impact work. (4) Protect dedicated time blocks for long-half-life outputs (Move meeting requests that land on maker blocks to manager-mode blocks — treat internal deep work with equal calendar commitment as client meetings — treat them like client meetings). Don't let ephemeral outputs consume them. (5) Review your output mix weekly: what percentage of your production time went to hours-lifespan outputs vs. months/years-lifespan outputs? If ephemeral dominates, restructure your allocation.