How to Deal With Coworkers Who Don't Read Your Emails Properly

How to Deal With Coworkers Who Don't Read Your Emails Properly

Why do coworkers skim or ignore your emails entirely? Here's what's actually happening, and how to write emails people read in full.

You send a clear, three-paragraph email laying out exactly what you need, and the reply comes back answering only the first sentence, or asking a question you already answered in paragraph two. It's easy to read this as carelessness or disrespect. It's rarely either. It's a predictable response to how much email the average person is actually dealing with, and understanding that changes how you fix it.

The Real Reason Coworkers Skim Instead of Read

The average professional now receives well over a hundred emails a day and spends roughly 28% of the workweek just managing the inbox, according to research from McKinsey Global Institute. Under that volume, research on workplace email behavior consistently finds that fast skimming is a rational response to overload, not a character flaw, one analysis found a large share of emails get read in under 15 seconds, with many professionals starting to skim their inbox before the official workday even begins just to keep up.

That reframes the problem usefully. A coworker who missed your second paragraph isn't ignoring you. They're triaging, the same way you triage your own inbox every single day.

Why This Matters More Than It Seems

Emails that don't get fully read generate follow-up emails asking for information that was already there, which adds to the very overload causing the problem in the first place. It's a loop: more volume causes more skimming, which causes more clarifying follow-ups, which adds more volume. Breaking it requires changing how the email is written, not just hoping the reader tries harder.

How to Write Emails People Actually Read in Full

Put the ask in the first line, not the last. If someone only reads one sentence, that sentence should tell them exactly what you need and by when. Burying the actual request in paragraph three guarantees it gets missed under skimming conditions.

Keep it short enough to survive a skim. Research on email response rates found that messages between 75 and 100 words consistently saw the highest response rate, around 51%, meaningfully higher than longer messages. If your email runs past a screen's worth of text, most of it isn't getting read closely regardless of how important it is.

Use structure, not prose, for anything with multiple parts. A short paragraph followed by a bulleted list of specific asks is dramatically easier to skim accurately than the same information buried in flowing sentences. Skimming behavior looks for visual landmarks, bold text, numbers, short lines, to extract meaning fast.

Separate the context from the action. If background matters, put it after the ask, not before it, so a time-pressed reader who only needs the action item isn't forced to read through justification first to find it.

Use the subject line to do real work. A subject line that states the actual ask, "Need budget approval by Friday" rather than "Quick question", lets the recipient triage accurately before even opening the message.

What to Do When a Coworker Keeps Missing Things Anyway

Ask a clarifying, not accusatory, question. "Did my email on Tuesday get buried, want me to resend the key part?" gives the person an easy out and surfaces whether it's a volume problem on their end rather than a reading habit.

Move time-sensitive or complex asks to a different channel. Email is a weak format for anything genuinely urgent or multi-part. A short message in chat, or a two-minute conversation, often resolves in less time than the email back-and-forth would have taken.

Don't assume one unanswered email means the relationship is fine to escalate immediately. Given how much email the average person is managing, one missed message is far more often a volume issue than a signal about how the person values the working relationship.

Model the behavior you want. Coworkers who consistently receive short, clearly structured emails from you tend to read your messages more carefully over time, since you've built a track record of not wasting their attention.

Common Mistakes That Make the Problem Worse

The most frequent mistake is responding to being skimmed by writing longer, more detailed emails to "make sure they get it," which backfires, since length is precisely what triggers skimming in the first place. The second is taking a missed detail personally and letting that show in a terse follow-up, which damages the working relationship more than the original miss did. The third is defaulting to email for anything genuinely time-sensitive, when a different channel would resolve it faster with less friction for both people.

When the Problem Is Bigger Than One Coworker

If this is happening across an entire team, not just with one person, it's often less about individual habits and more about genuine communication overload inside the organization, too many channels, no shared norms on what needs email versus a quick message. That's a structural fix, not an individual one.

Building Better Communication Habits Across a Team

ICE's Inform pillar helps organizations build communication norms and channel strategy that reduce exactly this kind of overload at scale. For more, see why employees don't read company emails and what to include in an employee newsletter on the ICE blog.

Follow ICE on LinkedIn, Instagram, Facebook, and YouTube for more HR and communication resources.

Frequently asked questions

Most professionals are managing a large daily email volume and skim rather than read closely by necessity, not choice. Emails with the key ask in the first line and a clear structure are far more likely to be read in full.
No, generally the opposite. Research shows shorter, well-structured emails get read more thoroughly and get higher response rates than longer prose-style messages.
For anything genuinely urgent or requiring back-and-forth clarification, a different channel, chat or a quick call, often resolves faster with less risk of being missed entirely.
Frame it as checking whether the message got buried rather than accusing them of not reading carefully, this keeps the conversation collaborative rather than confrontational.
Engagement 03 Oct 2026 · By ICE

Build a workplace people believe in.

Every great workplace starts with one conversation — let's have it.