There's a particular moment happening in a lot of organizations right now that doesn't get much attention. Someone opens their email client and instead of the usual wall of messages, there's a summary. AI-generated. Three bullet points. It's already processed everything for them.
On paper, this is obviously good. Email is broken. Everyone knows it. The average knowledge worker gets somewhere in the neighborhood of a hundred messages a day, most of them noise, many of them things they don't need to read. A summarization layer sounds like the obvious answer. Let the AI read it, extract what matters, show the human the distilled version. Efficiency problem solved.
But something worth examining happens when you actually watch people using this feature. They start trusting the summary more than they trust their own judgment about what they missed. Not consciously, not with intention, but inevitably. The AI says "no critical updates" so they don't skim the messages themselves. The AI identifies a message as "informational only" so they don't open it. Three weeks later someone mentions something that was in that message, and there's a moment of confusion about why they didn't know.
This isn't about the AI being wrong exactly, though sometimes it is. It's about what gets lost when a human stops reading something themselves. Context lives in the details. Tone lives in the details. The thing someone decided to lead with, the way they phrased something, the fact that they sent it to you specifically even though it technically went to a broader list, these things don't compress well into summaries. They matter anyway.
There's also something subtly important about the experience of skimming your own email. It's not efficient. It's actually pretty inefficient. But in that inefficiency, you're making micro-decisions about what you need to think about today. You're calibrating your own priorities against what's landing in your inbox. You're noticing patterns, reading between lines, picking up on things that aren't explicitly stated. It's work, real work, and it's mostly invisible. But it's the kind of work that prevents you from being blindsided later.
The people who seem most comfortable with AI email summaries are the ones who already have good information systems around their work. They know where the critical things come from. They're already talking to the right people directly. For them, the summary is genuinely just clearing noise. But for everyone else, especially people new to a role or managing something complex, losing that reading layer might be creating more problems than it solves.
There's also a second, weirder effect happening. Some teams are starting to see the summarization layer as a signal about what they should be sending. If the AI keeps marking things as "low priority," maybe that thing doesn't need to be in email at all. Which is sometimes true. But sometimes important context gets classified as low priority because AI doesn't have the full picture of why someone needed to know it. So people optimize their communication around what the summarization layer rewards, which might not be what the work actually needs.
None of this is an argument against having better email systems. The current situation is clearly broken. But there's a difference between fixing email and replacing human judgment with automated judgment. The interesting tension is that the people who most need help managing email are often the least able to afford to stop reading it themselves. They're the ones whose work depends on catching the thing that wasn't explicitly marked as important.