It's a parody of how tiresome emailing is in real world applications.
In an ideal world, you ask someone to do something, they ask you for details, you give them details, it's done.
In a less ideal world, you have busy people, lazy people, and people who have been given unreasonable schedules.
They drop emails, overlook, glance it over. They dread the back and forth long email threads, so they sit and think and procrastinate for an hour before sending a short email like the above.
And what let's say there's three teams involved. One person drops the ball or ignores an email. What next?
That's why you have to cc them. I once had an issue with this guy who I just kept giving him instructions, having meetings, and he still did the wrong things. I brought it up to the boss and he yelled at me and told me I don't know how to work in a team -- I never cc'ed him in these emails.
And I quickly learned that whenever an email cc-ed the boss, things moved, and when it didn't, they'll say okay, but the work would disappear.
Then the obvious solution is to cc every time right? But because of this, every time you cc someone, it implies that you don't trust them to get it done.
Something like Slack just automates this process. You post something in a team channel, it gives a slight-but-not-passive-aggressive pressure. You can send a document and it doesn't get lost (and you can't blame someone for not sending you the documents).
In an ideal world, you ask someone to do something, they ask you for details, you give them details, it's done.
In a less ideal world, you have busy people, lazy people, and people who have been given unreasonable schedules.
They drop emails, overlook, glance it over. They dread the back and forth long email threads, so they sit and think and procrastinate for an hour before sending a short email like the above.
And what let's say there's three teams involved. One person drops the ball or ignores an email. What next?
That's why you have to cc them. I once had an issue with this guy who I just kept giving him instructions, having meetings, and he still did the wrong things. I brought it up to the boss and he yelled at me and told me I don't know how to work in a team -- I never cc'ed him in these emails.
And I quickly learned that whenever an email cc-ed the boss, things moved, and when it didn't, they'll say okay, but the work would disappear.
Then the obvious solution is to cc every time right? But because of this, every time you cc someone, it implies that you don't trust them to get it done.
Something like Slack just automates this process. You post something in a team channel, it gives a slight-but-not-passive-aggressive pressure. You can send a document and it doesn't get lost (and you can't blame someone for not sending you the documents).