Email

Automate Office Work  ·  Episode Resources

AI Won't Fix Your Email Problem.
Here's What Actually Will.

Every framework, checklist, and tool from the episode — in one place. Work through these with your team.

Runtime ~3 hours
Frameworks 5
Checklists 4
Interactive items Check them off

This page contains every resource from the episode. The checklists are interactive — check items off as your team works through them. Use this page in a team meeting, a lunch-and-learn, or a process review session.

The core argument: Email is not a database, a task manager, or a knowledge base. Every time you use it as one, you create a disaster that compounds over time. The answer isn't AI that writes more emails. The answer is designing processes so the email never needs to be sent in the first place.

00

The Scale of the Problem

121 emails received per person per day, on average
28% of the working week spent managing email
500+ hours per year per employee — just on email
€2.75M annual cost for a 100-person team at €50/hr average
01

Email: Right Tool vs. Wrong Tool

Email IS the right tool for…
  • 1External parties who don't share your internal systems
  • 2Formal documentation requiring an external record (contracts, receipts, legal notices)
  • 3One-way broadcasts that require no response
  • 4Simple single-question exchanges (two lines in, two lines back)
  • 5Cross-timezone asynchronous communication where real-time isn't practical
Email is NOT the right tool for…
  • ✗Project tracking and task assignment
  • ✗Data collection and storage
  • ✗Approval workflows
  • ✗IT, HR, or support request management
  • ✗Status updates
  • ✗Knowledge management and documentation
  • ✗Onboarding checklists
  • ✗Complex multi-party decisions
02

The 12 Problems — Complete Diagnosis

Check off the ones you recognise in your organisation. Use this as a team discussion prompt.

  • Email as Database. Using the inbox to store customer info, project details, decisions, and institutional knowledge. It has no schema, no querying, no validation, no version control.
  • The Asymmetry Problem. It takes 30 seconds to send an email that creates 2 hours of work. No friction means no thoughtfulness. Free-text requests with no required fields.
  • Inbox as To-Do List. Using unread flags and starred emails as a task system. No due dates, no priorities, no delegation, no progress tracking. Tasks buried and forgotten.
  • Thread Chaos. 40+ message threads with no resolution, no summary, branching topics, replies to old messages, and new people added mid-thread with zero context.
  • Zero Access Control. Once sent, an attachment can be forwarded to anyone. No version control. No revocation. No audit trail. No permissions.
  • CC Culture Toxicity. CC used for political coverage, public shaming, and self-protection. BCC used deceptively. Massive noise for people who don't need to see every message.
  • Knowledge Burial. Information hidden in personal inboxes, unsearchable, outdated silently, duplicated across five slightly different versions with no authoritative source.
  • The Departure Time Bomb. When someone leaves, the knowledge in their inbox leaves too. Projects orphaned. Client history lost. Institutional memory walks out the door.
  • The "Who Do I Email?" Problem. Processes requiring people to know the right person's name and email address. Zero fault tolerance. Breaks for every new employee, every role change, every absence.
  • The Approval Chain Black Hole. Approvals scattered across multiple inboxes, forwarded to different threads, no record, no SLA, no audit trail. A one-week process that should take hours.
  • Status Update Tax. "Just checking in on the status of…" emails exist only because the status isn't visible anywhere. This is the tax you pay for not having proper project visibility.
  • Passive-Aggressive Language. "Per my previous email." "Going forward." "Please advise." These phrases signal broken relationships and broken processes — not communication problems.

Team Recognition Score

Check the problems you recognise in your organisation

0 of 12 checked

03

The DRAIN Framework

A structured audit for your team's email-based processes. Run this once to find where the dysfunction is concentrated — then fix the worst offenders first.

D
Define Your Categories
Classify one week of sent and received email into ten buckets: External / Status requests / Task assignments / Approvals / Information transfer / Coordination / Social / Escalations / Notifications / Process requests. Do this as a team, independently, then compare.
R
Rate the Damage
For each category, score Volume (H/M/L) and Dysfunction (H/M/L). High × High = fix first. High × Low = monitor. Low × High = fix for risk. Low × Low = leave alone. This is your prioritisation matrix.
A
Audit Root Cause
For each priority category ask: Why does this happen by email? Who sends/receives? What data fields appear? What happens after receipt? What goes wrong most often? These answers become your replacement system requirements.
I
Identify the Right Tool
Map each category to a tool type: ticketing system, project management, approval workflow, CRM, form, wiki, scheduling tool, or chat. Match complexity to scale. A 10-person team doesn't need Salesforce. A 500-person team shouldn't use a spreadsheet.
N
Navigate the Change
Set a hard date. Onboard in under 5 minutes. Get leadership to model it first. Dual-run with a sunset date. Create feedback loops and act on them visibly. Culture change is harder than the technology.
N
Normalize the Baseline
Celebrate wins with real numbers. Document every new process in the wiki. Integrate into onboarding Day One. Run the DRAIN audit again annually — organisations change and new drift accumulates.

The Priority Matrix — Where to Start

← Dysfunction →
Fix First High Volume + High Dysfunction This is where the most productivity is being destroyed. Start here, no exceptions.
Fix for Risk Low Volume + High Dysfunction Not frequent, but when it goes wrong it really goes wrong. Fix for morale and risk management.
Monitor High Volume + Low Dysfunction A lot of it, but it mostly works. Monitor for drift, don't over-invest in changing it.
Leave Alone Low Volume + Low Dysfunction Not worth the change management cost right now. Revisit next year.
↑ High Volume ↑ Low Volume
04

Process Maturity Levels

Where is your organisation today? Where do you want to be in 12 months?

1
Inbox as Operating System
Email is everything — the task list, archive, approval system, project tracker, and knowledge base. Fragile, person-dependent, and does not scale.
2
Islands of Tools, Sea of Email
Some tools exist (Slack, a CRM, a PM tool) but there's no clarity about what goes where. Email still bridges everything. Often more stressful than Level 1.
3
Defined Channels, Structured Intake
Written norms exist. Intake forms are in place. New employees find the right system without asking for an email address. Inbox is mostly external. Achievable in 12 months.
4
Data-Driven & Measurable
Processes are measured — resolution times, SLA compliance, bottleneck identification. Data drives improvement decisions. Can report on process health without manually reading emails.
5
Proactive & Self-Improving
Routine work is automated based on patterns. Humans handle exceptions. AI is used within structured systems — not to read and write more emails. The target state.
Team self-assessment questions
  • Q1Can a new employee find where to submit a request on their first day without asking anyone?
  • Q2When someone leaves, does their project history survive them?
  • Q3Can management see project status without requesting a status update email?
  • Q4Is your inbox mostly external, or mostly internal process noise?
  • Q5Do you have SLA data for your internal support processes?
05

The Email Replacement Tool Map

For every category of work currently running through email, there is a purpose-built tool that does it better. Find your matches here.

Currently done by email Replace with this type of tool Example tools
IT support requestsTicketing / helpdesk systemJira Service Mgmt, Freshdesk, Zendesk
HR requests (leave, expenses, onboarding)HR self-service portalBambooHR, Personio, Workday
Purchase & spend approvalsApproval workflow toolBuilt into most finance/HR/PM tools
Project status updatesProject management dashboardAsana, Monday.com, ClickUp, Jira
Customer tracking & follow-upCRMSalesforce, HubSpot, Pipedrive
Client onboarding data collectionIntake form → CRMTypeform, JotForm, HubSpot forms
Internal knowledge questionsSearchable wiki / knowledge baseNotion, Confluence, SharePoint
Document collaborationCloud storage with link sharingGoogle Drive, OneDrive, Dropbox
Meeting schedulingScheduling toolCalendly, Microsoft Bookings, Cal.com
Team task coordinationProject management toolAsana, ClickUp, Basecamp, Linear
Team discussion & Q&AChat toolSlack, Microsoft Teams
Structured data collectionFormsMicrosoft Forms, Google Forms, Typeform
The email-as-notification principle

Email should be a notification layer that points to where work actually lives — not the place where work lives. The ideal email reads: "A task has been assigned to you in Asana: [link]" or "Your approval is needed for Request #1247: [link]." The email alerts. The system contains.

06

The 10 Rules of Every Email You Send

Even after fixing your processes, you will still send some emails. Make every one count. Check these off as you review an email before sending.

01
Single, stated purpose

Complete this sentence before writing: "This email exists to ___." If you can't complete it in one line, don't write it yet. Valid completions: to inform / to request approval / to ask a specific question / to request a specific action by a date / to confirm in writing.

02
The one-minute test

If it takes more than one minute to write — pick up the phone. The friction you feel while drafting is your brain telling you this needs more bandwidth than email provides. Call first. Confirm in writing after.

03
Maximum three paragraphs

No email should exceed three short paragraphs. No paragraph should exceed four sentences. If you need more room, write a document, attach it, and keep the email body to a short summary and a clear ask.

04
The three-turn rule

Any exchange requiring more than three rounds of replies should become a meeting. Turn one: question or request. Turn two: response or clarification. Turn three: final confirmation. If you're heading into turn four, stop and schedule a call.

05
No passive-aggressive phrases

"Per my previous email," "going forward," "please advise," "not sure if you saw my last email," "hope this helps!" — all banned. Mean what you say. If you can't say it directly, the problem is not your word choice.

06
Every recipient must be defensible

To = must take a specific action. CC = must be informed and has no other way to be. BCC = almost never justified in business correspondence. Default to fewer recipients. Every unnecessary name has a real productivity cost.

07
Subject lines are navigation tools

The recipient should know the purpose and required action before opening the email. Use prefixes: [FYI], [ACTION NEEDED], [DECISION NEEDED], [URGENT] (only when genuinely urgent). Update the subject line if the topic changes mid-thread.

08
State the ask before the context

Lead with what you need. Then explain why. Most people write it backwards — three paragraphs of context, then the ask buried at the end. By then the reader has already lost the thread.

09
Explicit ask with an explicit deadline

"Let me know your thoughts" is not an ask. "Could you review the attached and send me feedback by Thursday 5 PM?" is an ask. If there's no deadline, say so explicitly: "No rush — whenever you have 15 minutes in the next couple of weeks."

10
Reply promptly or set expectations

Either reply, or send a 15-second acknowledgment: "Got this — I'll come back to you by Thursday with a proper answer." That one sentence eliminates three days of follow-up anxiety and additional email volume.

07

The Banned Phrases

These phrases don't exist because people are rude. They exist because email is the wrong venue for the conversations that cause them.

Per my previous email Translation: "I already told you this. I'm documenting that you didn't act on it." Weaponised documentation. Pick up the phone instead.
Going forward Translation: "You've been doing this wrong and I'm formally correcting you in writing." Have the conversation. Don't put corrections in email.
Please advise Vague and passive. Say what you actually need: "Could you let me know how to proceed with X by Thursday?"
Not sure if you saw my last email You know they saw it. Try: "Following up on [topic] — is there anything blocking this I can help with?"
Hope this helps! Tacked onto a correction or a barely sufficient answer. If it helps, it will help without being told to.
As discussed Often used as a gotcha — creating a paper trail of a verbal commitment. When used this way, it signals broken trust, not good communication.
Looping in [name] as they may have context Usually means: "I don't want to be responsible for this anymore." Have the conversation about ownership instead of forwarding the responsibility.
URGENT!!! (when it isn't) If you mark everything urgent, nothing is urgent. Using ALL CAPS urgency is an admission that your escalation process is broken. Fix the process.
08

Action Items — Starting This Week

Don't try to fix everything at once. Small improvements compound. Start with one item from each tier.

Individual — You can do these yourself

  • Audit your email habits for one week. Track: emails sent/received per day, time spent in email, and which categories (from the DRAIN framework) consume the most time. Set a baseline before trying to improve anything.
  • Unsubscribe ruthlessly. If you haven't opened the last five emails from a sender, you won't open the next one either. Reduce inbound volume at the source.
  • Batch-process email at set times. Check email only at 9 AM, 1 PM, and 4 PM. Turn off all real-time notifications. React less. Think more.
  • Move one regular email communication to a better tool this week. Weekly status updates → PM tool. Common knowledge questions → wiki page. Meeting scheduling → calendar link. Pick one thing and move it.
  • Create templates for your three most-sent emails. Common requests, status updates, standard answers. Saves time and ensures you always include the right context.

Team — Requires one conversation

  • Run the 12 Problems checklist together. Have everyone independently check the problems they recognise, then share and compare. The patterns that surface are your starting points.
  • Agree on one email norm and commit to it for 30 days. Start small: no reply-all unless everyone needs it; subject lines must indicate action required; all IT requests go through the form. One norm. One month. Measure it.
  • Move one process out of email — together. Not unilaterally. As a team. Choose the most painful high-volume, high-dysfunction process from the matrix and replace it with the right tool.
  • Start a shared knowledge base for common questions. Answer your five most-asked questions once, in writing, in a shared location. Link to it when someone asks by email. Build it up over time. This is how institutional memory is built.

Organisation — Requires leadership

  • Calculate the cost of email dysfunction and present it to leadership. Use the formula: employees × 11 hours/week × hourly cost. Make it a financial problem, not a culture complaint. Leadership responds to numbers.
  • Write and publish official email norms. When to use email. When not to. What the alternatives are. Subject line standards. Response time expectations. Written down. Part of onboarding.
  • Pilot better tools with one team, measure results, then expand. Don't change the whole company at once. Pick one team, tool them up properly, train them well, measure the before/after. Use them as the proof of concept.
  • Require leadership to model the behaviour first. The CEO submits IT requests through the ticketing system. The CFO uses the approval workflow. Leadership bypasses = everyone bypasses. There are no exceptions.
  • Integrate new process norms into Day One onboarding. Every new employee learns: here are our systems, here is what each one is for, here is how to submit your first request. Not folklore. Not trial and error. Standard.
Your two homework items
  • 1 Audit your last 50 received emails. For each one, ask: was email the right tool for this? Put each into a bucket. Count the buckets. The results will show you exactly where the dysfunction is concentrated.
  • 2 Pick one improvement and start this week. Not this quarter. This week. One form. One wiki page. One process moved to the right tool. Small improvements compound. Start there.
Automate Office Work  ·  "AI Won't Fix Your Email Problem. Here's What Actually Will."

Your Email Habits Are Killing Productivity – Here’s How to Fix Them

We’ve all been there: staring at the 10th email in a thread that could’ve been resolved in a three-minute phone call. Or digging through a bottomless inbox for a critical piece of data that should’ve lived in a project management system. Let’s stop pretending email is the Swiss Army knife of communication—it’s not.
Email is a tool, not a cure-all. When misused, it creates chaos, slows progress, and buries critical information. To fix this, we need to rethink when we use email, where we store information, and how we structure communication.

1. If it takes longer to type than to talk, pick up the phone.

Email is asynchronous—great for non-urgent updates, terrible for real-time problem-solving. If you’re drafting a 500-word essay to explain a complex issue, you’re wasting time. Worse, you’re inviting a days-long thread of misinterpretations. A 3-minute call (or even a quick Slack huddle) allows instant feedback, clarifies ambiguity, and builds rapport. Save email for summaries after the conversation.
Even when email is necessary, we often misuse it as a storage dump.

2. 90% of emails belong in a project management system.

Emails are ephemeral. They get buried, forgotten, or trapped in individual inboxes. If you’re using email to document decisions, share specs, or track progress, you’re creating a future nightmare for yourself and your team. Tools like Notion, Asana, or Trello exist for a reason: they centralize information, make it searchable, and ensure everyone has access to the same source of truth. Bonus? No more “Can you forward me that email from 2019?”
But what about sharing data itself? Email fails there, too.

3. Stop using email as a data landfill.

Sending spreadsheets, reports, or lengthy updates as email attachments is like tossing confetti into a hurricane. Email chains are inherently disorganized—no one can find, reference, or update that data efficiently. Instead, send a notification with a link to a shared drive, dashboard, or collaborative doc. This keeps the email itself short (a headline + URL) and ensures the actual data lives in a structured, accessible, and version-controlled space.
Email isn’t “broken”—we’re just using it wrong. By reserving it for quick, actionable alerts (not debates, archives, or data dumps), we free ourselves to use better tools for the job. The result? Fewer misunderstandings, less wasted time, and a lot less inbox-induced rage.
This week, catch yourself before hitting “send.” Ask:
  • Could this be resolved faster with a call?
    • Should this live in a project management tool?Is the data I’m sharing actually findable?
Your team (and your sanity) will thank you.

Episode: "Your Inbox is Not a Database (And Other Email Truths That Will Set You Free)"

[INTRO: Welcome to Email Hell]
Welcome back to Automate Office Work—the podcast where we take the broken systems that are slowly draining your will to live and show you how to fix them. I'm your host, and today... oh, today we're going deep.
Today we're talking about email.
And I know what you're thinking. "Email? Really? That's what we're spending an hour on?"
Yes. Absolutely yes. Because email is quietly, invisibly destroying productivity in organizations around the world. And most people don't even realize it's happening because email dysfunction has become so normalized that we think it's just... how work is.
Let me paint you a picture. It's Monday morning. You sit down at your desk with your coffee. You open your inbox. 127 new messages since Friday afternoon.
You start scrolling. There's an email with the subject line "Quick question" that contains seven paragraphs and asks you to compile data from five different sources. There's an email chain with 43 replies where you were CC'd on every single one, and you have no idea why you're on it or what you're supposed to do about it. There's an email that says "Per my last email" with a passive-aggressive tone that makes your blood pressure spike. There's an email asking for information that's already documented in three different places, but apparently it was easier for them to ask you than to look it up.
There's an email with an attachment called "Final_v3_REVISED_actualfinal.docx" and you're not sure if you're supposed to review it, approve it, or just acknowledge receipt. There's an email from two weeks ago that you meant to respond to but it got buried and now it's awkward. There's an email with the subject "URGENT" that is absolutely not urgent. There's an email that should have been a five-minute conversation but instead it's turned into a 12-message thread spanning three days with four people weighing in and nobody agreeing on anything.
And it's 9:17 AM and you haven't done any actual work yet. You've just been processing email. And you'll spend another hour on it at lunch. And another hour before you leave. And you'll check it on your phone at dinner. And before bed. And the cycle continues.
Does this sound familiar?
If you're nodding right now, you are not alone. The average office worker receives 121 emails per day. They spend 28% of their workweek managing email—that's 11.2 hours per week, over 500 hours per year. That's almost three full months of your working life every year just dealing with email.
And here's the thing: most of that email shouldn't exist. Most of those messages are symptoms of broken processes, lack of proper tools, unclear communication norms, and fundamental misunderstandings about what email is actually for.
Today we're going to talk about why email is failing you, why it was never designed to do what you're asking it to do, and what you should actually be doing instead. We're going to go deep into the history, the psychology, the specific problems, and most importantly, the solutions.
This is going to be a long one—about an hour. So settle in. Grab your coffee or tea or stress ball. And let's talk about email.
By the end of this episode, you're going to see your inbox differently. You're going to understand why email culture is broken and how to fix it. And you might just reclaim a few hours of your life every week.
Let's do this.
[THE ORIGIN STORY: What Email Was Actually Designed For]
Before we get into everything that's wrong with email—and trust me, we're going to get very deep into what's wrong—I want to start with history. Because understanding what email was originally designed for helps us understand why it's failing at what we're asking it to do today.
Email was invented in 1971 by Ray Tomlinson, an engineer working on ARPANET—the predecessor to the internet. He created a system that allowed people to send messages between different computers on the network. The first email ever sent was probably something like "QWERTYUIOP" or similar test text. Not exactly profound, but revolutionary.
The concept was simple and brilliant: asynchronous messaging. Unlike a phone call, which requires both people to be available at the same time, email lets you send a message whenever you want and the recipient can read and respond whenever they want. It's non-real-time communication. That was the innovation.
In the early days—through the 70s, 80s, and even into the 90s—email was primarily used by academics, researchers, and technical people. The user base was small. The volume was manageable. And there was an implicit understanding of what email was for.
Email was designed for:
1. Asynchronous communication - Sending a message that doesn't require an immediate response
2. Brief updates and notifications - "The meeting has been moved to 3pm" or "The report is ready for review"
3. Sharing information - "Here's the document you asked for" or "Thought you'd find this article interesting"
4. Coordinating across time zones and schedules - Allowing people who couldn't easily talk in real-time to communicate
Email was NOT designed for:
  • Storing data
  • Managing projects
  • Conducting complex negotiations
  • Building consensus among large groups
  • Tracking tasks and assignments
  • Creating institutional knowledge
  • Real-time collaboration
  • Long-form documents or detailed explanations
But here's what happened: Email became ubiquitous. By the late 90s and early 2000s, everyone had email. Businesses adopted it enthusiastically because it was cheaper than phone calls and faster than postal mail. And because it was the only digital communication tool most people had access to, they started using it for everything.
Need to coordinate a project? Email thread.
Need to store customer information? Keep it in email.
Need to make a decision? Email chain with 17 people.
Need to document a process? Email it around.
Need to share knowledge? Forward the email.
Email became the default for all business communication, not because it was the best tool for these purposes, but because it was the only tool people had.
And this is where the problems started.
Because email is fundamentally a messaging protocol. It's a way to send text from Point A to Point B. It has no inherent structure. No built-in workflow. No task management. No knowledge organization. No version control. No access permissions beyond "who has a copy of this message."
It's like using a telephone to store your filing cabinet. Sure, you can leave yourself voicemails with information you need to remember, but that's not what phones are for and it's going to be a disaster when you need to find something.
But that's exactly what we've done with email. We've turned it into a filing cabinet, a project management system, a database, a knowledge base, and a task manager—all at once, in one giant, unsearchable, unorganized pile.
The key insight is this: Email is a transport mechanism, not a storage system. It's a delivery truck, not a warehouse.
When you understand this—really understand this—everything else we're going to talk about today will make sense.
Email should deliver information from one person to another. What happens to that information after delivery—how it's stored, organized, acted upon, referenced later—should happen in purpose-built tools. Not in the inbox.
But we've made email the destination. The final resting place for information. The place where data lives and dies. And that's the fundamental problem we're going to dissect over the next hour.
[THE SLOW CREEP: How Email Culture Became Toxic]
Let me tell you a story about how email dysfunction happens. It's gradual. Invisible. Insidious.
Meet Jennifer. She's a project manager at a mid-sized consulting firm. When she started five years ago, her role was straightforward. Coordinate projects, track deliverables, communicate with clients and team members.
Email was one of her tools. A useful one. She'd send updates: "The proposal is ready for review." She'd get responses: "Looks good, approved to send." Clean. Simple. Functional.
But over time, things changed.
A client asked a question about a previous project. Jennifer dug through her email for twenty minutes to find the answer because it was buried in a thread from eight months ago. She finally found it, sent the response, and moved on.
A team member asked, "What's the status of the Peterson project?" Jennifer wrote a three-paragraph email summarizing the status, the blockers, the next steps. Same question came up two weeks later from someone else. She copied and pasted the same email, updated the dates.
A vendor needed information. Jennifer had it in her email somewhere. She searched for fifteen minutes, found it, forwarded it.
Someone asked for a document. "I know I have it, it was an attachment from... I think March? Let me search." Ten minutes of searching through attachments. Found it, sent it.
Each individual instance seemed fine. Just part of the job. But the pattern was forming: Email was becoming her primary tool for storing information, tracking status, answering questions, and finding documents.
Fast forward five years. Jennifer now manages twelve active projects. Her inbox has 8,472 messages. She gets 150+ emails per day. She spends roughly 15-20 hours per week just managing email.
Her typical day:
  • First hour of the morning: triage inbox, respond to urgent requests
  • Throughout the day: interrupted every 10-15 minutes by incoming email
  • Last hour of the day: catch up on everything she missed while in meetings
  • Evening at home: "Quick check" of email that turns into 45 minutes
She has elaborate folder systems and rules, but they don't really help because most emails touch multiple projects or don't fit neatly into one category.
She loses track of action items because they're buried in threads. She can't quickly answer questions like "What did we decide about the budget allocation for Project X?" because the decision is somewhere in a 23-message thread mixed with other discussions.
When she goes on vacation, she comes back to 600+ emails and spends three days catching up. Some things fell through the cracks while she was gone because they lived only in email threads and nobody else could find them.
She's exhausted. Overwhelmed. And she feels like she's constantly behind even though she's working 50+ hours a week.
This is email dysfunction. And it happened so gradually that Jennifer didn't even notice it was happening. Each individual email seemed reasonable. Each request seemed legitimate. But collectively, the system broke.
And here's the really insidious part: Jennifer's colleagues are having the same experience. Everyone is drowning in email. So when they need information from Jennifer, they email her because they don't know where else to look. And when Jennifer needs information from them, she emails them for the same reason.
The dysfunction is self-reinforcing. Email creates more email. The more information lives in email, the more you have to use email to find information, which generates more email, which creates more places for information to hide, which means more email searching, which means more replies and forwards and threads.
It's a vicious cycle. And most organizations are stuck in it right now.
[THE BIG PROBLEMS: A Deep Dive Into What's Actually Broken]
Alright, now we're going to get into the specifics. I want to go through—in detail—the fundamental problems with how we're using email today.
These aren't minor annoyances. These are structural failures that cost businesses billions of dollars in lost productivity, missed opportunities, and employee burnout.
Ready? Let's go deep.
PROBLEM #1: Email Is Not a Database (But Everyone Treats It Like One)
This is the foundational problem from which most other problems flow.
People use email to collect and store data. Customer information. Project details. Decisions. Specifications. Requirements. Contract terms. Pricing. Schedules. Technical details. Business logic. Institutional knowledge.
All of it goes into email. And email is possibly the worst place to store data that has ever been invented.
Here's why:
No structure. In a database, data has a schema. Fields have types. Relationships are defined. In email, everything is unstructured text. A customer's email address might be in the body, in the signature, in a previous message in the thread, or in a forwarded attachment. There's no "Customer Email" field you can query.
No querying. You cannot ask email: "Show me all projects with budget over $50,000 that are scheduled to complete in Q3." You can search for keywords, but that's it. And search is terrible because the information you need might be phrased a hundred different ways across a hundred different emails.
No deduplication. The same information exists in multiple places. You email me a customer address. I forward it to my colleague. They forward it to someone else. Now four people have four copies of the same information in their inboxes. If the address changes, which copy is current? Nobody knows.
No version control. You email me version 1 of a document. I make edits. I email you version 2. You make different edits to version 1. You email me your version 2, which conflicts with my version 2. Now we have two divergent version 2s and we have to manually reconcile them. This happens constantly.
No relationships. In a real database, a customer has orders, each order has line items, each line item references a product. These relationships are explicit and queryable. In email, those relationships exist only implicitly in the narrative of messages. "Regarding the Peterson order, here's the updated item list..." Good luck programmatically extracting that.
No validation. Anyone can type anything into an email. There's no enforcement of "this field must be a valid email address" or "this field must be a date" or "this field cannot be blank." So you get garbage data mixed with good data and no way to distinguish them.
Let me give you a concrete example of how this breaks down.
I worked with a sales team that used email as their primary system for tracking leads and opportunities. When a lead came in, someone would email the team: "New lead: Acme Corporation, contact is John Smith, interested in our enterprise package."
Then there would be follow-up emails: "I spoke with John at Acme, he wants a proposal by Friday." "Proposal sent to Acme." "Acme wants a demo next week." "Demo scheduled for Tuesday at 2pm." "Demo went well, John says they need to talk to their CFO." "John from Acme says they're going with a competitor."
All of this is scattered across dozens of emails over several weeks or months. And here's what happened in practice:
  • No one could easily answer "How many active leads do we have right now?" because you'd have to manually read through hundreds of emails and track which ones were still active.
  • No one could answer "What's the status of the Acme deal?" without reading the entire email thread.
  • When the salesperson went on vacation, nobody else could pick up their deals because all the context was in email threads in that person's inbox.
  • When it was time to do quarterly forecasting, they had to manually go through email and try to reconstruct the pipeline. It took days.
  • They lost deals because follow-up tasks were buried in email and people forgot to do them.
This team needed a CRM. A customer relationship management system. A database designed specifically for tracking sales leads and opportunities. Tools like Salesforce, HubSpot, Pipedrive—or even a well-configured SharePoint List or Airtable base.
In a proper CRM:
  • Each lead is a record with structured fields: Company, Contact Name, Contact Email, Status, Next Action, Deal Value, Expected Close Date
  • You can query: "Show me all leads in 'Proposal Sent' status with expected close date this month"
  • You can see the complete history of interactions in one place
  • You can assign tasks: "Follow up with John at Acme on Friday"
  • You can generate reports: Pipeline value, conversion rates, average time to close
  • When someone goes on vacation, their colleagues can see exactly where every deal stands
But instead, they used email. Because email was "easy" and "everyone already uses it" and "we don't need to learn a new tool."
And it cost them. In lost deals, in wasted time, in stress and frustration.
This pattern repeats across every business function:
  • Customer support using email threads instead of a ticketing system
  • Project management using email chains instead of Asana, Monday, or Jira
  • Knowledge management using forwarded emails instead of a wiki or knowledge base
  • Document management using email attachments instead of a shared drive or document management system
  • Inventory tracking using email updates instead of an inventory system
  • HR records using email instead of an HRIS
In every case, email is being used as a database. And in every case, it fails because it's not a database and was never meant to be one.
The rule is simple: If you're storing data, get it out of email and into a purpose-built system.
PROBLEM #2: The Asymmetry Problem—It's Easy to Create Work for Others
This is one of the most pernicious problems with email, and it's psychological as much as technical.
Email is asymmetric. It takes five seconds to send an email that creates five hours of work for the recipient.
Let me show you what this looks like:
Example 1: The "Quick Question"
Subject: Quick question
Body: "Hey, can you send me the sales numbers for the Northeast region broken down by product category for Q1, Q2, and Q3? Thanks!"
Time for sender to write this: 30 seconds.
Time for recipient to fulfill this: Pull data from three different systems, format it, cross-reference to make sure the categories are consistent, create a spreadsheet, write an explanatory email, attach the file, send it. Two hours.
The sender thinks they asked a "quick question." The recipient just got two hours of work dumped on them with no context, no explanation of why it's needed, no deadline, and no acknowledgment that this is a substantial request.
Example 2: The Vague Directive
Subject: Client feedback
Body: "The client had some concerns about the proposal. Can you take a look and revise? Let me know when it's ready."
What concerns? Which parts of the proposal? What specifically needs to change? What's the deadline? Who is "the client"—the main contact or someone new?
The sender dashed off a vague email in 20 seconds. The recipient now has to:
  • Email back asking for clarification
  • Wait for a response
  • Read the proposal again
  • Try to guess what the concerns might be
  • Make changes
  • Hope they addressed the right things
  • Send it back for review
What should have been a 15-minute revision becomes a multi-day back-and-forth because the original email lacked necessary information.
Example 3: The Mass Information Request
Subject: Need input for strategic planning
Body: "Hi team, we're doing strategic planning for next year. Can everyone send me their thoughts on priorities, resource needs, and growth opportunities for your area? Thanks!"
Sent to: 20 people
Time for sender: 2 minutes to write and send.
Time created for recipients: 20 people × 1-2 hours each to thoughtfully respond = 20-40 hours of collective work.
And here's the kicker: Because the request is vague and unstructured, everyone responds differently. Some send bullet points, some send essays, some send spreadsheets. Now the sender has to manually synthesize 20 different formats of information. The whole process is inefficient from start to finish.
The root cause: Email makes it trivially easy to delegate work to others without thinking about the burden you're creating.
There's no friction. No form to fill out. No fields that force you to provide context. You just type whatever comes to mind and click Send, and suddenly your lack of planning becomes someone else's emergency.
This creates a tragedy of the commons. Everyone is optimizing for their own convenience (sending quick, vague emails) while creating collective chaos (everyone receiving quick, vague emails that require extensive work to decipher and respond to).
The solutions:
  1. Use forms for structured data collection. If you need the same information from multiple people, create a form (Google Forms, Microsoft Forms, Typeform, whatever). Define the questions. Everyone answers the same questions in the same format. You get structured data you can actually analyze.
  2. Use templates for common requests. If you regularly ask for certain types of information, create an email template that includes all the necessary context: What you need, why you need it, deadline, format, level of detail expected.
  3. Estimate the work you're creating. Before sending an email that asks someone to do something, estimate how long it will take them. If it's more than 15 minutes, acknowledge that in the email: "I know this is a substantial request—I estimate it'll take about 2 hours. If that's a problem given your current workload, let me know and we can discuss."
  4. Provide context. Every request should answer: What do you need? Why do you need it? When do you need it? What format? How will it be used?
  5. Do your own homework first. Before asking someone else to find information, spend 5 minutes searching for it yourself. Maybe it's already documented somewhere.
The asymmetry problem is fundamentally about respect for others' time. Email culture that tolerates thoughtless, vague, poorly-scoped requests is a culture that doesn't value people's time.
PROBLEM #3: Email Is a Terrible Task Management System
How many of you use your inbox as your to-do list? Be honest.
You leave emails unread or flagged to remind yourself to do something. You have emails you've read but keep as "unread" to remember to respond. You have a mental map of "emails that need action" scattered across your inbox.
This is incredibly common. And it's a disaster.
Here's why email fails as a task management system:
1. No prioritization. All emails look the same. The urgent and important sit next to the trivial and irrelevant. You can't easily sort by actual priority—only by sender, date, subject, or whether you've artificially flagged it.
2. No due dates. Email has timestamps for when it was sent, but no concept of when the task needs to be completed. You can't see "tasks due today" or "tasks due this week."
3. No delegation or assignment. If a task needs to be done by someone else, you forward the email and hope they do it. There's no formal assignment, no tracking of who's responsible, no way to see "all tasks assigned to Jennifer."
4. No progress tracking. A task is either "not done" (email still in inbox) or "done" (email archived or deleted). There's no "in progress," no "waiting for input," no "blocked."
5. Tasks get buried. New emails arrive constantly and push older emails down. Something important from yesterday is now on page 3 and you've forgotten about it.
6. Context is scattered. The task is in one email, the background information is in another email, the relevant document is an attachment to a third email. You can't see everything related to the task in one place.
7. No recurring tasks. If you need to do something weekly or monthly, you can't set that up in email. You have to manually remember or create calendar reminders.
I've seen people with inboxes that have 3,000+ messages because they're using their inbox as a task list and they're afraid if they archive or delete anything, they'll forget to do it.
This is not a sustainable system. It's stressful, error-prone, and inefficient.
What you should use instead:
  • Actual task management tools: Todoist, Microsoft To Do, Asana, ClickUp, Monday.com, Notion, whatever works for you
  • Features you need: Due dates, priorities, projects/categories, delegation, progress tracking, recurring tasks, notes and attachments
  • The workflow: When an email creates a task, create the task in your task manager with all necessary context, then archive the email. The email is just a notification. The task is the thing you need to track.
Your inbox should be a temporary holding area for messages that need to be processed. It should not be a permanent storage system for tasks, reference information, or pending decisions.
Inbox Zero is not about having zero emails. It's about having zero unprocessed emails. Every email has been read, triaged, and the necessary action has been captured somewhere appropriate (task manager, calendar, knowledge base, filing system). Then the email itself can be archived.
[PROBLEM #4: Email Chains Are Where Context Goes to Die
Picture this: An email thread with 47 replies, spanning 12 days, involving 8 people.
The original question was simple: "What's the budget for the marketing campaign?"
But then:
  • Someone replied asking which campaign
  • Someone else replied with a budget number
  • Someone questioned whether that number included the agency fees
  • Someone forwarded an old email with different numbers
  • Someone chimed in about a related campaign
  • Someone asked whether this should include social media
  • The conversation split into two topics
  • People started replying to earlier messages in the thread, not the most recent one
  • Someone replied-all with "Thanks!" contributing nothing
  • Half the thread is trying to schedule a meeting to discuss it
  • The other half is actually trying to answer the original question
By message 47, the conversation has completely lost coherence. The original question still hasn't been definitively answered. Critical information is buried in message 23. A decision was made in message 31 but then contradicted in message 38.
New people get added to the thread partway through and have no context. People who were removed miss critical updates. The subject line hasn't been updated so it no longer reflects what's being discussed.
This is email chain dysfunction. And it happens because email threads are a terrible structure for complex discussions.
The problems:
1. Linear structure, non-linear conversations. Email threads are strictly linear—one message after another. But real conversations are branching. Topic A spawns subtopic B, which leads to tangent C, while topic A continues in parallel. Email can't handle this. Everything gets mashed into one chaotic thread.
2. No clear resolution. In a proper discussion system (like a forum, Slack thread, or project management comment system), you can mark a discussion as "resolved" or pin the final decision. In email, the thread just... ends. Did we reach a decision? Who knows. You have to read the whole thread to find out.
3. No summary or synthesis. After 47 messages, someone needs to synthesize: "Okay, here's what we decided." That summary goes into message 48. But new people joining the thread won't see it prominently—they see message 1. And in six months when you need to remember what was decided, you have to read all 48 messages to find the synthesis.
4. Information fragmentation. Important details are buried throughout the thread. The budget is in message 12. The deadline is in message 24. The list of deliverables is in message 35. There's no way to extract just the key facts without reading everything.
5. The "Reply All" problem. Not everyone needs to see every reply. But email doesn't have granular controls, so it's either "Reply" (and possibly leave out someone who needs to see it) or "Reply All" (and spam everyone). Most people default to Reply All to be safe, creating noise.
What should you use instead:
  • For decision-making: A meeting (if it's complex and urgent) or a collaborative document with comments and suggestions (if it's async and thoughtful)
  • For project discussions: Project management tools with threaded comments (Asana, Monday, Basecamp)
  • For team discussions: Slack, Microsoft Teams, or similar—where conversations are organized by channel/topic and threading is clearer
  • For documentation: A wiki, knowledge base, or shared document where the final decision/information is recorded in a findable, referenceable format
The rule: If an email thread goes past 5-7 messages and hasn't reached resolution, the conversation needs to move to a different medium. Either schedule a meeting to hash it out synchronously, or move it to a tool designed for structured discussion.
Email is for brief exchanges, not extended deliberations.
PROBLEM #5: Email Has No Access Control or Permissions
Let's talk about a scenario that should make you uncomfortable.
You email me a sensitive document—let's say a draft of a confidential strategic plan. You mark the email "Confidential" in the subject line. You trust me to handle it appropriately.
I receive the email. Now I have complete, unrestricted control over that information. I can:
  • Forward it to anyone, anywhere, at any time
  • Print it
  • Copy the text into another document
  • Screenshot it
  • Save it to a USB drive
  • Upload it to a personal cloud storage account
  • Accidentally reply-all with it attached, sending it to 50 people who shouldn't see it
And there's nothing you can do to stop me. Once you send that email, you've lost control of the information.
This is the access control problem. Email has essentially zero built-in mechanisms to control who can see what, edit what, or share what.
Compare this to a properly configured document management system:
  • You can grant "view only" access—people can read but not download or edit
  • You can set expiration dates—access automatically revokes after a certain time
  • You can track who viewed it and when
  • You can revoke access remotely if needed
  • You can prevent forwarding, printing, downloading
  • You can require authentication to access
  • You can see a complete audit trail
Email gives you none of this.
The consequences:
Information leaks: Sensitive data gets forwarded to people who shouldn't have it, either maliciously or accidentally.
Compliance violations: Industries with regulatory requirements (healthcare, finance, legal) have specific rules about who can access what information. Email makes it nearly impossible to enforce these rules.
Loss of version control: You send me version 1 of a document as an attachment. I save it. You later update to version 2 and send it to other people, but not me. I still have version 1. I might share version 1 with others, not realizing it's outdated. Now two versions are circulating and nobody knows which is current.
No "need to know" enforcement: In a secure environment, access to information should be based on whether someone needs it to do their job. Email works on "whoever has a copy" basis, which is the opposite of need-to-know.
What you should use instead:
  • For documents: Shared drives (OneDrive, Google Drive) or document management systems where you share a link with permissions, not a copy. You maintain control.
  • For sensitive data: Purpose-built secure portals, encrypted file sharing services, or internal systems with proper access controls.
  • For confidential discussions: Secure messaging platforms, internal collaboration tools with permissions, or in-person/video meetings followed by documentation in controlled systems.
The rule: Never send sensitive information as an email attachment if you care about controlling who sees it. Send a link to a controlled location instead.
PROBLEM #6: CC and BCC Culture is Destroying Productivity
Let's talk about everyone's favorite passive-aggressive email features: CC and BCC.
CC (carbon copy) was originally meant to "keep someone in the loop" on a conversation they don't need to actively participate in. BCC (blind carbon copy) was for sending to multiple recipients without revealing everyone's email addresses.
What they've become in modern email culture:
CC = "I'm covering my ass by making sure management sees this" or "I want to publicly shame you by having your boss see that you screwed up" or "I have no idea who actually needs to see this so I'm just including everyone to be safe"
BCC = "I want to secretly let this person see what I'm saying to that person" or "I'm building a case against someone and collecting evidence"
The result: Email overload and toxic communication culture.
The CC problem:
When you CC someone, you're saying "You should read this but you don't need to respond." But in practice:
  • People don't know if they're CC'd for information or if they're expected to do something
  • They feel obligated to read every CC'd email "just in case"
  • They're afraid to ignore CC'd emails because what if it's actually important?
  • Email volume explodes because everyone CCs everyone "to be safe"
I've seen email threads where 15 people are CC'd and only 2 people are actually involved in the conversation. The other 13 are getting noise, but they have to read every message to determine whether they need to care.
The BCC problem:
BCC is almost always used for sketchy purposes. If you're BCC'ing someone on an email, ask yourself: Why can't this person be a visible participant?
Common answers:
  • "I want my boss to see this exchange but I don't want the other person to know" → You're building a case or covering your ass, which suggests unhealthy work environment
  • "I want to secretly include someone" → This is deceptive
  • "I don't want to reveal everyone's email address" → This is actually the legitimate use (bulk emails, newsletters), but it's rare in business contexts
What you should do instead:
  1. Default to NOT CCing anyone. Only CC someone if they specifically asked to be kept in the loop or if they have a clear, documented reason to be informed.
  2. If someone needs context, don't CC them on the ongoing thread. Instead, send them a separate summary email: "FYI, here's what's happening with Project X..." They get the information without the noise.
  3. Make CC expectations explicit. If you're CCing someone, consider adding a line in the email: "CC'ing Sarah for visibility—no action needed from her."
  4. Use "To" for people who need to act, CC for people who need to know. And make sure the "people who need to know" actually need to know.
  5. Better yet, move information to a shared space. Instead of CCing 8 people on every project update, post updates to a project channel in Slack/Teams or to a project space in your project management tool. People can choose to follow closely or just check in periodically.
  6. Never BCC except for bulk emails. If you're BCC'ing someone in a business conversation, you're being deceptive. Don't.
The cultural problem: CC culture is often a symptom of lack of trust or unclear accountability.
  • People CC their boss on everything because they don't trust they won't be blamed later
  • People CC everyone because they don't trust that the right people will be informed otherwise
  • People CC broadly because they're afraid of being accused of leaving someone out
These are organizational culture problems that email exacerbates but doesn't cause. Fix the culture (clarify accountability, build trust, define clear communication norms) and the CC problem gets better.
PROBLEM #7: Email Is Terrible for Knowledge Management
Pop quiz: Three months ago, someone sent you an email explaining how to configure the reporting system. You need that information again today. How long does it take you to find that email?
If you're like most people: 10-20 minutes of searching, trying different keywords, scrolling through results, clicking into promising emails that turn out to be wrong, finally finding it buried in a thread about something else.
Now imagine that information was in a knowledge base or wiki. You search or browse to "Reporting System → Configuration Guide." Five seconds. Done.
Email is where knowledge goes to die.
The problems:
1. Information is hidden in personal inboxes. If I email you a process document, now the information exists in your inbox and my sent folder. If someone else needs that information, they either have to ask one of us (creating another email) or they'll never find it.
2. No categorization or tagging. You can't tag an email with "Onboarding Process" and "HR Policies" so it shows up when people browse either category. It just sits in chronological order with thousands of other emails.
3. Search depends on remembering keywords. If the email you need mentions "quarterly reporting" but you search for "Q4 reports," you might not find it. The same concept phrased different ways becomes unfindable.
4. Information becomes outdated. That configuration guide from three months ago? The system has been updated twice since then. The email has the old instructions. But you don't know that. You follow the old instructions and things break.
5. Duplication and inconsistency. Five people have each explained the same process to different people in five different emails. Now there are five slightly different versions of "how to do X" floating around. Which one is correct? Nobody knows.
What you should use instead:
  • Company wiki or knowledge base: Confluence, Notion, SharePoint, MediaWiki, whatever. A searchable, organized repository of "how we do things"
  • Features you need: Categories/hierarchy, search, version history, access controls, ability to link between articles
  • The workflow: When someone asks a question via email that's likely to come up again, answer it once and document it in the knowledge base. Then reply to the email with: "Great question! I've documented the answer here: [link]." Next time someone asks, you just send the link.
The rule: If you find yourself explaining the same thing more than twice, it should be documented somewhere permanent and findable, not re-explained via email every time.
PROBLEM #8: AI Is Not Solving the Real Problem
I need to address this because it's the hot topic right now. AI email assistants that write emails for you, summarize emails, categorize them, prioritize them, draft responses.
Here's my controversial take: AI is making the email problem worse, not better.
Let me explain.
The email problem is not "emails are hard to write" or "emails are hard to read." The problem is we're using email for things it was never designed for and creating massive inefficiency and dysfunction in the process.
AI that helps you write emails faster means... you send more emails. AI that summarizes long email threads means... people feel empowered to send even longer, more rambling emails because "the AI will summarize it anyway."
We're using technology to optimize a fundamentally broken process.
It's like this: Imagine your bathtub is overflowing because you left the faucet running. AI email tools are giving you a faster bucket to scoop water out of the tub. That's helpful! You're bailing water more efficiently!
But you're still not turning off the faucet.
The faucet is: Using email for data storage, project management, task tracking, knowledge management, and complex collaboration—all things email is terrible at.
Turning off the faucet means: Moving those functions to purpose-built tools so the volume of email naturally decreases.
Don't get me wrong—AI email tools have their place. If you're going to use email (and you will, for some things), AI can make it less painful. Summarization is genuinely useful. Smart categorization helps. Auto-generated responses for common inquiries save time.
But these are band-aids. They're treating symptoms, not the disease.
The disease is: Email has become the default tool for everything, regardless of whether it's the right tool.
The cure is: Using the right tool for each job so email volume naturally decreases to manageable levels.
When email is used only for what it's actually good at—brief asynchronous messages, notifications, and simple coordination—you don't need AI to manage it. You just... manage it. It takes 20 minutes a day instead of 3 hours.
So by all means, use AI tools if they help you today. But don't let them distract you from the real work: fixing your processes so you're not drowning in email in the first place.
[EMAIL ETIQUETTE: How to Not Be Part of the Problem]
Alright, we've spent over an hour talking about what's broken. Now let's talk about what YOU can do, individually, to be a better email citizen.
These are the rules of email etiquette that, if everyone followed them, would dramatically reduce email dysfunction.
RULE #1: Keep Emails Brief and Focused
If your email is longer than 3-4 short paragraphs, it should not be an email. It should be:
  • A phone call or video meeting
  • A document that you link to
  • A meeting
  • A structured form or questionnaire
Long emails don't get read carefully. They get skimmed. Important details get missed. Responses are delayed because people put off reading "that long email."
How to keep emails brief:
  • One email = one topic. If you need to discuss three things, send three emails or schedule a meeting.
  • State the purpose in the first sentence: "I'm writing to ask for X" or "I'm writing to inform you that Y"
  • Use bullet points for lists, not long paragraphs
  • Put supporting details in an attached document, not in the email body
  • Edit ruthlessly. Every sentence should be necessary.
RULE #2: Make the Action Clear
Every email recipient should immediately know: What am I supposed to do with this information?
Options:
  • FYI (For Your Information): Just keeping you in the loop, no action needed. Say this explicitly: "FYI, no response needed."
  • Action Required: I need you to do something. State it clearly: "ACTION NEEDED: Please review the attached document and send me your feedback by Friday."
  • Decision Needed: I need you to make a decision. State the options: "DECISION NEEDED: Should we use Vendor A or Vendor B? Please let me know by Wednesday."
  • Response Requested: I'm asking you a question. Make the question clear and specific.
If it's not clear what you're asking for, the recipient will either:
  • Email back asking for clarification (more email)
  • Guess and possibly do the wrong thing
  • Ignore it because they don't know what to do
RULE #3: Use Descriptive Subject Lines
Subject lines should tell the recipient what the email is about and what urgency it has.
Bad: "Question"
Good: "Question about Q3 budget allocation"
Bad: "Update"
Good: "Project Falcon update - timeline change"
Bad: "Urgent!!!"
Good: "URGENT: Client meeting moved to 2pm today"
If the email is just informational, consider adding [FYI] to the subject. If it's action required, add [ACTION NEEDED].
Update the subject line if the topic changes during a thread. Don't let a thread about "Meeting time" continue to use that subject when you're now discussing budget.
RULE #4: Respect People's Time with Requests
Before sending an email that asks someone to do work:
  1. Estimate the effort. If it's more than 15 minutes of work, acknowledge it: "I know this is a substantial request—I estimate it'll take 1-2 hours. If that's a problem, let me know."
  2. Provide all necessary context. Don't make them email back asking for basic information you should have included.
  3. Be specific. "Send me sales data" is vague. "Send me monthly sales data for Product X in the Northeast region for Jan-June, broken down by customer segment, in Excel format" is specific.
  4. Give a reasonable deadline. "ASAP" is not a deadline. "By end of day Friday" is.
  5. Explain why. People are more motivated to help when they understand the purpose. "I need this for the board presentation next week" gives context.
RULE #5: Don't Use Email for Urgent Matters
Email is asynchronous. People check it when they check it. If something is genuinely urgent—needs a response in the next hour—don't email. Call, text, use Slack/Teams, or walk to their desk.
Using email for urgent matters and then getting frustrated when you don't get an immediate response is setting yourself up for disappointment.
Reserve "URGENT" in subject lines for truly urgent things. If you mark everything urgent, nothing is urgent.
RULE #6: Respond Appropriately to Reply-All
Before hitting Reply All, ask yourself: Does everyone on this thread need to see my response?
If you're just saying "Thanks!" or "Got it!" → Reply only to the sender, not to all.
If you're answering a question that everyone needs to know → Reply All.
If you're discussing something that only pertains to a subset of recipients → Reply only to that subset, or move the conversation offline.
RULE #7: Don't Email When You're Angry
Angry emails are permanent records of temporary emotions. They escalate conflicts. They get forwarded to people you didn't intend. They damage relationships.
If you're upset, write the email if you must—but save it as a draft. Sleep on it. Re-read it the next day. 90% of the time, you'll either delete it or completely rewrite it.
Better yet: If you're upset about something, have a conversation (phone or in-person) instead of an email.
RULE #8: Use Out of Office Appropriately
When you're out of office:
  • Set an auto-reply that says when you'll be back and who to contact for urgent matters
  • Actually disconnect. Don't check email on vacation and respond sporadically. It trains people to expect responses from you even when you're off.
  • When you return, accept that you can't read every email. Skim, prioritize, archive liberally. Don't try to achieve inbox zero on day one back.
RULE #9: Unsubscribe Aggressively
If you get regular emails you never read (newsletters, automated reports, notifications), unsubscribe or set up filters to auto-archive them. Every email in your inbox creates decision fatigue. Reduce the volume at the source.
RULE #10: Default to NOT Sending
Before sending an email, ask: Does this email need to exist?
  • Could I walk over and have a 2-minute conversation instead?
  • Could I add this to an agenda for a meeting we already have scheduled?
  • Could I post this in a Slack channel instead?
  • Could I document this in a shared location instead of emailing it around?
  • Am I just sending this to feel like I did something, or does it actually add value?
Every email you don't send is time saved for both you and the recipient.
[BETTER ALTERNATIVES: The Right Tool for Each Job]
We've established that email is being overused. Now let's be specific about what you should use instead, for each type of situation.
SCENARIO: Collecting Data or Information
Wrong: Email blast to 20 people: "Everyone send me your budget requests for next year."
Right: Create a form (Google Forms, Microsoft Forms, Typeform). Define the exact fields you need. Send one email with a link to the form. Responses are automatically collected in a structured, analyzable format.
Why it's better: Structured data, consistent format, no need to manually compile from 20 different email formats.
SCENARIO: Project Collaboration and Task Management
Wrong: Email threads to coordinate tasks, share updates, discuss blockers.
Right: Use a project management tool (Asana, Monday.com, ClickUp, Basecamp, Jira, whatever fits your team). Create projects, assign tasks, track status, discuss in comments attached to tasks.
Why it's better: Everything related to a project is in one place. Clear accountability (who's doing what). Visible status (what's done, what's in progress, what's blocked). Searchable history. No information lost in email threads.
SCENARIO: Documenting Processes and Procedures
Wrong: Emailing step-by-step instructions to people who need them, re-sending every time someone asks.
Right: Document once in a wiki or knowledge base (Confluence, Notion, SharePoint, internal wiki). Email a link when people need it.
Why it's better: One authoritative source. Easy to update. Searchable. Can be organized by category. No version confusion.
SCENARIO: Customer Support
Wrong: Customer emails you, you respond. Then they email again. Thread gets long. You're on vacation and someone else can't see the history. Customer emails a different person and now two people are responding to the same issue.
Right: Ticketing system (Zendesk, Freshdesk, Help Scout, even a well-configured SharePoint list). Every customer inquiry becomes a ticket. Complete history is tracked. Status is visible. Can be assigned, escalated, reported on.
Why it's better: No duplicate effort. Complete context always available. Reporting on response times and resolution rates. SLA tracking. Knowledge base integration.
SCENARIO: Team Communication and Discussion
Wrong: Long email threads with 15 people discussing multiple topics.
Right: Slack, Microsoft Teams, or similar. Organized by channels/topics. Threaded discussions. Searchable. Real-time when needed, async when appropriate.
Why it's better: Organized by topic not chronology. Easier to follow multiple conversations. Less formal than email, encouraging quicker updates. Better search. Integration with other tools.
SCENARIO: Sharing and Collaborating on Documents
Wrong: Emailing Word docs or Excel files as attachments. Multiple people edit their copies. Version chaos ensues.
Right: Use cloud storage with real-time collaboration (Google Docs/Sheets, Microsoft 365 with OneDrive, Dropbox Paper). Share a link, not a copy. Everyone edits the same document.
Why it's better: One version. Real-time collaboration. Version history. Comments and suggestions. Permission controls.
SCENARIO: Scheduling Meetings
Wrong: Email chain with 8 people trying to find a time. "I can do Tuesday or Wednesday." "Tuesday doesn't work for me, how about Thursday?" "Thursday I'm in a client meeting..." 12 emails later...
Right: Use a scheduling tool (Calendly, Microsoft Bookings, Doodle). Propose times, people vote or pick from available slots. Meeting scheduled in 2-3 messages instead of 12.
Why it's better: Dramatically fewer emails. Visual interface showing everyone's availability. Automatic calendar integration.
SCENARIO: Collecting Feedback or Making Decisions
Wrong: Email asking for everyone's opinion. Responses come in various formats. Hard to synthesize.
Right:
  • For simple yes/no: Use a poll (Microsoft Forms, Google Forms, Slack poll)
  • For complex feedback: Create a shared document with specific questions/sections. People add comments.
  • For decisions: Schedule a meeting or use a decision-making framework in a shared doc.
Why it's better: Structured input. Everyone can see everyone else's responses (if appropriate). Clear synthesis of results.
SCENARIO: Announcements and Updates
Wrong: Emailing the whole company every time there's an update. Most people skim or ignore. Information gets lost.
Right:
  • Company newsletter (weekly/monthly digest, not daily emails)
  • Company intranet or hub (SharePoint, Workplace, internal site) where announcements are posted
  • All-hands meetings for major announcements
  • Slack/Teams announcement channel that people can subscribe to
Why it's better: Less inbox clutter. Information archived in findable location. People can consume on their schedule.
The pattern: Email should primarily be a notification mechanism pointing to where actual work happens.
Examples of appropriate emails:
  • "A new task has been assigned to you in Asana: [link]"
  • "Jennifer commented on your document: [link]"
  • "The weekly sales report is ready: [link to report]"
  • "Your approval is needed for Purchase Request #1247: [link]"
The email alerts you that something needs attention. The actual work/discussion/decision happens in the appropriate tool. The email doesn't contain all the information—it points you to where the information lives permanently.
This is email used correctly: ephemeral notifications, not permanent storage.
[FIXING EMAIL CULTURE: How to Make Organizational Change]
Individual email etiquette is important, but lasting change requires organizational culture change. Here's how to actually fix email culture at your company.
STEP 1: Acknowledge the Problem
Get leadership to recognize that email dysfunction is costing the company. Put numbers on it:
  • Average employee gets 121 emails/day
  • Spends 28% of work week managing email = 11 hours/week
  • For a 100-person company: 1,100 hours per week spent on email
  • At $50/hour average cost: $55,000 per week, $2.86M per year just managing email
Plus the hidden costs: Missed information, delayed decisions, employee stress and burnout, important messages lost in noise.
When leadership sees this as a multi-million dollar problem, they'll pay attention.
STEP 2: Define Email Norms
Create explicit, written guidelines for email use. Include:
When TO use email:
  • Brief messages that don't require back-and-forth
  • Formal notifications
  • External communication (clients, vendors, partners)
  • Confirming decisions made elsewhere
  • Sending links to information/documents
When NOT to use email:
  • Complex discussions (use meetings or collaboration tools)
  • Project coordination (use project management tools)
  • Task assignments (use task management systems)
  • Storing information (use knowledge bases, wikis, shared drives)
  • Urgent matters (use phone, Slack/Teams, in-person)
  • Long explanations (use documents with links)
Email etiquette standards:
  • Subject lines must be descriptive
  • Emails should be max 3-4 paragraphs (longer content goes in attached documents)
  • Action items must be clearly stated
  • CC only people who truly need to see the message
  • No Reply All unless everyone needs to see your reply
  • Response time expectations: 24-48 hours for non-urgent, immediate channel (phone/chat) for urgent
Publish these guidelines. Make them part of onboarding. Reference them regularly.
STEP 3: Provide Better Tools
You can't just tell people to stop using email without giving them alternatives. Invest in:
  • Project management platform (Asana, Monday.com, etc.)
  • Team communication platform (Slack, Microsoft Teams)
  • Knowledge base/wiki (Confluence, Notion, SharePoint)
  • Form builder (Microsoft Forms, Google Forms)
  • Shared storage (OneDrive, Google Drive)
  • Ticketing system if relevant (for support teams)
Make these tools easily accessible, well-integrated, and actually easier to use than email. If the "better" tools are clunky or siloed, people will stick with email.
STEP 4: Lead by Example
Leadership must model good email behavior. If the CEO sends rambling 10-paragraph emails at midnight and expects immediate responses, the culture will follow.
Leaders should:
  • Use appropriate tools (post project updates in the project tool, not email)
  • Keep emails brief and clear
  • Respect people's time (don't expect instant responses, don't email on weekends)
  • Acknowledge when they should have called instead of emailed
  • Publicly praise people who use the right tools well
STEP 5: Create "Email-Free" Times or Zones
Some companies have successfully implemented:
  • No-email Fridays: Use other communication channels, only email for external communication
  • Email-free mornings: First 2 hours of the day are for focused work, no email checking
  • Meeting-free + email-free blocks: Dedicated deep work time
These experiments help people realize how much more they can get done when they're not constantly interrupted by email.
STEP 6: Train People
Most people have never been taught email etiquette or how to use collaboration tools effectively. Provide training:
  • Email best practices workshop
  • Training on project management tool
  • Training on knowledge base/wiki
  • "Before you email, ask: is this the right tool?" decision tree
Make it practical and specific to your company's norms.
STEP 7: Measure and Improve
Track metrics:
  • Average emails sent/received per person per day
  • Average time spent in email per day
  • Email response times
  • Employee satisfaction with communication tools
Set goals: "Reduce average daily emails from 121 to 80 by end of quarter."
Celebrate wins: "We reduced company-wide email volume by 30%! That's 330 hours per week reclaimed for actual work!"
STEP 8: Address Root Causes
Often, email overload is a symptom of deeper problems:
  • Lack of clarity around roles/responsibilities → People CC everyone because they don't know who's responsible for what
  • Lack of trust → People email excessively to cover their ass
  • Poor meeting culture → Meetings are unproductive so people send follow-up emails repeating everything
  • Inadequate documentation → People ask the same questions repeatedly via email because information isn't documented
  • Siloed teams → Information doesn't flow so people email to bridge gaps
Fix these root causes and email volume will naturally decrease.
[THE VISION: What Email Should Look Like]
Let me paint you a picture of what healthy email culture looks like.
You arrive at work and open your inbox. You have 8 new emails.
Email 1: "New task assigned to you in Asana: Review Peterson proposal."
You click the link, go to Asana, review the task. All the context is there—the proposal, the deadline, the background. You complete the task in Asana. You archive the notification email. Time: 10 seconds in email, 15 minutes in Asana.
Email 2: "Jennifer commented on your document 'Q3 Strategy.'"
You click the link, read her comment in Google Docs, respond to her comment there. Archive the notification email. Time: 5 seconds in email, 3 minutes in Docs.
Email 3: A client asking to schedule a call.
You respond: "Happy to chat! Here's my Calendly link: [link]. Pick a time that works for you." Done. Time: 1 minute.
Email 4: Your manager: "Great job on the Peterson proposal. Client loved it."
You smile, reply "Thanks!", archive. Time: 30 seconds.
Email 5: A colleague asking a question that's already documented in your knowledge base.
You respond: "Great question! We actually have documentation on that here: [link to wiki article]." Archive. Time: 1 minute.
Email 6: Newsletter from an industry publication you subscribe to.
You skim the headlines, click one interesting article, read it, archive the email. Time: 5 minutes.
Email 7: Notification that a report you requested is ready.
You click the link, download the report from the reporting system, save it to the right folder. Archive the notification. Time: 1 minute.
Email 8: Spam. Delete. Time: 2 seconds.
Total time in email: Under 15 minutes.
The actual work happened in other tools—Asana for the task, Google Docs for the collaboration, Calendly for scheduling, the reporting system for data. Email was just the notification layer. The ephemeral pointer.
You spend the rest of your day actually working, not managing email.
You check email twice more during the day—once at lunch, once before leaving. Total time in email for the entire day: 45 minutes. Down from 3 hours.
That's the vision. Email as a utility, not a burden. A useful tool for what it's good at, not a dumping ground for everything.
[ACTION ITEMS: What You Can Do Starting Monday]
We're coming up on an hour. Let me give you concrete, actionable things you can start doing immediately.
INDIVIDUAL ACTIONS (You can do these yourself):
  1. Audit your email habits this week. Track: How many emails do you send/receive per day? How much time do you spend in email? What types of emails are most common? This gives you a baseline.
  2. Unsubscribe from newsletters you never read. Be ruthless. If you haven't opened the last 5, you're not going to. Unsubscribe. Reduce inbound volume.
  3. Set up email batching. Check email only at scheduled times (e.g., 9am, 1pm, 4pm) instead of constantly. Turn off notifications. Batch process instead of reacting to every message immediately.
  4. Create templates for common emails. If you send similar emails frequently (meeting requests, status updates, common answers), create templates. Saves time and ensures consistency.
  5. Start using "FYI - no response needed" in subject lines when appropriate. Train people that you respect their time.
  6. Move one regular email communication to a better tool. Pick one thing you currently do via email (weekly status updates? project coordination?) and move it to a more appropriate tool this week.
  7. Practice the "48-hour rule." Unless something is genuinely urgent, don't expect email responses in less than 48 hours. This alone will reduce stress.
TEAM ACTIONS (Requires coordination with colleagues):
  1. Have a team discussion about email pain points. Get everyone's input: What's broken? What's frustrating? What do we wish worked differently?
  2. Agree on one email norm as a team. Start small. Maybe it's "No emails after 6pm or on weekends" or "Subject lines must indicate if action is required" or "CC only when necessary." Pick one, commit to it for a month, see if it helps.
  3. Choose one process to move out of email. As a team, pick one thing currently done via email (project updates, task assignments, knowledge sharing) and move it to a better tool. Do it as a team experiment.
  4. Create a team knowledge base for common questions. Start a shared document or wiki page. When someone asks a question via email, document the answer there, then link to it. Build it up over time.
    5. ORGANIZATIONAL ACTIONS (Requires leadership support):
    1. Present the business case to leadership. Calculate the cost of email dysfunction in your organization. Propose investing in better tools and email culture training.
    2. Pilot better tools with one team. Don't try to change the whole company at once. Pick one team, give them project management + collaboration tools, train them well, measure results. Use them as a proof of concept.
    3. Establish company-wide email guidelines. Work with leadership to create and publish official email norms.
    4. Provide training. Host workshops on email etiquette, using collaboration tools, when to use which communication channel.
      5. Start with one or two items. Don't try to fix everything at once. Small wins compound.
      [CLOSING: The Path Forward]
      Alright, we're at an hour. Let me bring this home.
      Email is not the enemy. Email is a tool. A good tool, when used for what it was designed for: brief, asynchronous messages between people.
      The problem is we've overloaded it. We've asked it to be a database, a filing cabinet, a project manager, a task tracker, a knowledge base, a collaboration platform—all things it was never designed to be.
      And the result is: Overwhelm. Inefficiency. Lost information. Missed tasks. Burnout.
      But here's the good news: This is fixable.
      The tools exist to do all these things properly. Project management tools. Knowledge bases. Collaboration platforms. Shared storage. Forms. Real databases.
      The challenge is not technological. The challenge is cultural and habitual. We're used to email. It's familiar. It's the path of least resistance.
      But "easy to start" doesn't mean "effective at scale." Just like we talked about with Excel in the last episode—the frictionless beginning becomes a chaotic mess over time.
      The path forward:
      1. Recognize that email dysfunction is costing you—in time, in quality, in stress.
      2. Understand what email is actually for—and what it's not for.
      3. Use the right tool for each job—project management tools for projects, knowledge bases for knowledge, forms for data collection.
      4. Make email a notification layer—pointing to where the real work happens, not being where the work happens.
      5. Establish clear communication norms—as an individual, as a team, as an organization.
      6. Lead by example—model the behavior you want to see.
      7. Start small and iterate—you don't have to fix everything at once.
      Your homework:
      Before this week ends, do two things:
      1. Audit your inbox. Look at the last 50 emails you received. For each one, ask: "Was email the right medium for this?" Categorize them: How many should have been project management tool updates? How many should have been knowledge base articles? How many should have been quick Slack messages? How many were actually appropriate uses of email?
      This will show you where the dysfunction is.
      1. Pick one improvement. Just one. Maybe it's: "I'm going to stop using my inbox as a task list and move tasks to Todoist." Maybe it's: "I'm going to start documenting common answers in a wiki instead of re-typing them in emails." Maybe it's: "I'm going to move my team's project updates to Asana instead of weekly email summaries."
        2. One change. Start there.
        You don't have to fix email completely. You just have to start moving in the right direction. Small improvements compound over time.
        Imagine reclaiming even two hours a week from email. That's 100 hours a year. Two and a half full work weeks. What could you do with that time? Actual strategic thinking? Deep work on important projects? Time with your family instead of checking email at dinner?
        It's possible. It's achievable. You can get there.
        Email is a tool. Use it like a tool—for specific purposes it's good at. Use other tools for everything else.
        Your inbox is not a database. Your inbox is not a filing cabinet. Your inbox is not a task manager. Your inbox is not a knowledge base.
        Your inbox is a temporary holding area for messages. Treat it that way, and watch your productivity soar.
        Thanks for spending this hour with me on this deep dive. I know it's a long listen, but this topic affects literally everyone who works with computers, and it deserved the thorough treatment.
        If this resonated with you, share it with your team. Send it to your manager. Post it in your company Slack. Let's start a conversation about fixing email culture.
        Next episode, we're going to talk about meeting culture—another productivity killer—and how to run meetings that actually accomplish something without wasting everyone's time.
        Until then: Question your inbox. Be intentional about communication. Use the right tool for the job. And keep automating that office work.
        I'm your host, Justin, and this has been Automate Office Work.
        Now go batch-process that inbox, archive liberally, and maybe—just maybe—turn off email notifications for a few hours and see what deep work you can actually get done. Happy automating.
        Comments
        You must sign in to comment
        We use cookies to help run our website and provide you with the best experience. See our cookie policy for further details.