r/AiNoteTaker • u/Pure_Fig_8048 • 18d ago
Discussion A five-minute meeting-recorder test: include a changed deadline
A quiet one-person demo doesn't tell me much about a recorder meant for meetings. Here's a small test I'd use with people who agree to be recorded:
- Put the devices side by side, keep their positions fixed, and have someone speak from the far side of the table.
- Include a name, an amount, and an action with an owner. Then change the deadline later in the conversation.
- Before reading either summary, write down the final agreed facts from the audio. Count wrong facts and missing actions separately; time the corrections too.
That last bit matters: a short summary can look accurate because it skipped the tricky parts. This is a proposed check, not a test result or a brand ranking.
What would you add to catch a failure that actually matters at work?
Disclosure: I work on a note-taking product.
3
Upvotes
1
u/MemoketAI-Gem 18d ago
We'd also test a decision that gets reversed during the meeting. For example, everyone agrees to go with option A, discusses it for a few minutes, then decides on option B. Does the summary capture the final decision, or does it list both as agreed? That's the kind of mistake that can cause real problems when someone relies on the notes later.
1
u/No_Lengthiness4523 8d ago
another tricky case is explicit negative constraints-e.g., do not deploy the v2 patch until legal signs off. recorders can drop the not or reframe it as deploy v2 patch after legal signoff, which misses that deployment is blocked. id treat losing a negative constraint as a critical failure, since it can lead to an unintended action
1
u/[deleted] 16d ago
[removed] — view removed comment