Some of these are good, some are just needlessly assertive nonsense. Especially the two where it's actively refusing to acknowledge fault or apologize for it, which is standard PR crap. Refusing to apologize and instead saying "thanks for your patience" is what I expect to hear from my ISP when they miss their scheduled install, not from a coworker.
There's nothing wrong with being a normal human being that is capable of admitting their own shortcomings. If never saying sorry means "being a boss" then that explains why there's so many sociopaths as CEOs.
"Hope that make sense?" Vs "Let me know if you have any questions."
The latter is saying "here's the explanation, figure it out, bother me again if you can't". The fromer, while poorly worded, is being helpful, actively attempting to make sure the person understands before leaving them to it. It's both a kindness and doing your due diligence.
God I hate forced formality like this. This is the kind of shit Gen Z and millennials are rebelling against and I'm all for it. It is stupid for us to encourage people to be themselves and then to expect them to act like a completely different person at work, including the way they talk.
I think it definitely depends on your relationship with the recipient. While I do think most of those are better options, I wouldn’t say they’re necessarily what you should write.
All of these are really good examples of writing a good email, except the bottom left one.
The "wrong" example is perfectly fine, and the "correct" example is pretty rude unless you're a project manager addressing your team. Even if you were a project manager, it's still pretty rude.
Take those tips with a grain of salt, as this sort of conventional politeness strategy is heavily dependent on culture, situation, and sometimes even individual*.
I predict that those tips would work poorly with people from cultures where negative politeness ("don't burden the others") is valued over positive politeness ("show appreciation towards the others"). This is fairly common in East Asia for example, but even here in Latin America I got a few people rolling their eyes at "biztalk" like "obrigado pela paciência" (thank you for the patience) over a simple apology.
In special, I can picture the centre advice rubbing a lot of people the wrong way, as it's basically the writer lifting a burden from one's own shoulders (struggling to word something) by creating a burden to the reader ("I expect you to be available offline for a meeting").
*if anyone wants to dig deeper into this subject, check Penelope Brown and Stephen Levinson's Politeness: Some Universals in Language Usage. It's a bit of a technical read for Linguistics (more specifically Pragmatics), but I got plenty laymen who love the book.
Its not that simple. Its ok to apologize sometimes. But not so apologize every fucking time like I do for every minor slide. Also I can see the usefulness to just make the shot call instead of staying 1h writing that message/email. Others are ok too.
I'd never say 'always happy to help' because sometimes I'm actually not, particularly if a client is a pain and badgers me constantly. I don't want to invite more interruption
The thank you for your patience one has always rubbed me wrong. There's honor in apologizing in my opinion. I do like the making a mistake one though and I've tried to adopt that mentality when I'm working with QA on something I've merged. I want them to feel good about finding the mistakes and I want to avoid an adversarial relationship. I've learned that I get way better tickets from QA if they like how I treat them. Treat them like valuable experts and they'll act like valuable experts.
Some of these are great. “Could you do” takes the burden off the other person to propose something initially, and suggests respect for their time. “I will need to leave for” begs forgiveness rather than asks permissions, and since you are communicating it, it gives others the opportunity to correct your decision. These are examples of saving everyone time while still communicating them. Being too nice can be a time waste, like saying hello and then waiting for a response before asking your question.
Some of these take away the autonomy of the other person though, and that’s shitty. “When can I expect an update?” is one of those. It would be better to express this in terms of what you need and why, like “I am reporting to X person at noon tomorrow on this, could you give me an update before then?”
Of course, whether you say “just checking in” or “when can I expect…”, if you have no good reason (micromanaging is not a good reason) for checking in then you’re just being an asshole.
Non-native speaker here. What are the disadvantages of being straightforward? In my native language, it is considered more efficient and polite to be to the point. I have worked with Americans in the past, and I have noticed that they are not straightforward.
Yeah, I can tell why this is from adhddd.com, it's all about assertiveness. People with ADHD in general (including myself, to an extent) have trouble with being assertive, so most of the phrases in this chart try to change a meek or mild-mannered response to a more assertive one. I think part of the struggle of life is finding balance because while some of these are generally improvements, others are generally worse, and the difference will depend on the tone you're going for and the person that you're sending the email.
While most of these are a good rule of thumb, I disagree with 'Always Happy to Help.' > 'No Problem.'
'I'm Always Happy to Help' is a fine response, if you're actually willing to make your time available for the recipient at the drop of a hat. Sometimes that's called for, but I would only reserve it for a few very specific circumstances. I also don't see an issue with saying 'no problem' most of the time. There are situations where something a little more formal is called for, but 90% of the time 'no problem' should work imho.
Saying It’d be easier to discuss in person comes off as “I can’t legally put this in writing because it’s against your contract” and not “this is hard to word/explain.” Lol. This is straight PR shit.
These seem to be based on some core concepts of psychology and interpersonal influence (intended or not). I used to work in that area and picked up a few of these tricks along the way too.
Basically what they do is give your recipient a clear call to action-if you want them to do something, it's best to ask directly VS tiptoeing around. The best example there being the just wanted to check in one. If you want an update, ask for it. That way there's no ambiguity what the response needs to be and they can fire it off quickly without thinking. You can wordsmith it to fit your style and company culture but the point is to tell them what you want them to do.
The other thing I see here is a sort of 2-parter. It's about conveying confidence and positivity in your tone. There's a lot of nuance to this and personal communication style and context of the situation play in more. But basically these items like 'nice catch!' and 'thanks for your patience' all kind of do this, showing a kind of team player attitude that also demonstrates that you know your own worth. 'Happy to help' does something similar but is more subtle-it avoids the negative tone of things like 'no problem' and goes a bit further.
Individually theses communications may have a minimal impact (depending on the situation of course) but over time using this kind of language associates you with positivity and confidence and can help you with with you building work relationships.
Don't judge me... I never use exclamation points unless the context is absolutely fitting. Aka, %1 of my email and text, if not less, uses it.
It's like I've saved it for it's original meaning. My wife isn't a fan of this.
One really important thing I've learned is that you need to tell your employer when you need time off. You never request it.
Another really important thing I learned is if you have a good relationship with your boss is to discuss or ask when it would be best for the company to take time off and try to arrange you schedule with those dates in mind.
As an example of this, I like to take a vacation in the summer so I will usually discuss the best week I can do that with my boss because it's not very importent to me exactly which week I want as long as it's some time in the summer.
Some of these are good, because getting into the habit of thanking people for helping (“thanks for catching that!”) fosters good working relationships or providing specifics that, presumably, work for you, too (“can you do [x] times?”) is a better starting point than being truly open ended.
But I well and truly despise the “thanks for your patience/when can I expect” because we ALL know what you mean and I respect someone far more if they acknowledge, explain, and move on from their errors than just…reword shit.
The one about not saying "I think maybe" is one I actively try to do. Assertiveness is something that doesn't come naturally to me but I've been in too many situations where my lack of assertiveness comes across as uncertainty and introduces confusion into discussions where actually I do know what I'm talking about.
Hi Shelley! How are you? I really hope you're doing well. Shelley, we didn't go to school together and you're not my kris kringle, I'm at work and I need x. Ping me if you need anything. Also donuts in the kitchen.
I think it definitely depends on your relationship with the recipient. While I do think most of those are better options, I wouldn’t say they’re necessarily what you should write.
The "thank you for your patience" comments are really surprising me, to a point where I think I'll just stop using it. It's usually what I'd say going into a meeting if I'm less than 5 min late, but the last one there. As if to say "you could have totally started without me and it would be on me to catch up. But you didn't do that, so thank you." Where "sorry for being late" to me comes off as "I expect you to wait for me before starting, so I'm sorry that I prevented that from happening with my tardiness".
But I guess I just always overthought it or something. Now I feel so bad!