Two ways to protect your attention
Single-tasking means giving one piece of work your attention for a defined stretch. You might draft a proposal without checking messages or work through one difficult problem before opening another. Batching means grouping similar tasks and handling them in one session, such as replying to routine emails, filing notes, or processing invoices. Both approaches limit switching, but they do it at different scales: one protects a substantial task, while the other gathers many small tasks into a manageable block.
Neither method needs to govern your entire day. A useful plan might include a single-tasking session for writing, a batch for correspondence, and an unscheduled buffer for questions that arise. The goal is not to keep every minute occupied. It is to make your next action clear enough that you can begin without repeatedly deciding what deserves attention.
Choose single-tasking for work that needs continuity
Single-tasking is often the better fit when the work depends on holding several ideas in mind at once. Drafting, designing, learning a complex tool, and reviewing a detailed document can all require time to understand where you left off. If you repeatedly leave such a task for a quick reply, returning may require you to reconstruct your reasoning.
Give the session a concrete target rather than a vague label like “work on project.” You could aim to outline three sections, revise one page, or identify the next decision the project needs. Put the materials you need within reach and move unrelated tabs or papers out of view. If a separate thought appears, capture it in a short note instead of following it immediately.
A single-tasking session does not have to be long to be useful. Choose a span you can realistically protect, then decide what would count as a sensible stopping point. When you stop, leave a brief note about what you completed and what comes next. That makes it easier to resume, even if the day changes.
Use batching for small tasks with a shared process
Batching works well when several tasks call for the same tools or kind of decision. You might review meeting requests together, format several images in one session, or sort captured notes into project folders. Preparing the workspace once and following a similar process for each item can make the work feel less fragmented than scattering it throughout the day.
The key is to group tasks that genuinely belong together. “Do all admin” may be too broad if it mixes simple filing with decisions that require careful thought. A narrower batch, such as “reply to messages that need no research,” is easier to start and finish. Keep a separate place for items that turn out to need substantial work; they can become their own tasks rather than quietly expanding the batch.
Set a boundary for the batch, such as a list of items to process or a planned stopping time. Without one, an inbox or task queue can absorb whatever time is available. Batching is meant to give small obligations a place in the day, not to make clearing every queue the measure of a successful day.
Match the method to the task, not the label
Some work changes character as it progresses. Planning a presentation may begin as single-tasking while you decide on its message, then shift to a batch when you resize images or check slide titles. Email can work the same way: routine replies fit a batch, while a sensitive or complicated response may deserve an uninterrupted session of its own.
Before choosing a method, ask what the next step demands. Do you need to build or maintain a line of thought? Protect one task. Do you have several similar actions that each take little preparation? Group them. Are other people waiting on a timely answer? Handle that commitment explicitly rather than letting a batching rule delay it by default. These questions are more useful than trying to classify an entire role as either “deep work” or “admin.”
Build a rhythm you can revise
A simple starting point is to reserve a focused block for your most demanding task and one or two smaller windows for recurring batches. Let collaborators know when they can expect a response if your work allows it, while keeping an agreed route for genuinely urgent matters. Leave some space between blocks for transitions, breaks, and work that takes longer than expected.
After trying this for a few days, notice where your attention actually goes. If a batch keeps producing complex follow-up work, separate those items sooner. If a protected session is repeatedly interrupted by a responsibility you cannot postpone, plan around that responsibility instead of treating every interruption as a failure. Single-tasking and batching are tools for making attention easier to direct. Their value lies in helping you do the work in front of you while leaving room to respond, pause, and begin again.
