Why Communication Work Doesn't End After Sending Emails

We’ve built a communication culture where everyone is “sending” — but almost no one is actually connecting. I hear this in nearly every in-person workshop I run: “Our team is drowning in messages. Everyone’s emailing. CC’ing. Slacking. But no one is picking up the damn phone.” And that’s the real problem. Somewhere along the way, people started treating sending a message as completing the responsibility. “I emailed them — it’s on them now.” “I dropped it in Slack — they’ll see it.” “I sent a text — they should know.” No. 🤦🏻 That’s not communication. That’s offloading accountability. And this is exactly how: • Resentment builds • Teams slow down • Projects stall • Urgency disappears • Ownership gets blurred If the outcome depends on a response, your job isn’t done when you hit “send.” Here are the biggest breakdowns I see inside organizations right now: – Treating async tools like they replace real conversations – Assigning work without confirming true ownership – Emailing questions and assuming it’s “their job” to respond – Texting and expecting instant prioritization – Posting into Slack and waiting… and waiting… – Using messages for urgent issues instead of calling If your team feels buried in digital noise, it’s not because they’re bad communicators. It’s because they’ve confused sending with resolving. Sometimes the fastest path to clarity isn’t another message… it’s 90 seconds of real conversation. 📞 Pick up the phone. Confirm alignment. Create ownership. Move forward. So here’s the question: Where in your team are messages being sent… but responsibility is being avoided?

An email blast, especially one with half the company CC’d, is not a process. It’s an announcement. One person sends an email to a group with a list of things that need to happen. Everyone is CC’d “for visibility.” And suddenly: No one is sure who actually owns what No one knows what comes first Everyone assumes someone else is handling it And now everyone is watching That’s not alignment. That’s anxiety with a paper trail. Here’s what usually happens next: The email gets interpreted differently by each person Tasks start in parallel or not at all Clarifying emails begin to pile up More people get CC’d “just in case” Inboxes fill up while actual work slows down The email communicated intent. It did not create clarity. This is the Invisible Work Problem. When work isn’t visible, leaders default to broadcast communication and hope people figure it out. But sequence, ownership, and dependencies don’t live in an inbox, they live in how the work flows. So people protect themselves: “I replied.” “I was copied.” “It wasn’t clear.” Email becomes a record of confusion, not progress. It doesn’t scale work. It hides it.

FIRE-AND-FORGET EMAILS: You don’t win wars—or business deals—by firing off emails and hoping for the best. Yet that’s exactly what happens every day in government and industry with “fire-and-forget” emails. Someone drafts a long message, hits send, and walks away believing the job is complete. No call. No follow up. They think they’ve communicated. But they haven’t. All they’ve done is launch words into the void, with no assurance anyone received, understood, or acted on them. That’s not communication—that’s misalignment disguised as effort. And misalignment kills speed. Real communication requires closure. If it’s urgent or time-sensitive, it begins in real time: a phone call, a secure chat, a meeting. Only after alignment is achieved does email serve its proper role—documenting details, expanding awareness, and reinforcing next steps. Email is the record, not the synchronization. Inside the Pentagon, this failure is constant. Internal staff taskings vanish into crowded inboxes. Interagency coordination stalls for days while deadlines slip. Contractors don’t move production lines on “sent” alone. Teams waste hours chasing clarity. And when time finally runs out, everyone scrambles to recover. I’ve seen this dysfunction in very different contexts. In fighter squadrons, urgent pre-mission changes pushed only by email created confusion in the best case and near-failure in the worst. On the factory floor, our corporate offices sent unannounced customer-visit emails without follow-up. As a manufacturing manager, I’m not at a desk. I’m on the floor—probably overhauling equipment or rearranging production lines. So Instead of showcasing capability, we showcased churn. Both environments suffered from the same root cause: people mistaking a message for a decision, and “send” for synchronization. The cure isn’t complicated, but it takes discipline. Communicate in real time first. Call. Visit. Use the giant voice. Use email as confirmation, not initiation. And when it’s time to email, follow basic etiquette: Bottom Line Up Front, put action-owners in the “To” line, awareness-only in “CC.” Don’t inflate urgency by resending messages. Use “Reply All” sparingly—only when your response matters to everyone. And respect boundaries: after-hours emails can wait unless there’s a phone call making it truly urgent. In my organization, an after hours email is understood to be actioned the next business day. If I need urgent after-hours attention (should be rare), then I’ll call. Because communication isn’t complete when you hit send. It’s complete when the other side says: Got it. Understood. Acting now. In warfighting, in business, and in government—the organizations that win are the ones that synchronize, not the ones that just send.

One email almost cost us $450,000. A rep sent trial instructions via email to a top prospect.  The buyer ran the trial, failed us, and we were out. Plot twist: they tested our competitor's software by mistake.  One phone call would have caught it. The lesson: Sending is not selling. Pick up the phone or get on a Zoom when you: ▶️ Present a proposal or pricing ▶️ Deliver a business case or ROI analysis ▶️ Set up a POC/POV and review results ▶️ Send a contract or SOW ▶️ Provide references ▶️ Follow up after a key stakeholder meeting Why? Because buyers are overwhelmed. They spend 6 seconds on your email and miss critical details. You need to: ✅ Understand their reactions, questions, and concerns ✅ Correct misunderstandings in real time ✅ Discuss what happens next - who reviews it, what's the timeline, what could kill it A document sent by email is a guess. A document presented live is a conversation. Emails create risk. Conversations close deals. Before your next send, ask yourself: would a 15-min call make this land better?

In corporate comms, we often think of the job as finished when the message goes out. Email sent. Intranet updated. All-staff meeting complete. But as George Bernard Shaw famously said: “The single biggest problem in communication is the illusion that it has taken place.” Just because you've transmitted the message doesn’t mean it’s been received, understood, or acted upon. Communication isn’t a checkbox. It’s a process: It starts with clarity Requires context and relevance Needs repetition in different formats And it ends only when you’ve heard something back: questions, action, feedback, or even resistance. Great communicators don’t just send. They listen, reinforce, and follow through. So the next time you’re tempted to pat yourself on the back after a blast goes out, ask yourself: Do employees know what this means for them? Can they explain it to someone else? Have I created space for two-way dialogue? What happens next? Because until you have answers to those questions, your job isn’t done. Let’s stop confusing activity with impact. Let’s move from communication outputs to communication outcomes.

I stopped reading your email halfway through. Not because it wasn't important. Because my nervous system told me you were about to fire me. 🫠 A team member once told their manager: "Please stop sending me emails. Every time I see one from you, I panic." The manager was baffled. "What am I supposed to do? NOT communicate with my team?" That's why is so important to remember to work with the need without limiting the path forward by thinking there's only one strategy to meet the need. Your job isn't to be someone's therapist. But if every message you send triggers a fight-or-flight response, you've got a collaboration problem, not just a feelings problem. A dysregulated person can't innovate. They can't think strategically. They're just trying to survive their inbox. 📧⚡ So what DO you do? Not: Stop communicating (obviously) Not: Fix their trauma (not your lane) Instead: Get curious 🤔 ✨ "What would help you trust that my messages aren't threats?" ✨ "Could we do a daily check-in where I share everything at once?" ✨ "What if we used a shared doc you check twice a day?" The person still needs to expand their window of tolerance. That's their work. Their sovereignty. But YOU can design communication rhythms that don't keep them in a constant state of dread while they're doing that work. Because a regulated employee benefits everyone. Better thinking. Better collaboration. Better outcomes for the whole team. 💡 Question for you: Have you ever noticed your own body's reaction to certain types of messages or meeting invites? What patterns have you noticed? 👇🏾 If you're leading a team through uncertainty and want to learn how to create the conditions for people to do their best thinking (even when stress is high), let's talk. DM me to explore how we can build more resilient communication practices in your organization.