Earlier quoted context omitted.
> Back in the day I learned the hard way that sending a long reply to an email just ensures the other side won't read it. You can't assume that you dealt with their request effectively that way Then I guess you didn't deal with much of the empty-headed-managment type much. I learned a different lesson: Write a long email that took time to reason and write, precise and complete text. You get a short reply that is a re…
> This is true 100% I would even say: "Never reply on anything instantly that is not an absolute emergency, ever" you can shorten this to "never reply instantly", because an "absolute emergency" will never be communicated by email.
Based on my experience, it mostly translates to whatever task the person thinks it's important for them. Sometimes people will mark the task as "urgent" just to dump it on someone else.
The other thing is, in critical emergencies, you should work slower than usual. This means muting all notifications and taking your time. Rushing to get things done can exacerbate the issue.
Best engineering managers shield the team in those situation and simply reply with: "thanks, we've been notified and investigating".