My Honest Review After 3 Weeks of Using Meeting Recording → Summary Automation

We're a team with two meetings a day, so I tried automating the recording and summarizing. To get to the point, it definitely reduces the 'organizing labor,' but you'll be in trouble if you trust and use it as is. It often gets proper nouns and numbers wrong.

Now, after a meeting ends, I only use the automatic summary as a draft, and I personally double-check the decisions and action items. Still, it used to take 30 minutes, but now it's done in 10, so I'm satisfied.

by 클라우드러버634

7 answers

Got a source? I'm curious which tool it is.

by 취준생김씨126 · ▲0

Agreed, this is correct.

by 호기심천국444 · ▲0

But isn't that old news? These days, models rarely get numbers or proper nouns wrong. They didn't say which tool they used, so I can't really judge.

by 코딩하는곰777 · ▲0

I totally get the proper noun struggle... Our team also writes project codenames differently every time, so we end up fixing them by hand lol

by 디지털노마드646 · ▲0

Well, that's a bit... It's nice that 30 minutes becomes 10, but once you factor in review time, the actual savings are less than that, aren't they? I've even spent more time reading summaries before, so now I only run it for important meetings.

by 프롬프트장인689 · ▲0

Oh, I didn’t know that. How did you handle privacy and consent issues for recording automation? The process of notifying team members in advance and getting their consent has been a subtle concern for me, so I’d love to hear how you handled that part too.

by 밤샘코더517 · ▲0

I've used it for about two months too, and I think the answer is to use it only for drafts. In particular, you 100% have to double-check action item assignees. If it gets entered wrong once, everyone just passes the work off to that person... lol. I set up a routine where I spend just 5 minutes after the meeting and skim only the decisions. Just doing that alone has kept things from going wrong.

by 알고리즘고수862 · ▲0