The problem with deciding in a stream
Chat is excellent for reaching agreement quickly. People float an idea, someone raises a concern, a third person suggests a compromise, and within an hour the group has settled on something. The trouble comes a month later, when someone asks, “Why did we do it this way?” and nobody can find the discussion. Messages scroll away, threads are scattered across channels, and search results are full of near-misses.
Decisions that cannot be found tend to be made again, often with a different outcome, or are quietly forgotten. Keeping a few simple records avoids both. The practice is sometimes called keeping decision records, and it does not need to be heavy or formal.
What counts as a decision worth recording
Not every choice in chat needs a record. A lunch order does not. Record decisions that:
- Affect several people or ongoing work.
- Are hard or costly to reverse.
- Set a rule, a standard or a way of working.
- Might be questioned later, especially by someone who was not there.
- Involve trade-offs, where the reasons are as important as the result.
A good test is to ask whether a new colleague, six months from now, would benefit from knowing it.
Make the decision visible in the thread
The first step costs seconds. When a discussion reaches a conclusion, say so in plain words in the thread: “Decision: we will publish the report on the first Monday of each month. Owner: Maria. Starts next month.” Marking the message with a consistent label or keyword makes it much easier to search for later.
A useful short format has four parts:
- What was decided. One sentence, specific enough to act on.
- Why. One or two sentences about the main reason or the alternatives dismissed.
- Who owns it. A named person responsible for follow-through.
- When it applies or when it will be reviewed. A date, if there is one.
Writing these lines also forces clarity. If the group cannot agree on how to word the decision, there may not really be one yet. Clear writing helps here, as discussed under message clarity.
Pinning and bookmarking
Most chat tools let you pin a message to a channel or save it to a list. Pinning is useful, but it has limits:
- Pins accumulate. A channel with dozens of pinned messages is no better than one with none. Review them occasionally and remove outdated ones.
- Pins are tied to a channel, so people outside it will not see them.
- Pinned items may not be as searchable or well-organized as a document.
Use pins for things that are current and need quick access, such as the latest decision on a process, an important link, or the channel’s purpose. Treat them as a signpost, not an archive.
Summarize before the thread gets too long
Long discussions are hard for latecomers to follow. When a thread passes the point where a newcomer could read it in a minute or two, someone should post a summary. It might say:
- The question being discussed.
- The options considered.
- The conclusion, or what is still open.
- What happens next and who is doing it.
Ask for corrections: “Have I missed anything?” This invites objections while they are still easy to address, and it also guards against a decision that exists only in one person’s head.
Some teams assign a note-taker, or rotate the job, so that it is clear who writes the summary. Without that, everybody assumes someone else will.
Move lasting outcomes into lasting documents
Chat is a poor long-term store. Its history may be limited or removed by retention settings, search is imperfect, and context is lost when channels are archived or people leave. For anything that must last, copy the outcome to a document designed for it, such as:
- A shared document or wiki page with a running decision log.
- A project tracker, attached to the relevant task.
- Meeting notes with a clearly marked decisions section.
- A policy or process page, if the decision changes how work is done.
Link back to the original thread for context, and give the document a clear title and date. A simple log with one line per decision, a date, an owner and a link is often enough. The log can be sorted and searched in ways that chat cannot.
If the decision changes a team rule, update the policy at the same time. A decision that contradicts the written rules causes confusion. This is one reason a chat policy needs an owner and a review date.
Be careful about what moves into the document. Chat sometimes contains personal or confidential details that do not belong in a widely shared page. Copy the outcome and the reasoning, not the whole conversation, and check the guidance on sensitive information if there is any doubt.
Help people find what exists
Even good records are useless if people do not know where to look. A few small steps help:
- Pin a link to the decision log in the main team channel.
- Mention the log in onboarding materials; see the discussion of team onboarding for what new colleagues need to know.
- Use consistent wording and labels so that searches work.
- Name channels clearly and avoid creating many overlapping ones.
- Encourage people to search before asking, and to reply with a link when someone asks a question that has already been answered, kindly and without making them feel foolish.
For teams that cover many hours or regions, written outcomes are especially valuable because colleagues who were offline can catch up on their own schedule, a theme in asynchronous work.
Keep it light
The risk is over-engineering. A heavy process gets skipped, and then there are no records at all. Start with the smallest habit that works: a clearly marked decision line in the thread, and a monthly habit of copying the important ones to a shared log. Adjust as needed. The goal is not perfect documentation but making it easy to answer, quickly and without guesswork, the question of what was decided and why.