Classify pebbles and batch them into a defined window
Identify necessary-but-not-critical tasks (pebbles) and give them a contained, defined time block.
Key takeaways
- What it is: Identify necessary-but-not-critical tasks (pebbles) and give them a contained, defined time block.
- Why it works: Pebbles — routine tasks, correspondence, administrative work — are necessary and real, but they carry no urgency premium of their own; their urgency is often manufactured by notification systems or organizational expectations. Batching them prevents the diffusion of rock-time by pebbles: instead of handling them as they arrive, they accumulate in a queue and get processed efficiently in a dedicated block. Batch processing reduces context-switching cost and the attention residue it creates.
- Evidence: Backed by observational / correlational evidence.
- Avoid: Classifying "pebbles" so generously that they include genuinely important work — which starves the pebble window of time while leaving rocks unprotected.
Why it works
Pebbles — routine tasks, correspondence, administrative work — are necessary and real, but they carry no urgency premium of their own; their urgency is often manufactured by notification systems or organizational expectations. Batching them prevents the diffusion of rock-time by pebbles: instead of handling them as they arrive, they accumulate in a queue and get processed efficiently in a dedicated block. Batch processing reduces context-switching cost and the attention residue it creates.
How to do it
- 1Define what counts as a pebble for your work: email responses, approvals, admin tasks, short calls.
- 2Choose a daily window for pebbles (e.g., after lunch, 1:00–2:00 pm).
- 3Route all pebbles to this window during the day — flag them, don’t handle them.
- 4Process them efficiently in the batch; don’t let pebble time expand into rock time.
What the evidence says
ObservationalAttention residue research (Leroy, 2009) shows that task-switching generates a cognitive cost that reduces performance on the subsequent task. Batching collapses multiple context-switches into a single transition event, reducing the total residue cost.
Honest caveat: Batching works best when organizational culture and role type permit it. Roles with high time-sensitivity expectations may require modified batching — faster cycles, not the elimination of batching.
- — Leroy (2009), "Why is it so hard to do my work?", Organizational Behavior and Human Decision Processes
Common mistake
Classifying "pebbles" so generously that they include genuinely important work — which starves the pebble window of time while leaving rocks unprotected.
IX Coach helps you audit what landed in your pebble window during the week and whether it stayed there or colonized your rock time.
Practice this with IX Coach →