The impact of a ‘read receipt’ is two-way.Think ‘registered post’, otherwise don’t use it. There are legitimate and well-intentioned reasons for sending ‘read receipts’.Same for the ‘read receipts’, it’s all about how we choose to behave. I’ve not got much to add to that other than what I’ve said before, ’emails don’t send emails, people do’. They’re the first thing I disable when being setup under a new email system.”Nicely put….! Perhaps we should all get our IT departments to follow this advice, for the sake of trust between colleagues. The project encountered 24,368 unread ‘read receipts’ held by a single person (the mind boggles at the state of that inbox!) This is a technical account but worth reading, particularly for the first comment……, “Read receipts have to be the most inane and narcissistic feature of email. Here’s an interesting story about an email migration project on. Interestingly the technical community can also feel the pain of their creation. For those on the receiving end the impact can range from mild irritation to something much less desirable, the undermining of trust between colleagues. Unfortunately the misuse that is enabled by virtually zero effort (cognitive and physical) turns something useful into a problem. However I’m not sure that the potential for misuse by people was fully appreciated. The read receipt is undoubtedly a useful feature that has great value, in the right circumstances. It’s a bit like sending a ‘cc’ to the boss of a colleague, a sneaky action that undermines trust between colleagues. The only other conclusion I can draw is that “ you don’t trust me to read and act upon your email, so you want evidence in case you need to use it against me”. Something More Sinister…… I Don’t Trust You! Unless the document falls into the same category as ‘registered post’ I really don’t see the need for the read receipt. At least they get to feel the pain of the response emails flooding back in their own, undoubtedly, massively overloaded inbox.
Outlook read receipt for one email how to#
Why on earth would someone require a read receipt for an invite to an optional lunchtime presentation? I can only assume that it’s because the sender has some email feature set to automatic and isn’t aware of the impact (or how to turn it off). Some of the ‘read receipt’ emails I’ve seen relate to very innocuous interactions. These situations are generally few and far between in colleague to colleague communication. A hassle to carry out, but necessary for your protection, and the person sending you the package. It’s a bit like the ‘registered post’ package you have to sign for at the front door. Possibly something that affects your terms of employment, has legal implications or involves money. This is a really important email you need to read. Here are some thoughts on why people send them, particularly in relation to colleague to colleague communication. Unfortunately the virtually effortless act of sending a read receipt request can lead to misuse and undermine trust (I’ve explained my logic on this previously). These range from the well-intentioned and legitimate, right through to something more sinister like, a lack of trust between colleagues.
There are many reasons why people need to send email read receipts. Not quite the user experience (UX) emotion or response I’d imagine programmers, developers or the email sender were looking for. I must admit that when I get one, particularly from repeat offenders, I’m sorely tempted to just delete the email without even reading it. Pointless, irritating and questionable behaviour. Why do people send them? Many people I’ve spoken to have, like me, been on the receiving end of read receipt misuse. Do email read receipts make your spirits soar…….? Not mine.
0 kommentar(er)
