31–40 of 147 posts
That's a signal for me. A signal, that the author of this shit of an article didn't bother reading his own article before publishing it.
This article brings nothing new useful to the table. That's a rehash of someone else's rehash of something they've read somewhere.
this feels like advice for the person running the meeting, not the one being dragged into it. I'm just picturing myself telling my boss "Sorry, this meeting doesn't have a clear goal, so I'm dropping off." Anyone actually have the guts to do this when you're not the senior person in the room?
Not 100%, but seems to work.
Earlier quoted context omitted.
The value of written notes really adds up over time, though. Once a meeting is over, it's over; a Slack conversation is preserved for new hires or absentees or yourself when you return to it after your vacation. I agree though, for a small team to build a shared understanding and move quickly, just having a chat together is definitely more efficient. I don't think the ideas lined out here apply to that organisation s…
I agree in principle, although specifically with slack this is problematic. With emails, wikis, repos, it's easy to index them, or share them with a search engine or LLM. Slack is a moving target; they have the Slack AI, but if you don't enable it, it's hard to just grab all messages from a channel or a thread (and god forbid, you have a channel with multiple relevant threads). A lot of clicks required.
People simply don’t read emails, and ignore documents.
I don’t miss emails. Wiki devolves into a mess after a couple of years. Sharepoint has poor accessibility as there’s this constant churning between the app space and the web space.
I really think if you want to get people to take a document seriously you have to present it and walk people through it. If you get feedback and integrate it then it has collective ownership and it’s more interesting than a soliloquy.
But according to the popular glib, and I would say incorrect interpretation of agile principles, documentation is considered wasteful.
Too many mistakes/typos in text. That's a signal for me. A signal, that the author of this shit of an article didn't bother reading his own article before publishing it. This article brings nothing new useful to the table. That's a rehash of someone else's rehash of something they've read somewhere.
"This meeting could have been an email." - yeah, if people actually read their emails.
Earlier quoted context omitted.
The value of written notes really adds up over time, though. Once a meeting is over, it's over; a Slack conversation is preserved for new hires or absentees or yourself when you return to it after your vacation. I agree though, for a small team to build a shared understanding and move quickly, just having a chat together is definitely more efficient. I don't think the ideas lined out here apply to that organisation s…
I have never searched old chats for anything but passwords, network folder paths and license keys. Going back to some conversation on some topic and give it to the new guy, does it happen?
Is there a minutes taking tool that does automatically list the attendants and their join/leave times, allow me to create items like TODO, DECISION, POLL, DISCUSS_MORE, GET_INFO, BLOCKER that will then be tabulated and cross-referenced automatically across more than one meeting? And added to the TODO-lists of participants referenced?
Preferrably somewhat independently of the conference tool in use, because that varies a lot around here.
Btw, question to the wisdom of HN: Good meetings need minutes. Is there a minutes taking tool that does automatically list the attendants and their join/leave times, allow me to create items like TODO, DECISION, POLL, DISCUSS_MORE, GET_INFO, BLOCKER that will then be tabulated and cross-referenced automatically across more than one meeting? And added to the TODO-lists of participants referenced? Preferrably somewhat…
Ours are pretty informal, we (unfortunately) use MS Teams which has an agenda & notes section; people are asked to fill in the agenda if they have any points (which is frustrating because getting there isn't easy or obvious), people can write down notes and action points during the meeting (it's a shared and collaborative effort).
You can assign tasks to people's todo lists though, but of course the problem is fragmentation; everyone has their own todo lists, there's Jira for work items, etc.