1073
submitted 1 year ago* (last edited 1 year ago) by zoe@lemm.ee to c/aboringdystopia@lemmy.world
you are viewing a single comment's thread
view the rest of the comments
[-] theragu40@lemmy.world 3 points 1 year ago

I found this hilarious to read.

Take it from another would-be English major who found a career in IT infrastructure. We are the ones with the problem over-explaining things because we value having a full information set over being concise. The thing is I agree with you that people are overly terse, or maybe more directly people are unable to process long blocks of information. It's frustrating, because I would rather have it all in one place to reference back to.

But I've found the flip side of that is that in my efforts to ensure there is no possible way to misconstrue my communication, I lose everyone in its length. Yes it would be nice if everyone was able to digest what amounts to a technical manual-cum-email so they have a full understanding. But the reality is that the vast majority of people cannot. They simply shut down and stop reading. Therefore it is my responsibility to adjust my delivery to be most effective for the intended audience. This includes fewer words, more direct points, and less supporting details unless asked for more.

I guess my point is, I see myself in your comment. And I wanted to share that I used to feel that way but time has softened my outlook and opened me to the idea that I'm definitely complicit in the overall lack of understanding by failing to account for my audience.

Look at that, there I go rambling again!

[-] MystikIncarnate@lemmy.ca 1 points 1 year ago

I understand. The way I've taken to structure my messages is to provide the terse summary up front then elaborate as I go, summarize tersely at the end and re-pose any pressing questions. This way the reader can mostly skip the middle of my email and go from the executive summary at the top and forward themselves to the last few sentences and hit reply. If they want more detail, it's all there.

I try to keep away from any overly technical jargon, and kind of "dumb it down" aka, use non-technical language as much as I can while still keeping to the point and being accurate. If they want the technical jargon version, they can ask, but they never do.

I find it helps me since I can go back and reference the information if I need it, or point the client to it and go over it with them later if they ask at a later date.

I don't know if that's something that's possible with your work, but it seems to minimize the follow ups and the end user seems to be happy most of the time. There's always a few that will complain, but I've gotten more compliments on my communication style than anything.

this post was submitted on 06 Oct 2023
1073 points (97.8% liked)

A Boring Dystopia

9744 readers
355 users here now

Pictures, Videos, Articles showing just how boring it is to live in a dystopic society, or with signs of a dystopic society.

Rules (Subject to Change)

--Be a Decent Human Being

--Posting news articles: include the source name and exact title from article in your post title

--Posts must have something to do with the topic

--Zero tolerance for Racism/Sexism/Ableism/etc.

--No NSFW content

--Abide by the rules of lemmy.world

founded 1 year ago
MODERATORS