4 ms·
I don't literally read aloud the document but I do end up going through and paraphrasing what each section says. I don't think people are generally embarrassed
by uDontKnowMe 5y ago
I don't literally read aloud the document but I do end up going through and paraphrasing what each section says. I don't think people are generally embarrassed they haven't read up in advance, they'll show up like "okay so what is this all about?".
I do include 'Summary' paragraphs at the top that provide a TL;DR for an entire 1-ish page doc. I think people will usually open the doc for a few seconds maybe and then brush it off because the general team culture is that all important information will be passed verbally anyways so no point reading now.
Actually I guess I would like to encourage the entire team to do a bit more of this practice of writing things down. For instance, tickets are usually just ~3 word titles with no context or specifics. It's only once the team meets and verbally describes what the tickets mean, that the work can actually be done. I've noticed this sort of culture at multiple companies now actually.
- watwut 5y agoIn our team, nobody talks and it sux too. Because in writing they dont explain context. Plus they write very terse documents, because writing well takes too much effort.
- HWR_14 5y agoA big part of how to move forward would depend on your position within your company. Are your peers not reading it? People junior to you? People senior to you? Does your boss appreciate your documenting habits or hate that you waste company time? As for the tickets, is it a problem that work isn't don't on them before the meeting?