The two-minute rule, popularized as part of David Allen's GTD system discussed elsewhere on this shelf, is deliberately small: if a task will take less than two minutes to complete, do it immediately rather than logging it for later. The rule's value isn't really about the two minutes themselves — it's about removing an entire category of small, low-value decisions (should I log this, when should I get to it, which list does it belong on) for tasks trivial enough that the decision itself takes longer than the task would.
Why small decisions add up more than they seem to
Decision fatigue — the well-documented tendency for decision quality to degrade over a day as the cumulative number of decisions made increases — applies just as much to small, seemingly trivial choices as to large ones, and arguably more, because small decisions happen far more often across a day and rarely feel individually significant enough to notice their cumulative cost. A rule that removes an entire category of small decisions by making them mechanical (under two minutes: just do it, no deliberation) preserves decision-making capacity for choices that actually warrant it.
This is the underlying logic behind several small, mechanical rules beyond the two-minute one: rules work well specifically for decisions that are low-stakes individually but frequent enough in aggregate to meaningfully drain decision-making capacity if each instance is deliberated separately. For a practical software example related to the 7-minute payroll rule, find more here.
Other small rules that follow the same logic
A 'one in, one out' rule for recurring commitments (a new regular meeting or obligation requires dropping an existing one) forces the trade-off Essentialism argues for, discussed elsewhere on this shelf, without requiring a full deliberate cost-benefit analysis every time a new request arrives. A default response-time rule for messages (same business day, not same hour, absent explicit urgency) removes the recurring micro-decision of whether to respond immediately to each individual message, connecting to the notification-triage guide on this shelf. A fixed 'no meetings before 10 a.m.' or similar calendar rule removes the recurring negotiation over whether a specific new meeting request should get an early slot.
- A good mechanical rule applies to a genuinely frequent, genuinely low-stakes decision — applying rigid rules to high-stakes or infrequent decisions removes exactly the deliberation those decisions need.
- State the rule explicitly, even just to yourself, rather than applying it inconsistently — an inconsistently applied rule still requires the same decision each time, defeating its purpose.
- Review mechanical rules occasionally (monthly or quarterly) rather than constantly — the point is to stop re-deciding them daily, not to never reconsider them at all.
- A rule that starts producing consistently bad outcomes is a signal to revise the rule, not to keep applying it out of consistency for its own sake.
Where small rules stop being useful
Mechanical rules fail when applied to decisions that genuinely require situational judgment — a rigid rule about meeting scheduling, for instance, breaks down for a genuine one-off emergency that doesn't fit the rule's normal case, and insisting on the rule anyway in that specific situation defeats the purpose of having good judgment available at all. The value of a small decision rule comes specifically from applying it to the repetitive, low-stakes majority of cases while still allowing an explicit, deliberate exception for the genuine outlier.
Taken together, a small set of consistently applied mechanical rules functions as a kind of pre-decided policy for an entire category of recurring choices — freeing up exactly the finite decision-making resource that the rest of the methods on this shelf depend on being available when it matters. For additional background on this subject, consult the decision-fatigue overview.