Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'd say that if your team needs a meeting summarizer, your team has a meeting problem.

It's a clutch that will help you cope with the problem. But the real value is on fixing the actual issue.



I'd say if you're not using a meeting summarizer, you're wasting someone's time by having them write up notes. if you're not writing up notes, you're wasting someone else's time recapping the meeting for them. meeting notes are a 1 (meeting):many relationship for conveying information as to what was discussed. how else do you go back and see what the one person on the storage team talked to your the person on your team who left last week about so you can go into the next meeting with them prepared?


If your meeting produces "notes", and those are relevant for people that were not in it, you are doing it wrong.

If your meeting is aimed at producing "general understanding", it's already a dangerous one, and the understanding should go to the correct documentation (what is best done during the meeting). Otherwise, it should produce "focused understanding" between a few people and with immediate application.

If all you take from it is notes, well, I'm really sure that your team won't go digging through meetings notes every time they need to learn about some new context. Meeting notes are useful for CYA only, and if people feel safe they'll be filled directly at /dev/null.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: