The Fastest Way to Improve Efficiency at Work Is to Do Less of It

You’ve read the efficiency articles. Time-block your calendar. Prioritize by urgency and impact. Automate the repetitive stuff. Delegate what you can. Every one of those tactics works, and you’ve probably tried most of them already.

Here’s what none of them do: touch the actual list. You can time-block a task that shouldn’t exist. You can prioritize a meeting that never needed to happen. You can delegate a report nobody reads. Optimizing the wrong list just gets you through it faster. It doesn’t make the list shorter.

If your week is already compressed, that gap costs you more than it costs someone working a standard 40 hours. You don’t have the slack to optimize your way out of a list that’s too long. You have to shrink the list first, and that means deciding what gets cut before you decide how to do the rest faster.

Key Takeaways

• “Work about work,” coordination tasks like status updates, meetings, and searching for information, consumes roughly 60% of the average knowledge worker’s time, according to Asana’s Anatomy of Work Index. That’s time not spent on the skilled work you were actually hired to do.
• A keep-delegate-kill audit, sorting each recurring task by whether it needs you, needs someone, or needs to stop, does more for a compressed schedule than any time-management tactic layered on top of an unchanged list.
• Parkinson’s Law, the idea that work expands to fill the time available for it, works in your favor once you shrink your hours, but only if you also shrink your task list to match.
• Automation and delegation solve different problems. Automation removes tasks that don’t need judgment. Delegation moves tasks that need judgment to someone other than you. Neither one replaces the step of asking whether a task should exist at all.
• Cutting a meeting produces bigger time gains for less effort than shortening it, and most calendars have more to cut than their owners think.

This isn’t about being more disciplined. It’s about what actually happens to your calendar once you cut your hours and leave your task list the same size. Something has to give, and if you don’t decide what gets cut, your calendar will decide for you, usually by cutting the deep work first and keeping every recurring meeting intact. Getting the audit right is the difference between a compressed week that keeps working and one that quietly turns back into a 40-hour week with a shorter name on it.

What Is “Work About Work,” and Why Is It Eating Your Compressed Schedule?

“Work about work” is the coordination overhead that surrounds a job without moving it forward: status updates, searching for information, chasing approvals, and meetings held to talk about the work rather than do it. That’s the short answer. The longer answer is that most people can’t see how much of their week this actually consumes, because none of it feels optional in the moment.

Work About Work

“Work about work” refers to the coordination tasks, such as status updates, information searches, approval chasing, and meetings about the work, that consume time without producing the skilled or strategic output a role actually exists to deliver.

 

Asana’s Anatomy of Work Index found that knowledge workers spend roughly 60% of their time on work about work rather than skilled or strategic work, the coordination layer eating nearly two-thirds of a standard week. Source: Asana, Anatomy of Work Index

That 60% figure is for a standard week. Compress the week and the coordination layer doesn’t automatically shrink with it. The status meeting still happens. The approval chain still has the same number of steps. What shrinks is the time left over for the work you’re actually paid to produce, which is exactly backwards from what you want. This is why generic efficiency tips, do the tasks faster, batch the emails, block the calendar, run out of runway fast on a compressed schedule. They’re optimizing a layer of work that shouldn’t be there at full size in the first place.

The Keep-Delegate-Kill Audit

Here’s the framework I use, and the one I’d tell you to run before touching anything else on your calendar. List every recurring task, meeting, and report from the last two weeks. Not your whole job, just the recurring stuff, since that’s where the coordination overhead hides. Then sort each item into one of three buckets.

Keep: requires your specific judgment, expertise, or relationship, and the outcome changes if someone else does it.

Delegate: requires judgment, but not necessarily yours. Someone else could own the decision, not just the busywork underneath it.

Kill: doesn’t need to exist in its current form. Nobody acts on the output, the meeting could be a message, or the task was set up for a situation that no longer applies.

Most people find the third bucket is bigger than they expected once they actually look. Recurring meetings and standing reports are especially prone to outliving their reason for existing. Nobody cancels them because nobody owns the decision to cancel them, so they persist by default.

 

Efficiency isn’t doing the wrong things faster. It’s having fewer wrong things to do.

Why Subtraction Beats Optimization on a Compressed Schedule

Parkinson’s Law, the observation that work expands to fill the time available for its completion, comes from a 1955 essay by the British naval historian C. Northcote Parkinson. It’s usually cited as a reason compressed schedules work at all: give people less time and the task somehow still gets done. That part is real. What gets left out is the condition attached to it.

Parkinson’s Law only works in your favor if the task list actually shrinks along with the hours. If you cut your week from 40 hours to 32 but keep every meeting, every report, and every task on the list, you’re not compressing the work, you’re just doing the same volume under more pressure. That’s not efficiency. That’s a faster route to the same burnout that got most people looking for a shorter week in the first place.

This is the part optimization tactics can’t fix on their own. A better calendar layout doesn’t reduce the number of things on the calendar. A faster way through your inbox doesn’t reduce the number of emails that shouldn’t have been sent to you. The keep-delegate-kill audit is what actually reduces the list, and the optimization tactics you already know are what you apply to what’s left over.

What to Hand to Automation Instead of a Person

Automation and delegation get treated as interchangeable in most efficiency advice. They’re not. Automation is for tasks that follow a predictable, rule-based pattern and don’t require judgment: data entry, scheduling, routine status updates, recurring reports that pull from the same source every time. Delegation is for tasks that need judgment, just not necessarily yours.

The McKinsey Global Institute found that around 60% of occupations have at least 30% of their constituent activities technically automatable with currently demonstrated technology, meaning most jobs contain a meaningful slice of work that doesn’t need a human doing it manually. Source: McKinsey Global Institute, A Future That Works

The mistake I see most often on a compressed schedule is automating a task that should have been killed instead. Automating a status report nobody reads just means a machine produces the unnecessary thing faster instead of you producing it slowly. Run the keep-delegate-kill audit first. Automate what survives the kill decision and turns out to be rule-based. That order matters more than the tools you pick.

 

The Meeting Tax: When to Cancel Instead of Shorten

Meetings are the clearest example of work about work, and the easiest place to see the keep-delegate-kill audit pay off fast, because a canceled meeting returns time to everyone on the invite, not just you.

A Harvard Business Review study found that executives now spend nearly 23 hours a week in meetings, up from less than 10 hours in the 1960s, with senior managers themselves reporting that a large share of that time is unproductive. Source: Perlow, Hadley & Eun, “Stop the Meeting Madness,” Harvard Business Review

Most advice at this point tells you to shorten meetings or run them with a tighter agenda. That helps, but it optimizes something that often shouldn’t exist at full frequency. Before you shorten a recurring meeting, ask whether it can be canceled instead, or replaced with an asynchronous update that people read on their own schedule. Status meetings are usually the first candidates: if nobody makes a decision in the room, the meeting is a report wearing a calendar invite.

Cancel one recurring meeting on a trial basis. Not forever, just for two weeks. If the work still moves and nobody’s blocked, you have your answer. If something breaks, you’ve learned exactly what that meeting was actually for, which is more than most people know about their own standing meetings.

Common Mistakes When Running the Audit

Delegating the labor without the authority. If someone still has to check with you before deciding, you haven’t delegated the task, you’ve just added a step. This is the single most common way a delegate bucket item bounces back onto your own list within a month.

Auditing once and never again. Tasks that were correctly kept six months ago drift into kill territory as roles and priorities change. Treat the audit as a recurring part of workload management, not a one-time cleanup.

Killing the visible tasks and leaving the invisible ones. It’s easy to cancel a meeting you dislike attending and much harder to notice the report you generate that nobody downstream actually opens. The audit only works if you include tasks you do out of habit, not just the ones that annoy you.

Automation is for tasks. Delegation is for judgment calls someone else can make as well as you can. Neither one is for tasks that shouldn’t exist.

Start With One Cut, Not a New System

You don’t need a new productivity system to make this work. You need one honest look at your recurring calendar and a willingness to cancel something on a trial basis. Pick the meeting, report, or task you’re least sure anyone actually needs. Cancel or hand it off this week, not next quarter. See what breaks. Most of the time, the answer is nothing, and that’s the whole point of the audit: it shows you what was never load-bearing in the first place.

If you want a structured version of this to work through with your own task list, the checklists library has a format you can adapt, and it pairs well with the mechanics covered in Less Is More: Boosting Productivity in a Compressed Work Week if you haven’t run that audit yet.

Frequently Asked Questions

How can I improve efficiency at work without adding more systems?

Improving efficiency at work starts with removing tasks, not adding tools or systems on top of an unchanged list. Run a keep-delegate-kill audit on your recurring tasks and meetings first, then apply time-management tactics only to what survives. Most efficiency systems fail on a compressed schedule because they optimize a task list that was already too long to begin with.

Should I automate a task or delegate it?

Automate a task when it’s rule-based, repeatable, and doesn’t require judgment, such as data entry or a recurring report pulled from the same source. Delegate a task when it requires judgment that doesn’t have to be yours specifically. Check first whether the task should be eliminated entirely, since automating or delegating an unnecessary task just locks the waste in more efficiently.

How many meetings should I cut before I see a real difference?

Canceling even one recurring meeting on a trial basis is often enough to reveal how much of your calendar was coordination overhead rather than necessary work. Start with the meeting where no decision gets made in the room, since status updates and information-sharing meetings are the easiest to replace with an asynchronous update. The time saved compounds because it returns hours to everyone on the invite, not just you.

Does multitasking reduce efficiency at work?

Multitasking generally reduces efficiency at work because switching between tasks carries a cognitive cost each time attention shifts, even when the switch feels instantaneous. This matters more on a compressed schedule, where there’s less buffer time to absorb the lost focus. Batching similar tasks and protecting blocks for single-focus work tends to outperform juggling several tasks at once.

What’s the fastest way to start a keep-delegate-kill audit?

The fastest way to start is listing every recurring task and meeting from the past two weeks on a single page, then sorting each one into keep, delegate, or kill before making any changes. Resist the urge to fix anything mid-list. Once the full audit is visible, the kill and delegate candidates are usually more obvious than they were one task at a time.