You're folding laundry while listening to a podcast. That feels productive. Then you try to answer emails while sitting in a meeting. In practice, that feels like work. But are they the same thing?
Short answer: no. Not even close The details matter here. Still holds up..
One of them works with your brain. The other fights it. And knowing the difference might be the single biggest lever you have for getting more done without burning out.
What Is Multitasking
Multitasking is the attempt to perform two or more cognitive tasks simultaneously. On the flip side, key word: attempt. Your brain doesn't actually do them at the same time. It switches. In practice, fast. Because of that, context-switching is the technical term. Every switch costs energy, focus, and time It's one of those things that adds up..
Research from the American Psychological Association shows that task-switching can cost up to 40% of productive time. Consider this: that's not a typo. Forty percent Not complicated — just consistent. Took long enough..
The switching cost nobody talks about
When you jump from a spreadsheet to Slack to a text message and back to the spreadsheet, your prefrontal cortex has to:
- Disengage from Task A
- Activate the rules for Task B
- Suppress the lingering activation of Task A
- Re-engage Task A when you return
Each cycle takes milliseconds. And the more complex the tasks, the higher the cost. But they add up. Writing code while half-listening to a Zoom call isn't just inefficient — it produces worse code and worse listening Simple as that..
What counts as true multitasking
True multitasking only happens when at least one task is fully automated. Breathing and blinking. Driving a familiar route while singing along to the radio. Walking and chewing gum. These work because the basal ganglia handles the automatic task while your prefrontal cortex stays free for the other Less friction, more output..
But replying to email while "listening" to a strategy review? In real terms, that's not multitasking. That's rapid toggling with a side of self-deception Turns out it matters..
What Is Combining Tasks
Combining tasks — sometimes called task batching or parallel processing — is different. Consider this: you're not switching. You're pairing a cognitive task with a physical or automatic one. Or grouping similar cognitive tasks together so the context stays the same It's one of those things that adds up..
The mental framework doesn't shift. The rules don't change. You stay in one mode Worth keeping that in mind..
Examples that actually work
- Listening to an industry podcast while commuting
- Taking walking meetings for 1-on-1s that don't require screens
- Folding laundry while rehearsing a presentation out loud
- Batching all email responses into two 30-minute blocks instead of checking constantly
- Running a script that processes data while you draft the report that uses it
Notice the pattern? One task runs on autopilot or shares the same mental context. No context-switching penalty That's the part that actually makes a difference..
The cognitive science behind it
Your brain has two main attention networks: the default mode network (internal thought, creativity, planning) and the task-positive network (focused external attention). They're largely anti-correlated — when one activates, the other quiets down But it adds up..
Multitasking forces them into a tug-of-war. Combining tasks lets them take turns cleanly. Or it keeps you in the task-positive network for a sustained block, which is where deep work lives No workaround needed..
Why It Matters
Most people don't realize they're multitasking. On top of that, they think they're "good at it. " They're not. Nobody is. The 2.5% of people who test as "supertaskers" are statistical outliers — and even they show performance degradation under load.
The hidden costs show up everywhere
- Quality drops. Typos in emails. Missed action items in meetings. Bugs in code deployed Friday afternoon.
- Memory suffers. Information encountered during task-switching encodes poorly. You "hear" things but don't retain them.
- Stress rises. Cortisol spikes with each switch. The feeling of "busy but not productive" is real — and chemically measurable.
- Creativity dies. Insight needs uninterrupted incubation. Switching kills the simmer.
The productivity theater trap
Modern work culture rewards visibility. Day to day, quick replies. Slack green dots. Calendar density. Even so, looking busy. But the highest-value work — strategy, writing, coding, designing, deciding — requires the exact opposite: long, uninterrupted stretches where combining tasks is the only "parallel" work happening That's the part that actually makes a difference..
If you're proud of answering 200 emails a day but haven't had a single original thought in a month, you're not productive. You're reactive.
How It Works in Practice
Let's get concrete. Here's how to audit your day and redesign it around combining instead of multitasking.
Step 1: Categorize every recurring task
Grab a notebook. List everything you do in a typical week. Tag each one:
- Deep cognitive — writing, coding, analyzing, strategizing, learning
- Shallow cognitive — email, Slack, scheduling, expense reports, status updates
- Physical/automatic — commuting, dishes, walking, exercise, laundry
- Social/interactive — meetings, calls, 1-on-1s, workshops
Be honest. "Writing the quarterly narrative" is deep cognitive. "Checking email" is shallow cognitive. They need different treatment That's the part that actually makes a difference..
Step 2: Identify your combinable pairs
Now match them. Now, deep cognitive never pairs with deep cognitive. That's multitasking.
- Outline the blog post while walking the dog
- Rehearse the pitch while driving to the office
- Let the compiler run while stretching
Shallow cognitive batches beautifully with itself:
- Process all email in two windows: 9:30–10:00 and 4:00–4:30
- Batch Slack replies at the top of each hour
- Do all admin — expenses, timesheets, approvals — in one Friday afternoon block
Social/interactive tasks combine with physical when the format allows:
- Walking 1-on-1s for relationship-building conversations
- Phone calls (not video) while pacing or stretching
- Async video updates watched at 1.5x while on a stationary bike
Step 3: Build your default weekly template
Don't leave it to willpower. Design the container. A sample knowledge-worker week might look like:
Monday
- 8:30–11:00: Deep work block (no email, no Slack)
- 11:00–11:30: Email/Slack batch
- 11:30–12:30: Walking 1-on-1s
- 12:30–1:30: Lunch + podcast (combine)
- 1:30–3:30: Deep work block
- 3:30–4:00: Email/Slack batch
- 4:00–5:00: Admin batch
Tuesday–Thursday: Similar rhythm. Protect the deep blocks. Batch the shallow. Combine the physical.
Friday
- Morning: Deep work or learning
- Afternoon: Weekly review, planning, admin batch, async updates
The exact hours don't matter. Consider this: the principle does: one cognitive mode at a time. Physical tasks fill the gaps.
Step 4: Set up your environment to enforce it
Willpower fails. Friction works The details matter here..
- Turn off notifications. All of them. Use focus modes.
- Close email tab
completely. When the trigger is active, you are in a cognitive sanctuary. If it’s not "Email Batch Time," the app shouldn't even be visible on your screen. Even so, if it's an emergency, call me. On top of that, put your batching windows in your Slack status or email signature: "I check messages at 11 AM and 4 PM. - Create a "Deep Work" physical trigger. That said, - Communicate your boundaries. That's why this could be a specific playlist, a certain lamp you turn on, or noise-canceling headphones. " You'll be surprised how few "emergencies" actually exist.
The Psychology of the Shift
The hardest part of this transition isn't the scheduling; it's the anxiety. We have been conditioned to believe that responsiveness equals value. We feel a dopamine hit every time we clear a notification, which tricks our brain into feeling productive while we are actually just spinning our wheels And that's really what it comes down to..
When you stop reacting in real-time, you will initially feel a sense of "FOMO" (Fear Of Missing Out) or guilt. You might worry that a colleague thinks you're slacking or that a project is stalling The details matter here..
Remind yourself: Responsiveness is a service; deep work is a product.
If you spend your entire day providing the service of "being available," you will never have the time to build the product—whether that product is a piece of software, a strategic plan, or a creative breakthrough. The goal is to move from being a switchboard operator to being an architect.
We're talking about where a lot of people lose the thread.
Conclusion: Reclaiming Your Cognitive Sovereignty
Productivity is not about squeezing more tasks into a twenty-four-hour window; it is about protecting the quality of your attention. When you blur the lines between deep thought and shallow administration, you don't get more done—you just get tired faster.
By categorizing your tasks, batching the shallow, and combining the automatic, you stop leaking mental energy. You stop the constant "context switching" that drains your brain's battery and begins to erode your ability to think critically Practical, not theoretical..
Start small. Pick one deep block tomorrow morning and one batching window for your email. Protect them fiercely. Once you experience the clarity that comes from a single, uninterrupted cognitive mode, you'll realize that the "hustle" of multitasking was actually just a distraction from the work that actually matters.
