People at new company just…don’t respond

[Anonymous]

Do you use slack, teams something similar? I’ve noticed almost all communication in my company happens there. Hardly anyone uses email anymore. I think some people rarely check email.

[Anonymous]

Anonymous wrote:

Anonymous wrote:If they do what you tell them to do, that is your response. An acknowledgement is great but a lot of people don’t like email and don’t want to clog up someone’s inbox with a “got it, thanks!” IME, the younger generation typically does not respond with a “thanks,” they just do the work, and they won’t even tell you that they completed the assignment, but it’s done.

OP I am late thirties and dont send a thanks email unless it’s something someone resolved or posted for me, etc. I do send an email when I have completed a task that literally just says: Completed. I dont Hi or sign off. I know a lot of organizations use program management software so maybe you need to implement that to track whats being done. If thats already in place you dont need a completion email.

Wow I would really think you were a d*ck if you responded “completed” especially if you are a dude. Not sure why it would kill you to add a greeting or a full sentence.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:If they do what you tell them to do, that is your response. An acknowledgement is great but a lot of people don’t like email and don’t want to clog up someone’s inbox with a “got it, thanks!” IME, the younger generation typically does not respond with a “thanks,” they just do the work, and they won’t even tell you that they completed the assignment, but it’s done.

… which is very unprofessional. I don’t expect a response from people included on emails for information only, or to emails that are just informational updates. But I definitely expect a response from people when the email described a task they have to do.

People keep telling you it’s not abnormal yet you keep calling it unprofessional.

You said yourself they do the work. I think your need for attention and fanfare is unprofessional. Agree with the poster who said you’re bored.

I’m not OP. I am an experienced professional with a lot of experience in cross-team collaboration at several workplaces, and I absolutely would consider a non response to be unprofessional.

[Anonymous]

Anonymous wrote:I agree, if they did what you wanted in a shared doc, what’s the issue? They know you can see it. You know they can see it. Why add an email? That’s make work. Especially for an internal program.

It sounds like you’re not busy enough, to me. Client work is more important.

Because just because I see someone make one edit to a shared doc doesn’t mean I know they are finished. Among other reasons.

Clear communication is not make work.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:If they do what you tell them to do, that is your response. An acknowledgement is great but a lot of people don’t like email and don’t want to clog up someone’s inbox with a “got it, thanks!” IME, the younger generation typically does not respond with a “thanks,” they just do the work, and they won’t even tell you that they completed the assignment, but it’s done.

… which is very unprofessional. I don’t expect a response from people included on emails for information only, or to emails that are just informational updates. But I definitely expect a response from people when the email described a task they have to do.

Disagree. I'm in a very formal environment and we are not supposed to be clogging up people's inboxes with "thanks" or "on it". We have an official policy on it. It is considered rude to keep typing inane responses. You should send an email back though if you don't understand the task or something needs clarified.

You're supposed to send an email with a due date and it gets done. If the work isn't being done by the due date, that's what needs addressed.

I don’t know what kind of process you work on, but I absolutely expect an acknowledgment of when the work is done. It is also very uncollegial not to engage with a new colleague at least once or twice to establish the relationship.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:If they do what you tell them to do, that is your response. An acknowledgement is great but a lot of people don’t like email and don’t want to clog up someone’s inbox with a “got it, thanks!” IME, the younger generation typically does not respond with a “thanks,” they just do the work, and they won’t even tell you that they completed the assignment, but it’s done.

… which is very unprofessional. I don’t expect a response from people included on emails for information only, or to emails that are just informational updates. But I definitely expect a response from people when the email described a task they have to do.

I think it's just a different way of working, especially for younger or offshore cohorts. It can be annoying for sure but the pace of work means people don't always stop to acknowledge or confirm that they did what you asked them to do.

And per the bolded, if you're not my boss and you pull that, you're going to the bottom of the list if you are looking for info or a favor.

lol well likewise.

Young people - err on the side of establishing relationships and being polite.

[Anonymous]

Most collaborative work is done either with a shared document which tracks if people have made changes or task or assigned to a workflow ticket system. The only people who really should get away with emailing off tasks as they percolate from their brain or an executive level and, generally emailing their secretary or VP to then translate it into a tracked activity.

There was a real cost to cc people into add low value acknowledgment, he just clogged up mailboxes.

Also to the PP who sends the email a bunch of people no one gets on it, there’s a saying in my industry that when everyone is responsible, no one is responsible. You need to always delegate a task to a belly button, just like when they say and see if you are training you point at an individual and say YOU call 911

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:If they do what you tell them to do, that is your response. An acknowledgement is great but a lot of people don’t like email and don’t want to clog up someone’s inbox with a “got it, thanks!” IME, the younger generation typically does not respond with a “thanks,” they just do the work, and they won’t even tell you that they completed the assignment, but it’s done.

… which is very unprofessional. I don’t expect a response from people included on emails for information only, or to emails that are just informational updates. But I definitely expect a response from people when the email described a task they have to do.

I think it's just a different way of working, especially for younger or offshore cohorts. It can be annoying for sure but the pace of work means people don't always stop to acknowledge or confirm that they did what you asked them to do.

And per the bolded, if you're not my boss and you pull that, you're going to the bottom of the list if you are looking for info or a favor.

lol well likewise.

Young people - err on the side of establishing relationships and being polite.

Whatever, we all know that that senior employee would replace that young person with an AI and a half a heartbeat if they could

[Anonymous]

It sounds like no response is required and these emails are summarizing next steps. I wouldn’t expect any acknowledgment of such emails.

[Anonymous]

* in half a heartbeat

[Anonymous]

Anonymous wrote:Most collaborative work is done either with a shared document which tracks if people have made changes or task or assigned to a workflow ticket system. The only people who really should get away with emailing off tasks as they percolate from their brain or an executive level and, generally emailing their secretary or VP to then translate it into a tracked activity.

There was a real cost to cc people into add low value acknowledgment, he just clogged up mailboxes.

Also to the PP who sends the email a bunch of people no one gets on it, there’s a saying in my industry that when everyone is responsible, no one is responsible. You need to always delegate a task to a belly button, just like when they say and see if you are training you point at an individual and say YOU call 911

Not all offices have task management systems like that - most still just have emails. And no, the fact that you edited a Sharepoint doc at 3:52 yesterday does not tell me you are done.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:If they do what you tell them to do, that is your response. An acknowledgement is great but a lot of people don’t like email and don’t want to clog up someone’s inbox with a “got it, thanks!” IME, the younger generation typically does not respond with a “thanks,” they just do the work, and they won’t even tell you that they completed the assignment, but it’s done.

… which is very unprofessional. I don’t expect a response from people included on emails for information only, or to emails that are just informational updates. But I definitely expect a response from people when the email described a task they have to do.

Disagree. I'm in a very formal environment and we are not supposed to be clogging up people's inboxes with "thanks" or "on it". We have an official policy on it. It is considered rude to keep typing inane responses. You should send an email back though if you don't understand the task or something needs clarified.

You're supposed to send an email with a due date and it gets done. If the work isn't being done by the due date, that's what needs addressed.

I don’t know what kind of process you work on, but I absolutely expect an acknowledgment of when the work is done. It is also very uncollegial not to engage with a new colleague at least once or twice to establish the relationship.

Well in my case, when the work is done they send it to you before or on the due date.

Of course we engage with new colleagues. Usually in person, on Teams chat or during a brief intro call.

I receive about 100 emails a day. I don't need that number to be 200 with people saying thank you nonstop. Or introducing themselves by email.

[Anonymous]

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:If they do what you tell them to do, that is your response. An acknowledgement is great but a lot of people don’t like email and don’t want to clog up someone’s inbox with a “got it, thanks!” IME, the younger generation typically does not respond with a “thanks,” they just do the work, and they won’t even tell you that they completed the assignment, but it’s done.

… which is very unprofessional. I don’t expect a response from people included on emails for information only, or to emails that are just informational updates. But I definitely expect a response from people when the email described a task they have to do.

Disagree. I'm in a very formal environment and we are not supposed to be clogging up people's inboxes with "thanks" or "on it". We have an official policy on it. It is considered rude to keep typing inane responses. You should send an email back though if you don't understand the task or something needs clarified.

You're supposed to send an email with a due date and it gets done. If the work isn't being done by the due date, that's what needs addressed.

I don’t know what kind of process you work on, but I absolutely expect an acknowledgment of when the work is done. It is also very uncollegial not to engage with a new colleague at least once or twice to establish the relationship.

Well in my case, when the work is done they send it to you before or on the due date.

Of course we engage with new colleagues. Usually in person, on Teams chat or during a brief intro call.

I receive about 100 emails a day. I don't need that number to be 200 with people saying thank you nonstop. Or introducing themselves by email.

It sounds like you are not in a project management role.