We have completely normalized a specific complaint in our workplaces: “This could have been an email.”

And most of the time, this complaint is justified. Meetings that exist solely to report information, share status updates, or recap decisions already made are a massive drain on productivity. They waste time and absolutely should be relegated to a concise email.

But a more subtle problem exists on the exact opposite end of the spectrum. It rarely gets the attention it deserves: the things we put in writing before they are actually ready to be in writing.

Some conversations suffer severe damage the moment you turn them into text first. This happens because the simple act of writing something down, before any real dialogue takes place, immediately closes off the exact thing you need most. You lose the opportunity for a genuine exchange of ideas.

As leadership expert Susan Scott writes in Fierce Conversations: “Never be afraid of the conversations you are having. Be afraid of the conversations you are not having.”

Let’s look at what relying on text does to human connection, which scenarios desperately require real-time air, and how to spot when you are using your inbox as a shield.

What Email Actually Does to a Conversation

When you sit down to write an email about a complex issue, you are inherently committing to a firm position. You deliberately choose specific words. You structure a logical argument, and you essentially arrive at a tidy conclusion and wrap it up for delivery.

When the recipient opens your message, they read it and respond to your neatly packaged conclusion. They do not get to interact with the messy, uncertain, and exploratory version of your thinking. If spoken out loud, that early-stage thinking might have led both of you somewhere far more useful and innovative.

Furthermore, email creates a permanent record. And often, the mere existence of a permanent record changes human behavior. People naturally hedge their bets. They become overly careful with their phrasing. They start anticipating how a specific sentence might look if someone forwarded the thread to a supervisor or another department.

This reaction is not a character flaw in your colleagues. It represents a completely rational response to leaving a paper trail. But this dynamic guarantees that the reply you get back is often the highly polished, defensible version of someone’s thinking, rather than their honest, unfiltered perspective.

Author Patrick Lencioni made a sharp observation about this exact dynamic in leadership. Leaders, he noted, frequently confuse the simple transfer of information to an audience with that audience’s ability to understand, internalize, and actually embrace what is being communicated.

Email excels brilliantly at the first part. It transfers data instantly. But it struggles badly with understanding, internalization, and embrace.

4 Situations That Deserve Real-Time Air

There are a handful of workplace situations where this medium mismatch matters most. You generally know them when you are in them. It is that distinct moment you start drafting a message, realize you have written three entirely different versions, and none of them feel quite right.

Listen to that signal. Here are four specific agenda items that should never be an email.

1. When Alignment Is The Actual Goal

If you are actively trying to get people on the same page, email serves as a terrible tool. People read the exact same words on a screen and hear completely different things in their heads.

In an email thread, you lack real-time calibration. You send a message, the recipient interprets it through their own lens, they respond with their interpretation, and you have to re-explain yourself. This painful loop can easily take days to resolve. A focused, thirty-minute conversation would get you to alignment faster and leave both parties feeling genuinely heard and respected.

2. Feedback That Involves Nuance

Delivering written feedback without the benefit of vocal tone and live reaction is walking into a minefield. The reader always supplies their own tone to your words, and it is rarely the tone you actually intended.

Developmental feedback, performance conversations, and subtle course corrections deserve a real exchange. You need to see how your words are received. You need the ability to clarify what did not make sense and adjust your delivery in the moment. Email strips away this flexibility and turns constructive feedback into a cold verdict.

3. Disagreements In Their Early Stages

If you sense a conflict forming, perhaps a slight misalignment on project priorities or a difference of opinion about strategic direction, resist the urge to make your case in writing.

Your goal is to understand what is actually going on beneath the surface, not to win an argument. Email functions as a tool for making arguments and defending territories. Conversation functions as a tool for understanding people and finding common ground. Use the right tool for the specific moment you are in.

4. Anything Requiring Real Trust To Be Understood

Some messages need genuine warmth behind them to work effectively. Think about a re-engagement conversation with a suddenly disengaged team member. Consider a situation where you need to make a particularly hard ask. Think about acknowledging a major mistake or something that went wrong on a project.

Words on a screen can deliver the factual information about these events, but they struggle immensely to deliver care, empathy, or solidarity. If the relationship context matters to the outcome, you must show up and be present for the conversation.

As Susan Scott brilliantly reminds us: “The conversation is not about the relationship. The conversation is the relationship.”

The Hidden Impulse Behind The Draft

It is worth naming the psychological driver behind our email habits: we often reach for the keyboard because typing feels like control.

Writing allows you to craft the perfect message. You can think deeply before you speak. You can avoid the sheer awkwardness of a live, unpredictable reaction. And sometimes, that caution is perfectly legitimate. There are certainly times when written clarity genuinely serves the recipient better than a rambling meeting.

But very often, the impulse to write is simply avoidance. Email creates a safe distance between you and the recipient. It puts something officially “on the record” without requiring you to sit with the other person in the immediate discomfort of working through a problem together.

Let’s be honest: it is vastly easier to say a hard, confrontational thing when you can just hit send and immediately close your laptop.

If you notice yourself writing and rewriting, endlessly drafting and deleting paragraphs, you need to pause. Stop and ask yourself whether what you are actually doing is delaying a difficult conversation you desperately need to have.

This principle is equally worth keeping in mind when it comes to the meetings you do schedule. The mere fact that you have put time on the calendar does not automatically mean the meeting is serving the right function. If you gather people to “align” on a project, but the underlying issue is a massive disagreement no one is willing to name out loud, that meeting is essentially just an email too, just a longer, more painful one.

A Practical Test Before You Hit Send

You can fix this habit by implementing a simple, powerful pause in your daily workflow. Right before you hit the send button on a lengthy or complex message, ask yourself one crucial question:

Am I writing this because the information genuinely communicates better in text, or am I writing this because I am avoiding a real conversation?

If your honest answer is the latter, if you are secretly hoping the email will do the heavy lifting that a real human exchange needs to do, it won’t work. The message will fall flat, cause confusion, or create unnecessary friction.

Delete the draft. Schedule the meeting. Do the awkward, uncomfortable thing and actually talk to your colleague.

Your inbox will still be waiting for you when the conversation is over. Whatever agreements, action items, or conclusions need to be formally documented can go into an email afterward, once you have actually done the hard work of communicating face-to-face.

What about you? When was the last time you regretted sending a message rather than saying something in a meeting?