You have been in this meeting before. Someone asks, "Didn't we already decide this?" There is a long pause. Someone digs through Slack. Someone else checks a Google Doc from three months ago. Nobody can find the decision. So the team discusses it again, arrives at the same conclusion (or worse, a different one), and moves on.
This is not a communication problem. It is a memory problem.
The real cost of re-discussion
Re-discussing decisions is one of the most expensive wastes of time in knowledge work, and it is almost completely invisible. Nobody tracks it. Nobody measures it. But it compounds every week.
- Time: A 30-minute discussion repeated across three meetings is 1.5 hours of senior team time gone.
- Morale: People who remember the original decision feel unheard. Newcomers feel confused.
- Trust: When decisions keep changing, people stop trusting the process and start going around it.
- Speed: Every re-discussion delays the work that depends on that decision.
Why it happens
The root cause is simple: decisions are made in one context (a Slack thread, a Zoom call, a hallway conversation) and then never captured in a place the team can reliably find later.
1. Decisions live in conversation, not in systems
Most decisions are made during meetings or in Slack threads. They exist as messages in a timeline, buried under hundreds of other messages within days. There is no structured record of what was decided, why, or who was involved.
2. Meeting notes are unreliable
Even when someone takes notes, those notes are often incomplete, stored in a personal doc, or filed in a shared drive that nobody browses. The gap between "captured" and "findable" is enormous.
3. People change, context does not transfer
When someone joins the team or switches projects, they have no way to absorb the history of decisions that shaped the current state of things. So they ask questions that were already answered, and the cycle begins again.
How to fix it
The solution is not "take better notes" or "be more disciplined." The solution is to build a system where decisions are automatically captured, enriched with context, and searchable by anyone on the team.
- Capture decisions at the source. When a decision is made in Slack, email, or a meeting, it should be captured without requiring someone to manually copy it into a wiki.
- Add context automatically. A good decision record includes not just what was decided, but who was involved, what alternatives were considered, and what the reasoning was.
- Make it searchable. Text search is not enough. Semantic search that understands meaning (not just keywords) ensures decisions are findable even when you cannot remember the exact words used.
- Connect decisions to related knowledge. A decision about pricing connects to customer feedback, competitive analysis, and revenue data. These connections should surface automatically.
This is what Reattend does
Reattend is built for exactly this problem. It captures raw context from your team's tools (meetings, Slack, email), uses AI to identify decisions and enrich them with metadata, and stores them in a searchable memory graph where connections between related knowledge surface automatically.
The next time someone asks "Didn't we already decide this?", the answer is one search away.