▲ | sneak 2 days ago | |||||||
Most people in meetings don’t type very fast, and find it easier to talk than to write. This means that prior to AI transcription/summary bots, there wasn’t much written documentation about the decisions and conclusions from meetings. Now hopefully that will change. | ||||||||
▲ | a_bonobo a day ago | parent | next [-] | |||||||
In my org we have rotating minutes takers - it effectively takes them out of the meeting, but they do pipe up if an issue affects them directly. Of course people's meeting taking skills vary widely but I still find the human-made minutes far superior and accurate to whatever Copilot cooks up. | ||||||||
▲ | jbc1 2 days ago | parent | prev | next [-] | |||||||
I wasn't so much saying that there should be plenty of documentation generated during a meeting as saying that there should be plenty of documentation prior to the meeting. That the meeting is based on. | ||||||||
▲ | Cthulhu_ a day ago | parent | prev [-] | |||||||
I've also read a thing (dunno if it was opinion or fact) that posited that people's reading ability is directly correlated to a preference for video, I suspect it's the same with meetings. I read / write all day (including on here lmao), meetings are draining in comparison. But the people in those meetings don't read / write nearly as much as I do. I did once think that if the meeting were to be transcribed, people are outputting paragraphs of text in a short amount of time, just verbally. But keeping up with that is pretty draining, as you have to listen and process it, whereas with reading you can skim and re-read things easily. I sometimes think people's basic skills - reading and typing - are underdeveloped or not assessed, and they should be assessed when applying for a job that involves reading and typing. But I don't even think people consider reading/writing skills when looking for staff since the assumption is that everyone's is good enough. | ||||||||
|