Email eats 28% of the work week. Here is how to get a day back.

Email is the job that surrounds the job. The McKinsey Global Institute put a number on it that has not moved much in a decade, and a Vancouver lab put a number on what it costs you to keep checking.

The size of it

MGI's 2012 Social Economy report estimated that the average interaction worker spends 28% of the workweek reading and answering email, and another 19% searching for information. That is more than eleven hours in a forty-hour week. Later surveys have found similar or larger figures, and the arrival of chat tools added to the total rather than replacing it.

The cost of checking

Kushlev and Dunn randomised 124 adults to check email only three times a day for a week, and freely the other week. Stress was significantly lower in the limited week. The mechanism is the one Gloria Mark documented in office workers: an interruption costs about 23 minutes to fully recover from, and an open inbox is a machine for producing interruptions.

Where the hours actually go

Not reading. Reading is fast. The hours go to drafting replies, deciding what needs a reply at all, and remembering to follow up on the ones that went unanswered. Those three tasks are the ones a machine can do well: drafting is language, triage is classification, and follow-up is a schedule.

Getting the day back

Two changes carry most of the benefit. Batch: open the inbox two or three times a day and treat it as a task, not a feed. Automate the mechanical parts: let a drafter write the first version of every reply, let a sequence carry the follow-ups, and spend your attention on reading and deciding. PeakLook is built for the second change: it scans the Focused inbox, drafts replies threaded to each conversation, runs follow-up sequences server-side, and stops the moment someone replies. What is left is the part only you can do.