The definition, expanded
A batch is a set of tasks that use the same tools, the same mindset or the same place. Email replies are a batch. Phone calls are a batch. Errands near the post office are a batch. The rule is simple: if two tasks need the same setup, do them back to back.
Batching is mainly for small, repeatable work. Large tasks need their own block, not a batch.
Where it comes from
The term comes from batch production and batch processing in computing: run similar jobs together to avoid paying setup costs each time. The personal version leans on task-switching research. Lab studies such as Rubinstein, Meyer and Evans (2001) found that switching between tasks costs time, and the cost grows with task complexity. The American Psychological Association’s summary covers the same findings.
How it works
- List the small, recurring tasks from your week.
- Group them by setup: same app, same place, same kind of thinking.
- Give each group a fixed slot, daily or weekly.
- Let new items of that type wait for their slot instead of handling them on arrival.
- Review after two weeks: merge batches that are too small, split ones that run long.
An example
Alex used to answer messages as they came in. Now the week has three batches:
- Daily 12:30–13:00 · Email and client messages #Clients
- Daily 16:30–17:00 · Calls and voice notes
- Friday 15:00–16:00 · Invoices, receipts, Shop orders #Shop
The mornings between 09:00 and 12:00 stay free for the Website project. Urgent client issues still get through by phone; everything else waits a few hours.
When it doesn’t work
Batching assumes small tasks can wait. In support roles, or when a client expects replies within the hour, a twice-a-day email batch can cause real problems. Batches also grow: a 30-minute email slot that keeps running to 75 minutes is a sign the inbox needs fewer subscriptions, not a longer batch. And batching does nothing for big, ambiguous work; that needs deep work time.
Task batching in Needt
Use the context tag to mark the batch: call the printer, 10 min @calls. In Workspace → List, filter by that tag and save it as a view, so every call sits in one list. Give the batch a slot on the Calendar, and let auto-scheduling fit the rest of your tasks around it. Emails you need to act on can be turned into tasks from Gmail, Outlook or IMAP, so they join the batch instead of staying in the inbox.
Agent prompt for Ask: “Group all my @calls tasks into one block after 16:00 today and tell me if they won’t fit.”
