How do I get people to actually read project update emails?
Almost nobody reads status emails, forcing managers to treat them as an audit trail rather than communication. This leaves teams constantly confused, generates duplicate support tickets, and turns updates into an exercise where you just send messages knowing they will be ignored.
What people tried
Every workaround mentioned in the threads below. We haven’t tested any of them — and nobody here is claiming they worked.
- 1Holding meetings just to ensure information is consumed
- 2Sending emails primarily for audit trails and documentation (CYA)
- 3Using multiple channels like Slack, wikis, and newsletters simultaneously
- 4Putting non-responsive colleagues on blast during meetings
In their words
Unedited, most upvoted first, each linked to the thread it came from.
“barely 10% (!!) of the participants actually read my Go-Live email. Some even deleted without reading it.”source ↗
“Does anyone else just presume no one is going to read their emails but still send them anyway?”source ↗
“I update an outline, and give weekly stand ups about progress. And yet, people are still confused about the current status.”source ↗
“yep. i send emails knowing they’re mostly for audit, not action.”source ↗
“Yeah, people still don't read the emails, but I have a huge CYA when Bob in accounting doesn't get the work done.”source ↗
“people never read our emails and then send in tickets about "Why is this happening"”source ↗
Where this came up
People with this problem also raised
- 4How to get executives to actually read project reports
- 4How to motivate kids to read books
- 4How do you get stakeholders to actually follow a project plan?
- 4What's a good tween girl magazine option these days?
- 2Why does team documentation always go out of date?
- 3Learning about current events from my students