A good brainstorm is the highest-yield meeting a team runs: fifty ideas an hour, three of which get taken into work. The arithmetic everyone ignores is what happens to the other forty-seven. They don't get rejected — rejection would leave a record. They evaporate: half-captured on stickies, photographed, filed in a folder nobody reopens. And with them evaporates something more valuable than the ideas — the reasons: why this one was parked, what that one conflicted with, who saw the risk.
A quarter later, someone proposes a "new" idea. It's idea #23 from the last session. The team spends another hour walking the same path to the same conclusion — the most expensive déjà vu in product work.
Key takeaways
- Brainstorms lose ideas by design: capture competes with flow, and flow wins — as it should. The fix is capture that costs the meeting nothing.
- The valuable artifact isn't the idea list — it's decisions with reasons: "parked till fall — no bandwidth" is reusable knowledge; a bare sticky saying "team plan" is not.
- A recording keeps the harvest without a scribe: voiced ideas and decisions land in the summary; everything — including tossed-off half-ideas — stays findable in the transcript (product facts below).
- Honest scope: the "idea bank" is your searchable meeting archive playing a role — there's no dedicated idea-scoring or dedupe feature, and this article won't invent one.
Why capture loses to flow
Brainstorms run on momentum: the half-formed thought someone blurts is the raw material for the next person's better one. Appointing a scribe throttles exactly that — people slow down for the pen, self-censor for the record, and the meeting produces fewer, safer ideas. Stickies are faster but capture labels: "team plan" on a yellow square, with the two minutes of reasoning around it — the objection, the twist that made it interesting — living nowhere.
So teams face a false choice: document and dampen, or flow and forget. The recording dissolves it — the meeting runs at full speed, and the capture happens afterwards.
The harvest: ideas, decisions, and the why
Process the recording and the summary returns the session's structure: the ideas that were voiced, and the decisions around them — taken, parked, dropped — with the reasons that were said out loud (product facts: summaries capture discussion content with decisions extracted as distinct items). "Parked till fall — no bandwidth" and "dropped — conflicts with pricing" are the sentences that make the archive worth querying later.
Two honest mechanics. First, a summary compresses: a half-sentence idea tossed off and never picked up may not make it — but the full transcript catches everything, and it's searchable, so the safety net is complete even where the summary is selective (product fact). Second, "who saw the risk" requires speaker attribution, which runs on the premium engine — and rapid crosstalk is diarization's hardest case, a limitation detailed in speaker diarization explained.
Ideas that were taken become tasks with owners in the tracker, same as any meeting (product fact; the pipeline is in how to turn a meeting recording into tasks).
The bank: parking with a retrieval ticket
The archive turns "parked" from a euphemism for "killed" into an actual state. When the context changes — budget arrives, a competitor moves, fall comes — the parked idea is retrievable with its reasoning: search finds the session, questions to the archive ("didn't we discuss team subscriptions?") come back with the date, the decision, and who had doubts (product facts).
That changes two recurring moments. The déjà vu moment: idea #23's second appearance costs a lookup, not an hour — and sometimes the lookup says "context changed, unpark it," which is the system working, not failing. And the onboarding moment: a new product manager reading a quarter of brainstorm summaries inherits not just what the team decided but how it thinks — one of the fastest ways to transfer how a team thinks.
What stays craft
The pipeline captures; it doesn't facilitate. Divergence-convergence structure, voting, keeping the loud from drowning the quiet — that's still the facilitator's job, in whatever board or format works. And the bank is an archive playing a role: there's no idea deduplication, no scoring, no idea-stage kanban — if your idea volume outgrows search-and-ask, a dedicated tool awaits downstream. What the recording guarantees is that whatever tool comes next inherits a corpus instead of a folder of sticky photos.
Sources and method
Product facts (summaries with decisions extracted as distinct items, full searchable transcripts, task extraction with owners and tracker push, full-text search and archive-wide questions, speaker attribution on the premium engine) describe MeetResult as documented in the product catalog at the time of writing. "Idea bank" describes a use of the meeting archive, not a dedicated feature; no idea-scoring, deduplication, or idea-pipeline functionality is claimed. Idea counts ("fifty," "forty-seven") are illustrative. No statistics are cited or invented.
Related: How to turn a meeting recording into tasks · Speaker diarization explained · Retro action items that survive the sprint · Three of fifty ideas survive — now the rest do too (use case)
Next brainstorm, appoint no scribe: record it, run it at full speed, and drop the file into @meetresultbot. Check what the harvest looks like when nothing evaporates. New accounts include free processing minutes.