I work with a person that went presented with a problem, works through it and arrives at the wrong solution. When I have them show me the steps they took, it seems like they interpret things incorrectly. This isn’t a language barrier, and it’s not like they aren’t reading what someone wrote.
For example, they are working on a product, and needed to wait until the intended recipients of the product were notified by an email that they were going to get it. the person that sent the email to the recipients then forwarded that notification email to this person and said “go ahead and send this to them.”
Most people would understand that they are being asked to send the product out. It’s a regular process for them.
So he resent the email. He also sent the product, but I’m having a hard time understanding why he thought he was supposed to re-send the email.
I’ve tried breaking tasks down into smaller steps, writing out the tasks, post-mortem discussion when something doesn’t go as planned. What other training or management tasks can I take? Or have I arrived at the “herding kittens” meme?
Is that why you don’t use the concept of “to be” in your writing?
Oh, I use “is,” “was,” and other “to be” verbs often in speech and even in writing, though I do try to find ways around it simply because I prefer to use more precise language. A “to be” verb is basically an equals sign, i.e. “The job is terrible” could be roughly expressed as “The job = terrible.” While that construction is fine and tells the reader something, it would be better to be more specific because what is usually meant is something more nuanced: “The job has me walking around too much, which hurts my legs.”