A World Without Email: Reimagining Work in an Age of Communication Overload

Miles: Late in twenty ten, President Obama appoints Nish Acharya to run innovation and entrepreneurship at the Department of Commerce. The job means coordinating twenty six federal agencies and more than five hundred universities around a hundred million dollars of funding.

Miles: A few months in, on a Tuesday morning, a note comes round from the technology staff. A virus is in the network and they're taking it down. Two days, maybe. Then Homeland Security advises keeping it dark, and every computer, laptop and printer in the office is marked for destruction. The staff call it Dark Tuesday. The outage lasts six weeks.

Miles: And his work gets better. He goes out and meets people face to face. His meetings run long enough to get to the bottom of hard problems. He finds empty stretches in his day, and out of them come two ideas that set his agenda for the following year.

Miles: Today: A World Without Email, by Cal Newport. In two sentences: the trouble was never the inbox, it's the way of working that grew up inside it, one endless unscheduled conversation everybody keeps half an ear on. The cure is deciding in advance how work gets handed out and talked about, so the conversation can stop. And later Nora argues that one group pays more for that conversation than the rest, and shows you where the evidence runs out.

Miles: Sixty Books. Presented by Stoar Consulting and Coaching.

Miles: Book forty four, and this is Sixty Books. I'm Miles. The terms haven't moved: one management book per episode, sixty chosen from the best of the last hundred years, each one asked the same two questions. What does it hand a leader or a team whose minds don't run on the factory settings. And what survives now that AI sits in the working day. Nora has the research, and she's met this author before.

Miles: Nora, Burkeman left us last time with the day getting eaten, and a strong hint that the schedule wasn't the one doing the eating.

Nora: It's whatever has no slot. A calendar holds the things somebody agreed to in advance. What fills the gaps between them is the message nobody scheduled, and this whole book is about that message.

Miles: And it's Newport again, two books after Deep Work.

Nora: Same author, different target. Deep Work handed the job of guarding attention to the individual. When this one came out, he told an interviewer he'd naively assumed organizations would make room for focus once they understood its value. They didn't, so this time he goes after the way the office runs.

Miles: So the sequel blames the office.

Nora: Yeah. The sequel blames the office. Which, for a productivity writer, is like a diet author admitting the problem was the vending machine bolted to the wall outside your door.

Miles: And restocked all day.

Nora: Every six minutes, by one count. Hold that number. It gets a hard look later.

Miles: Back to the man with no network. What does the book make of him?

Nora: He's the opening scene, and Newport tells it as a puzzle. Acharya told him the first stretch was close to hell. He worried about missing something that mattered, and arranging a meeting took real effort. But nothing stopped. He went and saw people, he had room to think, and the work improved.

Miles: And Newport's reply?

Nora: That most of what the inbox did for him could have gone to an assistant: the daily checking, the meeting logistics. Acharya was stunned by the idea that he might not need email at all.

Miles: Which is a large claim to build on one federal office.

Nora: Fair, and the book knows it. Acharya's a story, not a study. He's there to make one thing visible: the stream of messages and the work itself are two different activities that have grown into each other.

Miles: And the stream has a name.

Nora: The hyperactive hive mind. His definition is a workflow centred on ongoing conversation, fed by unstructured and unscheduled messages. And he gives it its due. It's simple, it's flexible, nobody needs training, and in a very small group it's quick.

Miles: Then where does it go wrong?

Nora: Past a handful of people. The introduction backs that with four figures: a hundred and twenty six work emails per worker per day by twenty nineteen, a check of email or chat about every six minutes, seventy seven inbox checks a day in a field study from the University of California, Irvine, and more than three hours a day on work email. Four figures of four quite different kinds, which is a job for the evidence segment.

Miles: The author, briefly, since he had his hearing two books back.

Nora: Briefly. Cal Newport is a full professor of computer science at Georgetown, and his research is the theory of distributed systems: what separate machines on a network can and can't get done together. And here the field matters. Newport has described how theorists in his area study asynchrony, meaning no real time back and forth, and found that taking the real time exchange away makes coordination harder and costs many more messages. This book carries that from machines to people. A meeting two colleagues could settle in a two minute conversation turns into a dozen emails.

Miles: And the book itself.

Nora: March of twenty twenty one, three hundred and twenty pages, in two parts. Part one is the case against: email reduces productivity, email makes us miserable, email has a mind of its own. Part two is four principles for working without the hive mind: attention capital, process, protocol and specialization.

Miles: That third chapter title is doing a lot of work.

Nora: It's the history chapter. In Newport's account, in the nineteen eighties a large computer maker installs internal email for its own staff, expecting it to replace memos, notes and voicemail one for one. In the first week the traffic runs five to six times what anyone predicted. His reading is that nobody chose the hive mind. It grew, faster than any group could have planned it.

Miles: And once it's there, it feeds itself?

Nora: He borrows the mechanism from Leslie Perlow at Harvard Business School, who calls it a cycle of responsiveness. Somebody replies faster, colleagues come to expect it and ask for more, replying fast becomes the price of looking committed, and the loop tightens without anyone deciding it should.

Miles: The case against, then, in the book's order.

Nora: Chapter one opens on a founder Newport calls Sean, who ran a seven person software studio in London. Email at first, from waking until night. Then they moved to a chat tool, opened it to their largest clients, and Sean ended up working until one in the morning, because those were the only quiet hours left. When he checked which feature of the new tool his team used most, the winner was an add-on for posting animated GIFs.

Miles: So the busiest corner of the new system was the reaction pictures.

Nora: It was. Two of his project managers then quit, burned out, in his word.

Miles: And the research under the stories?

Nora: Starts old. The first published measure of what it costs to switch between tasks is Arthur Jersild's, from nineteen twenty seven: people alternating between two tasks were slower than people doing one at a time. Then Newport brings in Gloria Mark at Irvine, and a paper from twenty oh four whose title he clearly enjoys: Constant, Constant, Multi-tasking Craziness. Victor González and Mark shadowed fourteen analysts, developers and managers at one outsourcing firm, four hundred and seventy seven hours of observation in all. People stayed with one stream of work for about eleven and a half minutes before switching. They were interrupted about twenty five times a day.

Miles: And email was the main culprit.

Nora: Not in that study. Colleagues walking up to the desk, and phone calls, pulled people off task more than electronic alerts did. Keep that for the end of the episode.

Miles: Chapter two is misery.

Nora: And Mark ran the experiment that chapter's argument invites. In twenty twelve, with Stephen Voida and Armand Cardello, she switched off email for thirteen staff at a scientific research organization for five working days, against a few days of normal use, logging every move between windows. Without email, people switched windows less often and stayed in each one longer. Heart rate monitors pointed toward lower stress, but only seven people gave usable readings, and the difference fell short of significance.

Miles: So the switching result is solid and the stress result is a lean.

Nora: Within thirteen people, yes. Chapter three is the history we've covered, and then part two turns to the cure.

Miles: Attention capital.

Nora: It starts from Peter Drucker, who coined the phrase knowledge worker in nineteen fifty nine and argued in the sixties that such workers can't be closely supervised and have to direct themselves. Newport's complaint is that management heard that as permission never to look at how the work moves. Each person became a black box, and the hive mind filled the space.

Miles: And the alternative?

Nora: Ford. Before nineteen thirteen, the book says, putting a Model T together took more than twelve hours of labor. Once the cars moved past workers who stayed put, it took about ninety three minutes. Nobody's effort changed. The arrangement did. Newport's claim is that knowledge work has never had that moment, and that its raw material is the brain's capacity to focus, which he calls attention capital.

Miles: That analogy will make some people nervous.

Nora: He says so himself. Line work was draining, and people became extensions of the machinery. What he takes from Ford is the willingness to experiment with the arrangement, not the conveyor.

Miles: Process.

Nora: Decide in advance how each recurring kind of work moves. His main tool is a task board: columns for stages, cards for tasks, and the talk about a task lives on its card, not in anybody's inbox. One marketing firm in the book gave every client its own board. Add a short regular status meeting where each person says what they did, what's next and where they're stuck, and a lot of messages never get written.

Miles: Protocol.

Nora: Rules for when and how coordination happens. Office hours for questions that can wait a few hours. A way of booking a meeting that doesn't need a thread. Client terms written into the contract, so everyone knows when to expect an answer and how to reach someone in a real emergency.

Miles: And specialization.

Nora: Do fewer things, better, and own them. Move the administrative load to support staff, organized so they don't become a fresh source of interruptions. And work in sprints, often two weeks on a single goal, with outside contacts told in advance that you're hard to reach.

Miles: Huh.

Miles: The evidence. Start with those four figures.

Nora: They arrive together, and they aren't alike. The hundred and twenty six is an estimate, and that's the book's own word. The six minutes is a time tracking company's data on more than fifty thousand of its own users, the median gap between check-ins, and everyone in that pool installed software to watch their own time. The three hours is a software company's annual survey of about a thousand American workers estimating their own day. All three are industry data. They point the right way, and none was built to measure precisely.

Miles: And the seventy seven?

Nora: That one's different. It's peer reviewed, and unlike the residue study two books back, it watched real inboxes. Mark again, with Shamsi Iqbal, Mary Czerwinski and colleagues, at a computing conference in twenty sixteen. Forty workers in the research division of one large company, about twelve days each, software logging every switch to email and a heart rate monitor worn on the chest. The more time someone spent on email in a given hour, the higher their measured stress. The more time on email across a day, the lower they rated their own productivity.

Miles: And the cure everyone recommends is batching.

Nora: Which they tested. Eleven of the forty were batchers, with most of their email packed into a few hours. Batching made no detectable difference to stress, and batchers rated themselves more productive only on heavy email days. It's correlational and from one workplace, so it can't tell you what causes what.

Miles: Is there anything with a manipulation in it?

Nora: One. Kostadin Kushlev and Elizabeth Dunn, Computers in Human Behavior, twenty fifteen. A hundred and twenty four adults in Vancouver, about two thirds of them students, each spending one week told to check email three times a day and one week with no limit, in random order. In the limited week they reported lower daily stress.

Miles: By how much?

Nora: Not much. About one point four six against one point five five, on a scale from zero to four. And the limited week wasn't three checks: people averaged nearly five, against twelve and a half when nothing was limited. The authors call their study exploratory, and write that checking less often is by no means a panacea. Then a lab result that points somewhere uncomfortable. Mark again, with Daniela Gudith and Ulrich Klocke, twenty oh eight. Forty eight people, mostly German students, answered a stack of work emails, sometimes interrupted every couple of minutes and sometimes left alone. Interrupted, they finished faster, with no more errors. They also reported more stress, more frustration, more time pressure and more effort.

Miles: So the work survives and the person pays.

Nora: Over twenty minutes, in a lab. Which is close to Newport's whole argument in miniature.

Miles: And the prescriptions?

Nora: The thinnest layer. The four principles rest on interviews, company stories, and a survey of his own readers in twenty nineteen, more than fifteen hundred replies from people who chose to answer, and he calls their testimonies anecdotal himself. I found no trial of a team moving from the hive mind to boards and protocols and measuring what happened. One reviewer, in April of twenty twenty one, found the diagnosis more convincing than the cures and thought the title promised more than the book delivers, which Newport himself concedes.

Miles: Tier statement, then.

Nora: This is practitioner literature, a working computer scientist's argument for general readers, not peer reviewed research. The diagnosis stands on small field studies, a short lab experiment and one modest randomized crossover, which agree on direction and report small sizes. The cures stand on cases. So on my running score, the claim that the hive mind costs attention and calm has held up in miniature, and the claim that these principles fix it hasn't been tested. Neither of those is a mark against the author.

Miles: Our half.

Nora: And it opens with a claim, so let me mark it as one. Unscheduled interruption is the most expensive thing an open inbox does to people with ADHD, as a group, and this book hands you the currency to price it in. That goes past the evidence, and I'll show you where.

Miles: Start with what you went looking for.

Nora: An interruption study with an ADHD sample. Every email and interruption study in this episode recruited general workers or students. I didn't find one, at work or in the field, that recruited adults with ADHD and measured what interruptions cost them. So the plain answer is that nobody has priced it directly.

Miles: Then what is there?

Nora: Lab work on distraction, and one study comes close. Sophie Forster, Nilli Lavie and colleagues, Neuropsychology, twenty fourteen. Seventeen adults diagnosed with ADHD through a London clinic or support groups, and a matched comparison group, doing a letter search on a screen. On one trial in ten a bright cartoon character appeared that had nothing to do with the task. It slowed the ADHD group significantly more than the comparison group.

Miles: So an irrelevant thing pulls harder.

Nora: In that group, in that lab, on that task, yes. And when the search was made more demanding, the cartoon's pull dropped, as much for the ADHD group as for everyone else. A small sample, fifteen of the seventeen tested a day after their last dose of stimulant medication. Group findings, not a description of anybody in particular.

Miles: And alerts in daily life?

Nora: Kushlev and Dunn again, with Jason Proulx, twenty sixteen. Two hundred and twenty one undergraduates, not an ADHD sample, one week with phone alerts on and one week with them silenced, in random order. With alerts on, they rated themselves higher on a checklist of inattention and hyperactivity symptoms. The differences were about a tenth of a point on a four point scale, and the authors say outright that this doesn't show notifications cause ADHD.

Miles: So here's the argument.

Nora: Here's the join, and it's mine. If a salient, irrelevant interruption costs adults with ADHD more in the lab, and if alerts raise everyone's self rated distractibility in daily life, then the hive mind probably doesn't charge a flat rate. It charges more to the people whose attention gets pulled hardest. Attention capital gives you the unit. Nobody has done the arithmetic.

Miles: And why would this book help where the usual advice doesn't?

Nora: Because the usual advice is personal discipline, and the evidence on personal discipline is unkind. Told to check three times a day, Kushlev's participants managed about five. Batching on your own didn't move stress in the Irvine data. Newport takes the decision out of the individual's hands and puts it into how the team coordinates: office hours, a board, a fixed meeting. A protocol works for the person whose attention is pulled hardest without that person disclosing anything or asking for anything.

Miles: Cautions.

Nora: Two. The first is that nobody has tested a process and protocol workflow with neurodivergent employees as the outcome. Forster's lab, Kushlev's students and Mark's offices are three separate literatures, and the line running through them is drawn by me.

Miles: And the second.

Nora: Protocols are only as kind as the people who write them. Office hours set by the busiest person on a team fit that person's rhythm. The book itself says the people a procedure affects should help design it. So build the board and the hours with the people who'll live inside them, and leave a way to reach someone when a question can't wait.

Miles: Right.

Miles: One minute, on our terms. A World Without Email says the inbox isn't the problem. The problem is a way of working built on constant, unscheduled conversation, and it spends attention and calm that nobody budgets for. For anybody leading a mind that runs on different settings, or working inside one, here's Monday. Find the one kind of request that throws off the most messages on your team and give it a home: a board, a form, a standing slot, anything but a thread. Set office hours for the questions that can wait, and say plainly how to reach someone when one can't. Write those rules with the people who'll follow them, not for them. And stop handing out check less often as personal advice, because the studies say it barely holds. Change the arrangement, so nobody has to win a willpower contest to get a morning's work done.

Miles: The machines.

Nora: The standing caution about these tools waits after the music, unchanged, so I'll point you there and spend this on what Newport's book makes of them.

Miles: Go on.

Nora: The obvious use is answering email faster, and there's a big field experiment on that. Sixty six large firms, about seven thousand knowledge workers, some picked at random to get an AI assistant built into the software they already used for email, documents and meetings, over six months. Those who used it spent about two hours a week less on email, from a starting point of nearly twelve, and worked less outside normal hours. But the same paper found no detectable change in how much work people did or what kind. It's a working paper that hasn't been through peer review, and it was run by researchers at the company that makes the tool. Read beside this book, the meaning is plain: the hive mind got cheaper to run, and it's still running.

Miles: So where would Newport put the thing?

Nora: On the process side, never the reply side. Hand it last month's thread about a recurring request and have it draft the form, the office hours note or the client terms that would have made the thread unnecessary, then rewrite that draft with the team. Describe how a piece of work moves and have it propose the columns for a board. Have it boil a long chain down to one card with the decision on it.

Miles: Send us out with something to try.

Nora: Before you let a tool write your replies, ask what the reply is for. A faster answer to the hive mind is still an answer to the hive mind. The better use is building the process that means the message never has to be sent.

Miles: That's A World Without Email.

Miles: Next time: Peopleware, by Tom DeMarco and Timothy Lister. Nearly everything Newport argues about shielding a working mind from interruption, two software consultants had in print in nineteen eighty seven, when the culprit was a ringing desk phone and an office with no door, and the trade has spent the decades since rediscovering it.

Nora: And in that shadowing study, people walking up to the desk pulled workers away more than any alert did, so the room was always half the story.

Miles: Thanks for the company in a crowded inbox, Nora.

Nora: Glad it was this one.

Miles: Onward.

Miles: Sixty Books is made at Stoar Consulting and Coaching. Logan Williamson is a Licensed Professional Counselor in Texas and Louisiana. You heard one book read closely, for people who run teams and the people on them. It wasn't coaching, it wasn't counseling, and nothing in it was a finding about you.

Nora: Sources for each claim are on the episode page, with the full transcript. Book forty five lands in two days.

Miles: A word on who made this, then one note. The voices you've been hearing are generated. There's no Miles and no Nora, nobody here holds a license in anything, and not a word of this was aimed at you in particular. AI helps draft every script, and Logan Williamson, a Licensed Professional Counselor in Texas and Louisiana, at Stoar Consulting and Coaching, edits each one and approves it.

Nora: And one note about the AI segment. The evidence that these tools help neurodivergent people at work is early. There are controlled trials now, but they measure things like conversation skill rather than how a job actually goes, and for work itself most of what exists is individual providers reporting success. So take it as promising and not proven. The tools also get rebuilt every few months, so whatever you set up today is built on something that moves.