Why multitasking is a myth and how to reclaim focused time

Executive overview

Switch tasking — rapidly alternating between attention-requiring tasks — makes everything take longer, increases mistakes, and raises stress. It is biologically unavoidable: the brain cannot handle the cognitive load of two demanding tasks simultaneously.

The fix is not an app. It is reducing switches through deliberate scheduling, communication agreements, and giving people a clear "when."

Protecting single-tasking time is the highest-leverage productivity move a leader can make.

Switch tasking vs. backtasking

• Switch tasking: attempting two attention-requiring tasks simultaneously (e.g. answering email while in a meeting) — you are just alternating rapidly, not doing both.
• Backtasking: a mindless or automatic task runs in the background (e.g. running on a treadmill while listening to a podcast) — this is genuinely productive.
• Every switch incurs cost: longer completion time, more errors, higher stress.
• The more complex the task, the higher the switching cost.
• People who claim to be great multitaskers are statistically among the worst at it — a classic blind spot.

The impact on the people you lead

• Switching attention while someone is talking communicates they are unimportant — the most common word people report feeling is "unimportant."
• The reverse is also true: putting the phone away and turning off the screen during a conversation signals that the person matters.
• Leaders who are hard to reach create "vultures" — people who circle and grab your attention the moment they get it, adding unrelated items because they don't know when the next chance will come.
• Hovering at the end of a conversation is a signal: the person fears they won't get another opportunity and is improvising.

Shifting from the culture of now to the culture of when

• The culture of now drives a chain reaction of texts, emails, and calls demanding immediate response — perpetuating switch tasking.
• The culture of when means communicating clear expectations about when you will respond, when you will meet, and when tasks will be done.
• People tolerate delay well when given a reliable "when" and you meet it.
• Start the shift with a conversation framed around serving the other person, not your own frustration.
• Agree on response-time norms for each communication channel (Slack, email, text) — the team should define what each channel is for and how quickly a reply is expected.

One-to-one huddles and the quick-question trap

• "Quick questions" erode the day — batch them instead.
• Schedule a regular one-to-one huddle to fire all quick questions at once, then return to focused work.
• One manufacturing company increased overall productivity by 20% from this single change.

Auditing where your time actually goes

• There are 168 hours in a week. Mapping rough time allocations (sleep, work, meetings, family) quickly reveals whether your mental accounting adds up.
• If your tally exceeds 168 hours, you are doing two things at once and calling it one — the hours are an illusion, not a bonus.
• After the audit: reconcile. Ask "what do I want?" rather than "how do I survive this week?"
• Even with a constraining boss or role, there are always hours you control — start there.

Using the calendar as the primary productivity tool

• The calendar is the most powerful productivity app available — not a new one.
• Use it to see the truth about your week and make strategic decisions rather than reacting.
• Budget generously: leave buffer between appointments and open time for inevitable interruptions.
• Scheduling every minute is a mistake — under-spending time is the goal.
• Google Calendar's speedy meetings setting defaults meetings to 50 or 25 minutes, building buffer automatically.
• Structured days create freedom in the moment: when you have already decided where time goes, you can be fully present with whoever is in front of you.

Saying no as an ongoing practice

• Even advocates of focus need to keep practising saying no.
• A useful filter: if something can be delayed a week, test whether it can wait a month; if a month, test a year — some things can simply be dropped.