Flex your dispatch threshold with context: ~1 minute during fragmented days, ~5 minutes during dedicated admin blocks
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.
Why This Is a Rule
Your available processing capacity varies dramatically between days, and the dispatch threshold should adapt accordingly. On a meeting-heavy day with 15-minute windows between meetings, you can only handle very short tasks immediately — anything over ~1 minute risks running into the next meeting. On a day with a dedicated 2-hour admin block, you can handle 5-minute tasks without concern because the block provides ample capacity.
The principle is matching task size to available time slots. Small time slots (5-15 minutes between meetings) should be filled with the smallest tasks. Large time blocks (1-2 hour admin sessions) can absorb larger tasks. If you apply a uniform 2-minute threshold on a fragmented day, you'll attempt tasks that don't fit the available windows and either run late to meetings or leave tasks half-finished. If you apply the same threshold during a dedicated block, you'll capture tasks that could easily be dispatched immediately, creating unnecessary management overhead.
This is the same principle behind memory allocation in computing: match the object size to the available memory slot. Small slots get small objects; large slots can handle larger ones. Using the wrong slot size (task too big for the available time window) produces fragmentation and waste.
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: set it where management overhead equals execution cost, not at an arbitrary 2 minutes (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: set it where management overhead equals execution cost, not at an arbitrary 2 minutes). 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 (communication, financial, scheduling), not by arrival order — minimize context-switching within processing blocks) 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.