After every consequential meeting, someone writes notes. The notes capture what was said, the points raised, the considerations discussed. They get filed in Notion or Confluence, shared in the meeting thread, and consulted exactly once — by the person who wasn't there and needed to catch up. Within two weeks, nobody reads them again.
The problem is not that teams write bad meeting notes. The problem is that meeting notes are the wrong artifact. Teams need decision records, not discussion records.
The distinction that matters
A discussion record captures what was said. A decision record captures what was concluded.
Discussion records are useful for the meeting participants who want to remember the conversation. They're nearly useless for anyone trying to understand the current state of the team's commitments, direction, or reasoning. To find a conclusion in a discussion record, you have to read the entire document and extract it yourself — work that the record should have done for you.
A decision record answers a different question: "What did we decide?" One sentence. Present tense. No reconstruction required.
Why teams default to discussions
Three reasons teams end up with discussion records when they need decision records:
Notes taken during the meeting, not after. Real-time note-taking captures the conversation as it unfolds, which produces a discussion transcript. Decision records require a moment of reflection after the meeting closes — time to answer "what was actually decided here?" That moment gets skipped when the notetaker is running to the next meeting.
Nobody wants to declare a decision. Declaring a decision creates accountability. If it's wrong, it's traceable. Discussion records let everyone maintain plausible deniability — the document shows there was a conversation, not necessarily a conclusion. This is psychologically comfortable and operationally disastrous.
Conflating "we talked about it" with "we decided it." Teams often leave meetings with alignment on a direction but no declared decision. Alignment is not a decision. Alignment means people are pointing the same way; a decision means someone committed to a course of action with defined authority. Without that commitment, the "decision" dissolves the next time someone raises a different view.
Declarations, not discussions
StandIn is built on the principle that decisions should be declared, not inferred. Every wrap captures what was decided — not what was discussed — so the team's decision record is always current without requiring a separate documentation step.
Request early accessThe right tool for each
Discussions and decisions need different infrastructure:
Discussions belong in ephemeral tools. Slack threads, Loom videos, meeting recordings, shared docs used for collaborative thinking. These tools are great at capturing the flow of a conversation. They're terrible at surfacing conclusions. Use them for discussion, accept that they're ephemeral, and don't try to make them into a knowledge base.
Decisions belong in durable tools. A searchable wiki, a governance tool, a dedicated ADR folder in the repo, a decision log maintained by the Chief of Staff. The defining property of the right tool: the decision is findable in twelve months by someone who wasn't there, using a search on the topic — not a search on the date or the meeting name.
The mistake is trying to make one tool serve both purposes. Notion is used as both the discussion space and the decision archive, which means neither function works well. Slack becomes the place where "permanent" decisions get posted because posting in Slack is fast, which means decisions get buried within a week.
How to run the transition
If your team currently has discussion records and wants decision records, the transition takes two changes:
Change 1: End every meeting by naming decisions explicitly. Before the meeting closes, someone asks: "What decisions did we make here?" The answers get written down immediately, before anyone leaves the room. This step is the most important and the easiest to skip. Don't skip it.
Change 2: Move decisions to a durable location within 24 hours. Wherever decisions land in the moment — on a whiteboard, in a meeting doc, in the final Slack message of the discussion — they need to be moved to the canonical decision record location before they get buried. Twenty-four hours is a reasonable window. Forty-eight hours means half of them won't make it.
What teams discover when they make the switch
Teams that separate decision records from discussion records consistently find the same thing: they made fewer decisions than they thought. Many conversations that felt like decisions were actually discussions that ended without a declared conclusion. Surfacing this gap is uncomfortable and useful. It forces the team to distinguish between conversations that concluded and conversations that just stopped.
The second thing teams discover: the rejected-options field in their decision records is the most valuable part. The options that were considered and ruled out — with documented reasoning — prevent the team from re-evaluating the same alternatives in future meetings. Without this field, rejected options have a way of reappearing as if they were never considered.
Frequently asked questions
Should we stop taking meeting notes entirely?
No. Meeting notes serve a purpose — they help participants remember the conversation and help absent team members follow along. The change is to stop treating meeting notes as the knowledge system. They're a communication artifact, not a knowledge artifact. The knowledge system is the decision record; the meeting notes are the supporting context.
What about decisions made outside meetings — in Slack or async?
These are the decisions most likely to get lost. The same rule applies: once a decision is reached — even in a Slack thread — it should be captured in the decision record within 24 hours. Async decisions often feel less formal, which makes them more likely to be skipped. They're not less important; they're just made in a context that makes documentation feel optional.
How do you handle decisions that get reversed?
Update the record rather than deleting it. A reversed decision is itself a decision: add a new entry that references the original, explains what changed (new information, changed context, changed authority), and documents the new direction. The history of a decision — including its reversals — is often more valuable than the current state alone.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.