Batch or stream

Group work into batches or process it continuously to balance switching cost against waiting cost.

Errands leak through your whole week: Tuesday pharmacy run, Wednesday one grocery item, Thursday the post office, each with its own drive, parking, and mental restart. Or maybe you are the opposite type, letting all household admin pile up for one monster Saturday that eats the weekend and still misses deadlines.

Batch or stream means grouping work into batches or processing it continuously, balancing switching cost against waiting cost. The cue: either many small repetitions each paying a fixed overhead (drives, mental restarts), or a big irregular pile where items wait so long they rot (late fees, expired return windows). Steps: estimate the two costs, what each switch costs you versus what waiting costs you; move toward the cheaper side, batching errands into one Saturday loop while pulling anything deadline-sensitive out of the batch into an immediate stream; then recheck occasionally, because the right answer shifts with circumstances. The visible change: fewer total hours lost to overhead, and fewer items dying in the queue. This is a dial, not a doctrine, so don't batch things whose value decays fast while waiting; a billing dispute or a leaking pipe streams now, no matter how elegant your Saturday system is.