The Art of Doing Less

The Productivity Paradox: Why Less Can Be More

Why adding more tasks and more tools can lower output, explained with plainly hypothetical examples and a few ways to check it against your own week.

On this page
  1. The paradox in one sentence
  2. Cost 1: Switching
  3. Cost 2: Managing the work
  4. Cost 3: Tools
  5. Cost 4: Fatigue and quality
  6. Cost 5: Lost slack
  7. A table of the examples
  8. When “less” does not win
  9. Testing it on yourself
  10. The takeaway

The paradox in one sentence

You add more tasks, more apps and more reminders in the hope of getting more done, and somehow less gets finished. This is the puzzle behind the phrase, and it is common enough that many people recognize it from their own weeks. The explanation is usually not mysterious. Extra work, extra tools and extra commitments each carry costs that are easy to overlook.

All numbers below are hypothetical, made up to illustrate the idea. They are not measurements and do not describe real people or studies.

Cost 1: Switching

Imagine you have an 8-hour workday and you split it across 4 unrelated tasks, switching between them often. Suppose each switch costs 10 minutes of getting back up to speed, and you switch 12 times. That is 12 x 10 = 120 minutes, or 2 hours, lost to switching. Of 8 hours, 6 remain for actual work.

Now suppose you focus on 2 tasks and switch only 3 times. That is 3 x 10 = 30 minutes, leaving 7.5 hours. The people in these examples did not work harder or smarter; one simply switched less. Real switching costs vary widely and depend on the work, so treat the 10 minutes as a placeholder. The shape of the idea is what matters: switching is not free. Practices like single-tasking and task batching aim to reduce it.

Cost 2: Managing the work

Every task you take on needs some overhead: remembering it, tracking it, updating others about it. Imagine each commitment needs 15 minutes of administration per day. With 4 commitments that is 60 minutes. With 8 it is 120 minutes. Doubling the commitments doubled the administration, but if the hours available stayed the same, the working time fell from 7 hours to 6 in this example (8 minus 1 versus 8 minus 2). Again, the numbers are invented, and in real life overhead is uneven. But it often grows with the count of things, even when no one notices it.

Cost 3: Tools

Tools are meant to save time, but each one adds something to learn, check and maintain. Suppose you use 3 apps for notes, tasks and reminders. Each has its own inbox of items to review, 5 minutes a day each, so 15 minutes daily. Items also slip between apps, because you wrote something in one and looked in another. A single list or one plain notebook can mean less review and fewer lost items. This is why people sometimes talk about tool overload: the problem is rarely any single app, but how many you are maintaining at once.

Cost 4: Fatigue and quality

Hours are not all equal. After a long run of constant switching or very long days, many people find their attention thins and mistakes creep in. Fixing mistakes takes time too. If a rushed job needs an hour of rework, the “saved” time may disappear. This effect varies greatly with the person and the task, and some people thrive on busy schedules. The claim is not that it always happens, only that it often does.

Cost 5: Lost slack

A schedule packed to the edge has no room for the unexpected. Imagine you plan 8 hours of work in an 8-hour day, and one task takes 1 hour longer than planned. Something else now slips, and the delay can spread through the week. If you plan 6 hours and leave 2 hours of slack, the same overrun is absorbed without drama. Time padding is not laziness; it is an acknowledgment that estimates are often optimistic.

A table of the examples

Situation (hypothetical) More Less
Switching 12 switches = 120 min lost 3 switches = 30 min lost
Admin overhead 8 commitments = 120 min 4 commitments = 60 min
Planned load 8 of 8 hours, no slack 6 of 8 hours, 2 hours slack

The point is not that the right number is four, or six. The point is that the costs scale with the count.

When “less” does not win

It would be misleading to claim that fewer is always better. Some work really does need many hands, many tools or long hours. A new tool can legitimately save time once you learn it. Seasonal peaks, deadlines and emergencies are real. The paradox describes a tendency, not a law, and it is mostly about the unnoticed costs, not a ban on effort.

Testing it on yourself

You can check whether this applies to you without any special system.

  1. Pick a typical week. Note roughly how many separate commitments, apps and tasks you juggled.
  2. Track one cost. For example, count how often you switch tasks in a morning, or how many places you check for what to do next.
  3. Remove one thing. Cut an app, pause a task, batch your messages into two checks per day.
  4. Compare after two weeks. Do you finish more of what you meant to? Do you feel less scattered? Be honest if the answer is no. Your situation may simply not suit the approach.

Keep the experiment small, and change only one thing at a time so you can tell what made a difference. Also note how you feel, not only how much you finish, since a calmer week may matter to you even if the output is similar.

The takeaway

More is not automatically more. Each task, tool and commitment brings costs in switching, upkeep, fatigue and lost slack, and those costs can quietly cancel the gains. Removing a few things sometimes frees more capacity than any new technique could. If you try it, expect modest, not dramatic, changes, and adjust to your own circumstances.

The complete guide to the art of doing less

The Art of Doing Less: Embracing Simple Living
Read the guide

Keep exploring

Guides from other topics

All topics →