3 ms·
If you think that every email has to be a formal masterpiece that will be graded you are over thinking it. That type of work generally belongs in a document in
by mgerdts 4y ago
If you think that every email has to be a formal masterpiece that will be graded you are over thinking it. That type of work generally belongs in a document in G-Suite, confluence, git, etc. Notifications that it exists or needs review may go out via automated or manual email.
If you think that most conversations should be instant messages, you are likely being quite inconsiderate of other people’s time. Likewise, many will not read chat messages that meet some definition of old.
Email tends to have better filters, tagging, sorting, and search to allow the recipient to never miss what is important to the recipient using criteria chosen by the recipient. When I return from vacation I’m sure to read everything sent by my boss and those things related to my area of focus. The rest is likely to go unread unless I’m mentioned in the original or it is brought to my attention.
Collaboration through G-Suite and similar has thankfully ended most passing around of an attachment for review. A similar thing has happened by for code reviews with tools like GitHub and gerrit. Notifications via email from those tools is helpful.
If you are lucky enough to work somewhere that has a culture of plaintext email, in-line replies, proper trimming of cruft from replies, and thread friendly clients, email can be a joy to use. If you work somewhere with Exchange and Outlook, email feels more like a necessary evil.