How email created the hyperactive hive mind — and what to do about it

Executive overview

No one decided that constant digital messaging was a good way to work. Email replaced fax machines and memos, but the relentless back-and-forth communication style that followed was an unintended consequence — a case of technological determinism, not deliberate design.

Email's real impact wasn't replacing old tools; it was creating an entirely new, unrequested way of working.

The hyperactive hive mind and how it emerged

• Email replaced fax, voicemail, and memos because it was faster and cheaper — a clear pragmatic win
• The hyperactive hive mind workflow — constant ad hoc, unscheduled messaging — was never chosen by anyone; it emerged spontaneously
• Business emails grew from ~50/day to ~126/day; workers check inboxes every six minutes on average
• No memo, no Harvard Business Review piece, no leadership decision endorsed this way of working — it just happened

Why no one stopped it

• Technological determinism: tools introduced for one purpose can reshape group behaviour in unintended ways
• Historical parallel: the horse stirrup, introduced to ease riding, led to armoured knights, which led to feudalism — no one planned it
• Social feedback loops: quick replies created expectations of quick replies; the cycle of responsiveness (Leslie Perlau, Harvard) spun until everyone expected instant responses
• Ad hoc messaging mirrors how people naturally communicate face-to-face — so it felt right, even though it doesn't scale
• Hidden cost of asynchrony: moving a 5-minute conversation to email generates 15 messages, not a replacement but an explosion
• The autonomy trap in knowledge work meant no one had authority to stop it — individuals were left to figure out their own workflows

What this means for change

• Recognising that no one chose the hive mind gives permission to reject it
• The question to ask: what way of working would we actually design if we were designing from scratch?
• Process-oriented approaches — defining workflows explicitly and reducing unscheduled messages — are the alternative
• Practical starting point: audit one day of email to identify recurring processes, then redesign each to minimise unscheduled messages

Managing people-pleasing and workload in academia

• Saying yes or no to service requests has almost no bearing on tenure — promotion at research universities is driven by peer letters assessing research quality
• Teaching is a disqualifier if poor, not a booster if excellent; service matters even less for assistant professors
• Service budgets — capped, tracked allocations of service time per semester — make invisible inequities visible
• Once you know your quotas (one major committee, one minor committee, three journal reviews, etc.), use them as a concrete reason to decline
• Saying "I don't want to do this and I don't think I'd be good at it" is a complete and legitimate response

Reducing browser tab overload

• Excessive open tabs create visual clutter and constant attention pull even when you're not reading them
• Solution: keep a plain text file (working memory.txt) on every desktop as an external working memory
• Paste links with short titles into the file rather than keeping tabs open; organise by category using caps-lock headers
• At day's end, move useful links into a permanent note system or delete them
• A plain text file also works for inbox processing, drafting, capturing tasks, and thinking through plans

Pursuing skill and mission without the passion trap

• The "follow your passion" model is too simple — passion typically grows from skill, not the other way round
• For a PhD student: write well-crafted papers at a steady rate with good collaborators; use those to build expertise and publication track record
• From that foundation, a mission becomes visible through the adjacent possible — the space of new ideas accessible once you're at the cutting edge of a field
• Mission (a clear, worthwhile direction) amplifies passion for work; you can't identify a good mission without first developing rare and valuable skills
• Skill-building requires: a concrete project, deliberate practice pushed past comfort, feedback mechanisms (problem sets, coursework), and time-blocked regular sessions

Digital minimalism: navigating inconvenience vs pain

• Inconvenience (can't check email on the go) is acceptable and expected when removing technology
• Pain (unable to contact a meeting contact, blocked from essential banking) requires a targeted response
• Targeted response: add only the specific app causing pain — on a tablet if possible, on a minimal smartphone if necessary — without reintroducing the full distraction ecosystem
• Alexa and similar devices exist primarily as data collection to train natural language AI models for commercial enterprise use — not because the home use case is profitable