Asana surveys thousands of knowledge workers every year for its Anatomy of Work index, and the headline number barely moves: about 58% of the workday goes to "work about work." Not the job. The coordination around the job: chasing statuses, searching for documents, re-reading threads to find a decision, sitting in meetings about the work, writing reminders to people who owe you things.
Line that up with McKinsey's finding that email alone consumes 28% of the workweek and a picture emerges. The biggest cost center in most professional workdays isn't a project or a client. It's the connective tissue, and nobody budgets for it.
What busywork actually is
A working definition: busywork is coordination that produces no output. It's real effort, it fills a calendar, and at the end of it nothing new exists. The recognizable species, most of them living in your inbox:
- Status chasing. "Any update on this?" sent, received, and answered, times a hundred a month.
- Archaeology. Scrolling a 30-message thread to find the version, the decision, or the attachment.
- Human routing. Forwarding things to the person who should have gotten them directly.
- Memory work. Keeping track of who owes you what, and noticing when they've gone quiet.
- Re-reading. Opening the same email a fourth time because you didn't decide anything the first three.
Why it grows even when headcount doesn't
Coordination cost scales with connections, not output. Fred Brooks made this argument about software teams in 1975, and it generalizes: every added teammate, client, or tool multiplies the messages that need reading, answering, and tracking. Your actual work grows linearly at best. The busywork around it compounds. That's why last year felt busier than the year before even though the job didn't change.
There's an attention tax on top of the time tax. Gloria Mark's research at UC Irvine puts the cost of refocusing after an interruption at roughly 23 minutes, and busywork is almost entirely made of interruptions: each ping is small, and the recovery isn't.
Cutting it structurally
Advice like "protect your mornings" treats a structural problem as a motivational one. The durable fixes change the structure:
- Reduce arrivals. Fewer cc's, notifications filtered out of the inbox, status meetings replaced by short written updates. Every message that doesn't arrive is one nobody processes. Our email management system covers this layer.
- Make commitments visible. Half of status chasing exists because the answer lives in someone's head. One shared list of who-owes-what removes the need to ask.
- Automate the tracking and chasing. Following up is the most mechanical work a professional does: check what's outstanding, notice what's overdue, write a polite nudge. Machines do this without forgetting and without dreading it.
The email-shaped chunk is the biggest one
Since email is where most busywork lives, it's the place where automation pays back fastest. Pidgy takes the mechanical layer off your Gmail or Outlook inbox: it reads everything, sorts what needs you from what doesn't, turns buried requests into tasks, keeps the who-owes-you-what list automatically, and drafts the chasers and routine replies for your approval. The archaeology, the memory work, and the re-reading go away. What's left is the short list of things that actually need a human, which was the job all along.
