The PM Skill Nobody Talks About: Knowing Which Emails to Ignore
"You are better off doing nothing than be a PM."
TL;DR: Not every harsh email deserves your energy. PMs sit at the center of delays, dependencies, and disappointment. Most angry emails are looking for a pressure outlet, not a discussion. Spend less time replying than they spent writing. Fix the problem, not the email.
The Email That Stuck
My friend was talking about an email from years ago that ended with that line. Harsh, blaming, and completely unfair. What surprised me was not the email itself. It was that he remembered it word for word, years later.
That is the thing about harsh emails. They stick. Not because they are accurate, but because they hit you when you are already stretched thin, already juggling five things, already wondering if you are doing enough.
Early in my PM career, I did the same thing. Every critical email, I read slowly. Line by line. Again and again. I would lose sleep replaying it in my head. I drafted the perfect reply to prove I was not wrong. I wanted to make sure every point was addressed, every accusation countered, every timeline defended.
Classic rookie PM mistake.
Why PMs Get More Harsh Emails Than Anyone Else
PMs sit at the center of delays, dependencies, and disappointment. You are the person everyone comes to when something goes wrong, even when the thing that went wrong had nothing to do with you.
Engineering missed a deadline? The PM should have flagged it earlier. A customer is unhappy with a feature? The PM should have scoped it better. Sales promised something that does not exist? The PM should have aligned expectations.
You are the default recipient of frustration because you are the most visible person in the room who is not writing code, not closing deals, and not designing screens. You are the one who is supposed to "make it all work." And when it does not work, the email lands in your inbox.
This is not a bug in the PM role. It is the job. The sooner you accept that, the sooner you stop taking it personally.
The Mistake: Treating Every Email as a Debate
When I was new, I treated every harsh email as an argument I needed to win. Someone said the release was late because of poor planning? I would write a 500-word reply with a timeline, screenshots of Jira tickets, and a detailed explanation of every dependency that caused the delay.
The result? Nobody read it. Or worse, they read it and thought I was being defensive. The email thread got longer. More people got CC'd. What started as one person venting turned into a multi-day discussion about process and accountability.
I was solving the wrong problem. The person who sent the email did not want a timeline. They wanted to feel heard. And my detailed reply told them I was more interested in being right than in fixing the issue.
What I Learned
I later learned that not every email deserves your energy. Most harsh emails are not looking for a discussion. They are looking for a pressure outlet. The person is frustrated, and you happen to be the closest target.
Here is how I handle them now:
If a customer fires a harsh email about delays, do not defend. Reply with something boring: "We understand the urgency. We are looking into what can be done and will update you by [date]." Then go fix the problem. The customer does not care about your internal dependencies. They care about when their thing will be ready.
If someone mails saying you or your team messed up, without hearing your side, do not write an essay. A simple: "Noted. We will be careful next time." is enough. People who want clarity will ask questions. People who want to blame have already decided. Your 500-word reply will not change their mind.
If the email is CC'd to leadership to make you look bad, resist the urge to reply-all with your defense. Talk to the person directly. A 5-minute conversation resolves what a 10-email thread cannot. And leadership notices who escalates and who de-escalates.
If the email is genuinely unfair and factually wrong, still do not reply in the moment. Wait 24 hours. Most of the time, you will realize the reply you drafted at 11 PM is not the reply you want to send at 9 AM. The best response to an unfair email is often no response at all, followed by quietly fixing the problem and letting the results speak.
The Rule I Live By
Spend less time replying than they spent writing.
If someone spent 20 minutes writing a frustrated email, your reply should take 2 minutes. Not because you do not care, but because the email is not where the problem gets solved. The problem gets solved in the next sprint, the next customer call, the next release.
Your energy is finite. Every minute you spend crafting the perfect defensive reply is a minute you are not spending on the thing that actually matters: shipping the product, unblocking the team, or talking to the customer.
When to Actually Respond in Detail
Not every harsh email should be brushed off. There are times when a detailed response is the right move:
- When the criticism is valid and you need to own it. "You are right. We missed this. Here is what we are doing to make sure it does not happen again." Short, honest, no excuses.
- When there is a factual misunderstanding that will cause real damage if left uncorrected. Not ego damage. Real damage, like a customer making a decision based on wrong information.
- When your manager asks you to clarify. If leadership wants context, give it. But give it to your manager directly, not in a reply-all.
The key is knowing the difference between emails that need a response and emails that need you to close your laptop and go fix the problem.
The Bigger Picture
The PM role is inherently thankless in the short term. You do not write the code, so engineering gets credit for shipping. You do not close the deal, so sales gets credit for revenue. You do not design the interface, so design gets credit for the experience.
What you do is hold the whole thing together. And the people who hold things together are the first ones blamed when something falls apart.
That is okay. The PMs who last are not the ones who win every email argument. They are the ones who learn which battles matter and which ones are just noise. They fix the problem, let the results speak, and save their energy for the work that actually moves the product forward.
The next time you get a harsh email, read it once. Close it. Go fix the problem. And if you need to reply, keep it shorter than what they wrote.
Your resume should show the impact of your work, not the battles you fought. If you want to see how well your resume communicates your PM impact, score it against PM best practices.