I used to bounce between email, design, and calls all day and end up exhausted with nothing actually finished. Now I batch by task type instead of working straight down a mixed to-do list. Monday is admin, Tuesday is content, same kind of work in one block, instead of jumping between kinds of work all day. I still wear every hat my business needs. I just don't wear all ten of them before lunch.
Every video in my "30 Hacks From Dahlia" series ends with the same line, and this hack is one of the reasons I keep saying it: I help small teams do big things, and a lot of that starts with how the week itself is built, not just what's on it. This one came out of a problem I couldn't keep ignoring. I used to bounce between ten tasks all day and end up exhausted with nothing actually finished. Email in the morning, a design tweak before lunch, a client call after that, then back to email because something new had landed while I was on the call. By the end of the day I had touched almost everything on my list and completed almost none of it.
Why bouncing between tasks wears you out
Turns out every time you jump from email to design to a call, your brain pays a tax. I'm not citing a study here, I'm describing what I noticed in my own week, over and over, until I couldn't unsee it. Each switch meant reloading context: who am I talking to now, what's the goal of this task, where did I leave off last time I touched it. That reloading takes real time and real focus, even when every individual task on the list is simple on its own.
String enough of those switches together across one day and you get exactly what I was living: busy from nine to five, and somehow still behind on everything by the time I closed my laptop. The tasks themselves weren't the problem. The order I did them in was.
How to find your own recurring task types
Before you can batch anything, you need an honest list of what actually fills your week, not what you wish filled it. I sat down and wrote out everything I do in a typical week, then grouped it into a small handful of buckets. Yours might look a little different depending on your business, but almost everyone running something small ends up with some version of the same few categories.
The buckets I use
- Admin: email, invoicing, scheduling, the parts of running a business that don't need deep thought but do need steady attention.
- Content: writing, recording, designing, anything that produces something a client or an audience will actually see.
- Calls: client check-ins, discovery calls, team syncs, anything that runs on another person's calendar, not just mine.
- Deep strategy: planning, pricing decisions, system design, the thinking work that needs quiet and a clear head, not a spare half hour between meetings.
Once I had those categories, mapping my actual tasks onto them for a week made the pattern obvious. Most of what felt like ten different jobs was really four kinds of work, just showing up in a random order.
Designing a themed week that actually holds
With the buckets in hand, I mapped them onto the days I actually have, not an ideal week that doesn't exist. Monday is admin, because the inbox always piles up over the weekend, and I'd rather clear it in one focused block than let it interrupt me for the rest of the week. Tuesday is content, because that's when I tend to have the longest uninterrupted stretch, and content work needs momentum more than it needs a perfect mood.
Calls get clustered too, usually into one or two specific days, so the rest of the week isn't dotted with thirty-minute holes that are too short for deep work and too long to just wait out. Strategy gets whatever day I have the most energy for thinking clearly, which for me is early in the week, before the smaller decisions of daily operations have worn down my attention. I didn't fight my calendar to make this work. I built the theme around the shape my week already had.
Before you assign days to task types
What to do when something urgent doesn't fit the plan
The system meets its first real test the moment something urgent lands on a day it doesn't belong to, and something urgent always does. A client emergency doesn't wait for its themed day, and it shouldn't have to. What I've learned is that the goal was never a perfectly untouched schedule. The goal is fewer switches, not zero switches.
When something urgent comes up, I handle it, then I go straight back to the theme for that day instead of letting the interruption turn into an excuse to abandon the whole system. Most of what feels urgent in the moment could actually wait until its themed day. Ask yourself that before you switch, not after.
You wear ten hats, but you don't have to wear all ten before lunch.
The solo-founder and small-team reality
If you're running something small, you already know the batching doesn't remove any of your hats. I still do admin, I still write and design, I still get on calls, I still have to think strategically about where the business is headed. Batching doesn't shrink that list. It sequences it, so I'm the admin version of myself for a stretch, then the content version, then the strategist, instead of trying to be all four at once, all day, every day.
That distinction matters more, not less, for a small team or a solo founder. When you're the only person available to do most of the work, the exhaustion of constant switching lands entirely on you. Wearing ten hats is the job. Wearing all ten of them within the same hour is what actually burns people out.
Checking whether the batching is actually working
After about a month, I sit down and look back honestly, not at what I touched each week, but at what I actually finished. If content is still dragging even with its own protected day, that tells me something: maybe content needs a bigger block, or maybe it belongs on a different day entirely, one where I have more energy left after admin and calls are already handled.
The themed week isn't a fixed structure I set once and defend forever. It's a working draft I keep adjusting against what I actually observe, the same way I'd adjust anything else in the business that wasn't performing the way I expected it to.
Key takeaways
- Every switch between different kinds of work costs focus, even when each task is simple on its own.
- Group your recurring work into a small number of honest buckets: admin, content, calls, deep strategy, or whatever fits your business.
- Assign task types to days based on your actual energy and calendar shape, not an idealized version of your week.
- Urgent work still gets handled immediately. The system just keeps the non-urgent version of that interruption from derailing your whole day.
- Batching doesn't remove any of the hats you wear running a small business. It sequences them so you're not wearing all of them at once.
- Review after a month by looking at what actually got finished, then adjust the theme, not just your effort.
This is hack 9 in a series I never expected to keep going past thirty, because there's always one more piece of the day quietly worth restructuring. Full step-by-step guide and the rest of the series are linked in my bio. If you run more than one business, or more than one role inside the same one, the pattern here scales the same way: find your real task types first, build the week around them, and leave room for the one thing that won't wait for its turn.
Frequently Asked Questions
It means grouping similar work into the same block of time instead of doing it in whatever order it arrives. Instead of a to-do list that mixes email, design, and calls throughout one day, you sort your recurring work into a handful of categories, admin, content, calls, deep strategy, and assign each category its own day or block. The work doesn't change. The order it happens in does.
Start with three or four categories, not ten. Most small business owners already have a natural handful: admin, content, calls, and deep strategy or planning work cover the bulk of a typical week. Adding more categories than that usually just recreates the fragmented schedule you were trying to fix, because you end up with a theme for every single day and no room to breathe.
Handle it, then go back to the theme. The goal of batching is fewer switches, not zero switches. A genuine client emergency on your admin day still gets handled on your admin day. What batching prevents is the smaller, non-urgent version of that interruption, the thing that could easily wait until its themed day but pulls your attention anyway because it happened to land in your inbox first.
Yes, and it matters more, not less, when you're solo. Batching doesn't remove any of the hats a small business owner wears. It sequences them. You still do admin, content, sales calls, and strategy in the same week. You just stop wearing all of them within the same hour, which is what actually causes the exhaustion of running something small on your own.
