I agree, but, you’d be surprised how many people find many of these seemingly innocuous distinctions offensive (if only a little bit). For example, I was once chided by HR for saying ‘no problem’ during a seemingly friendly discussion.
Most? I can definitely see “when can I expect an update?”, that one’s terrible. “It would be best if we” sounds pretty self-assured without a modifier such as “in my opinion” (which is what the original option was doing). “Nice catch!” is also a bit too honeyed and casual as well. But I don’t see a problem with the rest of them.
I actually like nice catch, as long as it’s not an egregious error. There are often going to be mistakes in a document, even when prepared by someone completely competent. This acknowledges someone as being part of a process instead of focusing on an error.
To be honest, I find most of these passive aggressive and patronizing.
I agree, but, you’d be surprised how many people find many of these seemingly innocuous distinctions offensive (if only a little bit). For example, I was once chided by HR for saying ‘no problem’ during a seemingly friendly discussion.
Seems like a toxic work environnement to get chided for so little…
Agreed. Got my revenge though. They got fired a week after I quit working there.
If someone has a problem with “no problem,” they have a problem.
I mean apparently some people think a thumbs up in a chat is passive aggressive.
👍
I don’t know how else to explain it, but thumbsup is the boomerest emoji.
Nah, mate. 😱 is the boomerest emoji
I do NP!
Most? I can definitely see “when can I expect an update?”, that one’s terrible. “It would be best if we” sounds pretty self-assured without a modifier such as “in my opinion” (which is what the original option was doing). “Nice catch!” is also a bit too honeyed and casual as well. But I don’t see a problem with the rest of them.
Nah. By my count, 1 is context dependent, 2 are okay, the remaining 6 are kinda cunty.
I actually like nice catch, as long as it’s not an egregious error. There are often going to be mistakes in a document, even when prepared by someone completely competent. This acknowledges someone as being part of a process instead of focusing on an error.
it’s a guide to being a soulless corporate cog