Classify pebbles and batch them into a defined window

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.

How to do it

1. Define what counts as a pebble for your work: email responses, approvals, admin tasks, short calls.
2. Choose a daily window for pebbles (e.g., after lunch, 1:00–2:00 pm).
3. Route all pebbles to this window during the day — flag them, don’t handle them.
4. Process them efficiently in the batch; don’t let pebble time expand into rock time.

Evidence

Attention 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. (observational)

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.

Sources

• 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.