How to document decisions in Slack without killing the conversation

Why Slack loses your decisions

Slack is where modern teams decide things. It is also, by design, where decided things disappear. A channel is optimized for flow: the newest message wins, threads collapse, and anything older than a fortnight exists only for people who know exactly what to search for. The decision about the vendor renewal is in there somewhere, spread across forty messages, two threads, and one hallway conversation that never made it in at all.

Search does not save you, for a reason worth understanding: a decision is not a message. It is a conclusion that emerged across messages, and usually nobody wrote the concluding sentence. What you can search for is the debate; what you need is the ruling. Documenting decisions in Slack means separating the ruling from the debate, and there are three ways teams do it, in increasing order of reliability.

Option 1: a #decisions channel

The lightest convention: a read-mostly channel where every settled decision gets one message in a fixed format. The question, the decision, the owner, the date, a link to the thread where it was debated. Keep the format in the channel topic so nobody has to remember it.

Why it works: zero new tools, one searchable place, and posting there is a public act, which makes decisions feel decided.

Where it breaks: the channel depends on the decision-maker remembering to cross-post, in the right format, while busy. Compliance decays exactly like a manual decision log, because that is what it is. It also captures no reasoning beyond what fits in one message, and Slack's own retention settings may eventually eat the linked threads.

Option 2: pinned decision digests per channel

Each working channel maintains one pinned message (or canvas) listing the decisions made in that channel: one line each, newest on top. The channel owner updates it weekly.

Why it works: the record lives next to the context, and pins survive the scroll. For a project channel with a competent owner, this is often enough.

Where it breaks: it fragments the archive (there is no single place to search across channels), it still depends on a human editor, and it records outcomes without reasoning, which is the part people actually come back for. Teams that outgrow this usually notice the same debate being re-run in a different channel, unaware there was a ruling; we wrote about that failure mode in why teams relitigate decisions.

Option 3: capture the decision from the conversation itself

The third approach removes the re-typing step entirely: tooling that turns the Slack conversation into the decision record. Disclosure: this is what Withose does, and Withose publishes this blog, so weigh this section accordingly.

The mechanics matter more than the brand. In Slack you type /withose in the channel where the discussion happened, or right-click a message and use the message action. AI drafts the record from the conversation: the question, the options, and where each participant stands. People whose position is missing get asked, by email link, no account needed. The finalized record lands in a searchable archive that new decisions are checked against for contradictions. The conversation itself never moves; nobody changes how they talk.

Where it breaks: it is a paid product beyond the free plan, and it is deliberately explicit-capture, so a decision nobody thinks to capture still escapes. No tool fixes a team that does not want a record. You can judge the flow yourself in the playground, which runs it on sample data without an account.

What every decision record needs, whichever option you pick

The format of a decision record outlives the mechanism. Whether the record is a channel message, a pinned line, or a captured card, it needs the same five things: the question, the decision in one unhedged sentence, the date, the people (including who disagreed), and the reasoning. We keep a free decision log template with exactly those fields if you want the manual version.

And if your company runs on Microsoft Teams rather than Slack, all three options translate directly; only the capture triggers differ, which we cover in how to document decisions in Microsoft Teams.

And one rule of thumb for the whole system: if writing the record costs the author more than two minutes, it will not survive a busy week. Optimize for the author, not the archive; an imperfect record that exists beats a perfect one that does not.