Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
Have we started to get reddit style bait on lemmy now? There's no way someone can communicate so poorly in this and multiple responses while blaming someone else for not understanding.
It's pretty funny, I'll give you that.
My wife told me, "please go to the store and buy a carton of milk and if they have eggs, get six."
When I came back with 6 cartons of milk she said, "why in the hell did you buy six cartons of milk?"
I said "they had eggs."
Sometimes being extremely specific helps some people understand. Anything that could have multiple meanings is always open to some interpretation. And while it would be nice if they asked for clarification, they may not because they think they fully understand the instructions.
some people hate legalese, but after reading the situation, I think legalese is made for this sort of problems.
some people learn by example better than following instructions.
also context plays a lot when it comes to instructions. try to see things ahead if played in different contexts.
Though language is an effective means of communication, it's not perfect.
To use an example, there was a meme about a literature professor quoting from a book and telling students what the author meant by mentioning the curtains being blue in a scene. As they go on and on about the melancholy and sadness the author was known to experience at the time, Samuel L Jackson busts in through the door and yells "The color was blue because the curtains were blue, motherfucker!"
Or am I remembering it wrong? Anyway, language is open to interpretation and as such, people will interpret it openly.
It's fine if they get it wrong, you explain how you actually wanted it so they understand and then get it right, sometimes you have to spell out what you mean.
If you explained and showed what you wanted and how, after their mistake, then a 2nd or 3rd time they screw up in the same way that's an issue. Words can mean different things to people.
If it's a different screw up each time, and they aren't intentionally being obtuse, then you could probably be clearer or explain yourself better.
I wish I knew. I have a coworker who flat out doesn't understand anything about his job and causes others to do all his work for him. He has been employed with us for a year and has barely improved. I personally would never give him a task because I know he'd fuck it up royally, causing a day task to be become a 5 day task while wasting hours of other people's time.
I have tried talking to managers about him and they won't listen. I cannot understand how he's not been fired. The motherfucker clearly is not working 90% of the time. His slack status shows him offline almost always, he doesn't respond to emails or GitHub notifications. He opens about 1 pull request per two weeks, and most of them have 50 or more comments from other developers pointing out the same mistakes he always makes. I think every single task he's successfully completed has been via pair programming, and when I've been involved it's been painful how little he gets. Baffling shit.
I think I work with this guy.
Not sure why so many people here comment that your communication style is vague.
Both instructions and issue are clear. Send product after notification was sent via mail. Colleague did that and aso sent the mail again, which had already been sent.
Why people are talking about the product being sent as the issue in thus scenario is beyond me.
As for a solution: Let them repeat back to you what they're supposed to do in their own words to verify you're both on the same page, before the do what they need to do.
If you have tried this unsuccessfully, I have no further suggestions without a whole lot more detail except for: ask theco worker in question how they would have phrased the task if they had given it to someone else. Try and learn what their style of communication is and adjust for that particular colleague.
Most people would understand
...and some people would not understand.
If you want that the other party understands, then you need to be specific.
if others were regularly coming to me with questions about my direction I would agree with you. In this case I was an outside observer to how the situation transpired, and the individual seems to run into this problem with me and others.
the individual seems to run into this problem with me and others
Of course he does. People are people. Some are this, others are that.
What is your question? Do you want to change the other person? It never works. You can only change your own part.
How to work with someone that regularly arrives as the wrong answer?
Yes.
I'll join the others here saying that it's very unclear what you're requesting, what your colleagues did, what they were supposed to do, and what actually happened.
It may serve you well to look inwards for a solution to your problem.
From the way this post is written, I think you don't realize how vague your communication style is. Too many possible interpretations of what you said makes it hard to even follow the story you laid out.
Who emailed who about what?
How did someone resend an email that someone else sent?
Re-sending would mean the same coworker sent the email twice.
On rereading, I think you meant that one coworker sent an email to the client, then another coworker that you are having trouble with also sent the same email to the same client.
So, to answer your question, I think they arrive at a different conclusion because they see things differently. Anything that can be interpreted differently will be interpreted differently. The other co workers think they're giving this person set values when in fact they're handing them a set of variables and expecting only one result.
Have you considered events from their perspective? From what you've described, they were told to wait until a notification was sent, then they were given a notification with the instruction "send this". If it was me my first thought would absolutely be that that's the notification to be sent, the only reason I'd hesitate is because those sort of communications are well outside my job description.
The reason they sent the product afterwards is obvious; they were told to send them after the notification was sent, and they had sent the notification.
From what you've described, you are communicating incredibly poorly then blaming your workers for misunderstanding.
I wasn’t directly involved in this example, so if the problem was with how I communicate it didn’t affect this situation.
I agree that the request was worded poorly but you correctly hesitated.
Unfortunately they seem to be the only one that has difficulty in asking questions when the instructions are unclear or outside the norm.
Yes, it was too vague. OP may have set a tone that doesn't allow for clarifying questions, or the coworker honestly thought they were carrying out every step exactly as it was told to them and didn't see the need for clarification.
Is he maybe just a really literal person and took the forwarded email with instructions "send THIS to them" as "send this email to them", but then he knows his work responsibility is to send the product, hence why he sent both the product and the email?
Do you have an SOP or exact steps to follow written down in a very clear, concise manner (yes, even something as simple as "after employee A sends the email, employee A will notify employee B to send out the product by forwarding the customer email to employee B"; I'm talking reaaaallly literal steps here)?
Can you give other examples of times he's messed up in a similar way?
Does he have poor reading comprehension? ADHD?
I train employees a lot in my current job and jobs prior and I've learned that everyone interprets things differently and learns at their own pace. Most times you can adapt to their style, but sometimes people are just mentally out to lunch 24/7 and not fit for the job.
Might be a high functioning autist? If he got sent the notification email, he could interpret "go and send this" as what he is supposed to send, and thus the logic of shipping the product afterwards kicks in and he also sends that. Just my two cents as a fellow high functioning autist...
But then why did he also send the product?
ETA: Apologies, I feel my lack of reading comprehension on this one deeply.
Because the product was supposed to wait until the email was sent. Email sent -> no problem, send the product next.
Ah, so he was just following his set of the instructions. This situation is exactly why I teach students to always put some kind of noun after a "this," so that it is clear what "this" refers to.
This is simple, practical advice that I can use when instructing coworkers. Thank you!
Saving this to see if there is an answer.
Side note : just my opinion, but some people will never understand basic logic.