Flex your dispatch threshold with context
During meeting-heavy days with fragmented administrative windows, lower your dispatch threshold to ~1 minute; during dedicated administrative blocks, raise it to ~5 minutes to match available processing capacity.
When This Fires
- At the start of each day when assessing what kind of day it is (meeting-heavy vs. admin-heavy)
- When you have 10 minutes between meetings and a queue of captured tasks
- When you have a long admin block and are deciding what to process
- Complements Calibrate your personal do-it-now threshold (personal threshold calibration) with the daily context adaptation
Common Failure Mode
Rigid threshold regardless of context: applying the same 2-minute rule on a day with twelve 10-minute windows between meetings as on a day with a 3-hour uninterrupted block. The rigid threshold either under-dispatches (missing opportunities to clear quick tasks in short windows) or over-dispatches (attempting 5-minute tasks in 3-minute windows).
The Protocol
(1) At the start of each day, assess your processing context: Fragmented day (mostly meetings with short windows) → set threshold to ~1 minute. Only dispatch the quickest tasks between meetings. Everything else waits. Balanced day (mix of meetings and blocks) → use your calibrated threshold (Calibrate your personal do-it-now threshold). Admin-heavy day (long dedicated blocks) → raise threshold to ~5 minutes. Process larger tasks during the block; don't over-capture for later. (2) During fragmented windows, pre-sort your task queue by estimated duration — tackle the shortest items first to maximize what fits. (3) During dedicated blocks, batch by cognitive context (Batch tasks by cognitive context…) rather than by size. (4) Adjust in real-time: if a planned block gets interrupted, lower the threshold for the remainder. (5) This is about fitting tasks to time, not about changing how hard you work.