Convert infinite information activities into finite ones — email twice daily, news once for 15 minutes, with hard stopping points

Why This Is a Rule

Information consumption activities — email, news, social media, messaging — are structurally infinite: there is always more to read, another thread to follow, another message to check. Activities without natural stopping points expand to fill all available time because there's no signal that says "you're done." You're never done with email; you just stop checking for now.

Time-bounded windows convert these infinite activities into finite ones by adding artificial stopping points. "Email from 10-10:30 and 3-3:30" creates a bounded activity with a clear end. When 10:30 arrives, you stop — not because you've processed everything (you haven't; you never will) but because the window closed. The unprocessed email waits for the next window.

This works because most information consumption follows a diminishing-returns curve: the first 15 minutes of email processing catches the urgent items; the next 45 minutes processes the medium-priority items; the subsequent 2 hours processes items that could wait days. Time-bounding captures the high-value items (the first window's content) while preventing the low-value tail (the endless processing of non-urgent items) from consuming your attention budget.

When This Fires

• When information consumption expands to fill more time than you intended
• When "just checking email" turns into 90 minutes without a clear stopping point
• When designing an information diet for attention management
• Complements Turn off all social platform push notifications — each one is a variable-ratio reinforcement trigger delivered at your most susceptible moment (turn off notifications) with the structured consumption schedule

Common Failure Mode

Open-ended checking: "I'll check email and then get to work." Without a time bound, email checking has no stopping point — there's always one more message to read, one more thread to follow. The "and then" never arrives because the activity never ends. A time bound makes the activity finite: "I'll check email for 20 minutes and then get to work regardless of inbox state."

The Protocol

(1) Identify your infinite information activities: email, news, social media, messaging, feeds. (2) For each, set a time-bounded window: Frequency: how many times per day? (Email: 2-3x. News: 1x. Social media: 1x.) Duration: how long per window? (Email: 20-30 min. News: 10-15 min. Social media: 15-20 min.) Timing: when? (Batch at natural transition points — Calculate activity cost as disruption footprint: ramp-down + activity + ramp-up — the true cost includes attention residue — to minimize disruption footprint.) (3) When the window opens → process with full attention. When it closes → stop, regardless of inbox state. (4) Accept incomplete processing: you will never finish. The time bound ensures the most important items get processed while preventing the infinite tail from consuming your day. (5) Pre-define override conditions (Pre-define information boundary overrides — real-time exception negotiation produces spurious justifications from anxiety) for genuine emergencies so the time bounds don't create rigidity.