For years I ran my business the way most advice suggests: a bit of everything, every day. A little marketing, a little client work, a little admin, a little strategy, spread across the week to "stay on top of things." It felt responsible. It was, in hindsight, one of the most expensive habits in my entire business, and switching to batching was the single change that returned the most time.
Every time you switch from one kind of task to a different kind of task, there's a cost. Your brain has to unload the context of the last task and load the context of the new one: different mental models, different tools, sometimes a different tone of communication entirely. For a neurotypical brain, that switching cost is real but manageable. For ADHD and autistic brains, the cost is often much higher, and the recovery time after a switch, before you're back to full capacity, can stretch far longer than people assume.
Batching means grouping similar tasks together and doing them in a single block, so the switching cost gets paid once instead of five times. All client emails happen in one sitting instead of being answered as they arrive throughout the day. All content gets written in one focused block per week instead of a little each morning. All invoicing happens on one afternoon a month. The type of work stays consistent within each block, so the brain never has to reload context mid-stream.
The time savings were bigger than I expected going in. I estimated it conservatively at first and ended up recovering more than fifteen hours a week once I fully committed to batching instead of spreading similar tasks across days. Most of that time wasn't "found" in the sense of doing things faster. It was time that had been quietly lost to switching costs I hadn't been measuring at all, because they don't show up on a calendar the way a meeting does.
Setting it up required being honest about what kinds of work actually belong in the same batch. Communication tasks batch well together, even across different clients, because the mode of thinking is similar. Deep creative or technical work batches separately, and should never be mixed into the same block as communication, because the context switch between "respond quickly and clearly" and "think slowly and deeply" is one of the most expensive switches there is.
The other piece that mattered was protecting the batches from interruption. A batch only saves time if it's actually uninterrupted. I turned off notifications during batch blocks entirely, told clients in advance when I'd be reachable, and stopped treating "quick availability" as a virtue. Being slightly less available, in exchange for dramatically more focused output, was a trade worth making publicly, not just privately.
If your week feels full but your output doesn't match the hours, batching is usually the first thing worth testing. Look at what kinds of tasks you're currently spreading across every day, and try grouping them into single blocks instead. The time doesn't come from working faster. It comes from stopping the constant, invisible cost of switching between different kinds of thinking, over and over, all day long.