How do I deal with people not reading things?
How do I deal with people not reading things?
I'm autistic. This problem shows up for me all over the place, to the point that I typically don't recommend reading anymore except when strictly necessary. However, it is showing up now because I'm working with people on a project (and generally everyone I have worked with at school so far) who will not read, particularly documentation for tools and programs, data sheets, and application notes. How do I get people "up to speed" if they refuse to read the things I send them?
Some concepts are simply too complex or too lengthy for me to explain correctly in a real conversation. It's really the fact that nobody seems to want to read in any field of endeavor suggests that it's something wrong with me and how I perceive things.
How do I get people "up to speed" if they refuse to read the things I send them?
You dont. Honestly unless you are their manager or lead you can't really make them do anything that helps them.
Disconnect yourself from their lack of self help by reminding yourself that, This is not your circus and they are not your monkeys.
Exactly that. I've got the same problem here. I've got my side of the project well-documented, but the head PC software guy often phones me out of the blue, asking me questions that have long been documented.
Luckily, I can tell him (on most questions) that the information he looks for is so old that I don't have it present anymore, and would have to read my own documentation to get him the answer, so he could do it himself...
Can I get a TLDR?
tl;dr; y u no read
If we put aside everyone who's unable to literally read more than one sentence, I can imagine a different scenario as well.
I have a coworker who's very likely autistic and his type of working is, writing down everything. At first that sounds helpful, you can always go back into the documentation and every ticket has all the information. But for me personally this incredibly annoying. Why? Because he has no filter of compacting information. Some easy tasks, like for instance "CEO wants access to test results of XY", will result in a 20 pages essay.
Again you might think that I'm maybe overreacting, but when you have 20 or 30 tickets that way and are busy solving something that requires more brain power and you got to jump in between issues - because sometimes you're waiting for a reply or other people to act - then it's super frustrating if you jump and it's again a 20 pages essay you got to read. This is super time consuming, frustrating and literally makes me angry.
This might be useful if you have a super complex project and important scientific workflows where you're highly urged to not do mistakes, but otherwise it's way too much. In my eyes this is not efficient working.
My coworker is smart, maybe too smart to work with us, but he also lacks a filter of what information is important and which isn't.
I try my best to not work on any projects with him and skip over most of his writing. Going as far as writing it down myself, to not have to go into his tickets and read his unfiltered "brain puke" and waste time and energy trying to find the gist.
Have you tried to be brief? Maybe throw the text into chatGPT and compare a condensed result with your own?
Also btw, if you're really autistic, then your brain literally works different, compared to how most other people process information and sensory impressions. At least that's what I'd assum autism is about, but maybe I'm wrong.
I have a coworker who's very likely autistic and his type of working is, writing down everything. also lacks a filter of what information is important and which isn't.
This is figuratively me, because yeah I'm autistic and I personally have a dogshit memory. To that end, I've not shown them like 90% of my notes.
This might be useful if you have a super complex project and important scientific workflows where you're highly urged to not do mistakes, but otherwise it's way too much.
See that's the thing though, we really are working on a super complex project where we really can't afford to make mistakes.
Have you tried to be brief?
Yeah I have. I guess not brief enough.
Maybe throw the text into chatGPT and compare a condensed result with your own?
I'll give that a shot!
Also btw, if you're really autistic, then your brain literally works different, compared to how most other people process information and sensory impressions.
Yes I am actually autistic, and I'm aware my brain works different. That's why I decided to get other people's perspectives on the matter.
Executive summaries are a good approach to cut down the chaff. 2 or 3 lines saying what the document is covering so people can at a glance decide if it is relevant to what they are doing.
Some concepts are simply too complex or too lengthy for me to explain correctly in a real conversation.
You might have to deal with people who learn differently than you do, which means you may need to have that conversation.
Bring your documentation and go through it with them so the two of you can discuss.
Complicated instructions need to be documented somewhere everyone has access and tagged appropriately. OneNote would be an easy option. Then whenever a question comes up that you already answered you can send them a link so they have the info when they need it.
Emails need to be kept very short, otherwise everyone will "read them later" (i.e. never)the flipside of this is, I have found that by dint of merely being willing to read manuals that I am viewed as a techno god with domain over all things electronic.
You can tell them it's just reading the manual but they don't listen they think you have some magic power.
(and generally everyone I have worked with at school so far)
The context is a group project you have to do for school?
The reason I am checking is that these often turn into one person desperately trying to get the others to do something and ending up doing it all themselves. You're not really talking about "people" so much as "students who half-arse it until a few hours before the deadline".
What is it you're trying to get them to do? Why do they need to read the stuff you're sending them?
particularly documentation for tools and programs, data sheets, and application notes.
No one reads this stuff unless they absolutely have to. What is the purpose of asking them to read it?
The context is a group project you have to do for school?
Yeah, grad school. I was expecting four years of college to filter out unserious students.
The reason I am checking is that these often turn into one person desperately trying to get the others to do something and ending up doing it all themselves.
I genuinely hope they just ask me to do the whole thing, because I can do the whole thing myself. I brought them on because I need to learn to work with people. Naturally, I would always work alone, but I've been burned a few times trying to take on group projects solo and burning myself out, so I brought on some people to split the work.
What is it you're trying to get them to do? Why do they need to read the stuff you're sending them?
I don't want to give out too many details in case they show up here, but I am trying to get them to write basic implementations of a few key features. They need to understand how the microprocessor actually communicates with the peripherals so they can configure it (and the peripherals) correctly. This topic is exactly what the course is about.
No one reads this stuff unless they absolutely have to. What is the purpose of asking them to read it?
It's a coding-intensive project where we need to communicate with a few peripherals without locking up the rest of the system. There's no way to just "figure out" this stuff. You either read the code, or you read the docs, or you flounder.
I notice that people refuse to read emails. They would rather have a 30 minute conversation where I give them all of the information/questions that would have been an email and I hate it.
One way I deal with it is to PARE BACK the content I need to give them and use bullet points. You have to get it to the absolute bare bare bare minimum. Never write more than two short, broken up, and spaced out paragraphs. Bullet points should never be more than one brief sentence.
I've had increased success in getting people to accept and respond to emails that way.
Different people have different learning styles. Some people will refuse to read. Some people were will refuse to ask questions only read. Depending on the project you're working on you have to tailor the communication to the person.
There's a reason YouTube channels are successful by basically reading documentation out to people.
Some people were will refuse to ask questions only read.
Hi.
I've tried to address that by sending them videos on the topic and teaching them the fundamentals in person as best as I could, but still no dice.