When Slack decisions never become docs

The team settles a billing architecture question in #eng on a Thursday afternoon. Finance and eng agree on EU routing through Stripe. Someone reacts with a checkmark emoji. The thread scrolls away.

Six months later, a new hire asks the same question. Slack search finds the thread. It also finds four other threads about payment providers, two side conversations in DMs that never got summarized, and a GitHub issue that captured the workaround but not the constraint finance insisted on.

The thread exists. The decision does not, not in any form a new hire can use without reading 200 messages and guessing which reply was the call.

Why Slack search is not enough

Enterprise search and native Slack search are good at finding text. They are bad at telling you which message was the decision, who had authority to make it, and whether it still applies.

Search returns relevance-ranked chunks. It does not return "this is the current EU payment routing call, confirmed by the person who signed off, with high confidence." That requires someone to distill the thread into a decision and confirm it.

Why your wiki doesn't stop Slack pings covers why the wiki never got updated either. The failure mode is the same: documentation was homework, and the decision was already made in chat.

The thread lifecycle

Most Slack decisions follow a recognizable arc.

Someone asks a question. A few people debate constraints. A senior or domain owner makes a call. The thread dies within hours.

Between "call made" and "thread buried" is the capture window. Inside that window, the people who were present still remember what was decided and what was explicitly rejected. Outside it, reconstruction starts. Reconstruction is where errors creep in.

Teams that capture well treat the ten seconds after a thread resolves as part of the workflow, not a separate documentation task.

What capture is not

Capture is not exporting a channel. It is not silently ingesting every message. It is not asking an LLM to summarize #finance and hope nobody gets misquoted.

Ignius surfaces candidates: threads that look like decisions, repeats, or handoff paths. A human confirms what becomes a saved decision. That decision has a summary, a source link back to the specific Slack message, a confidence level, and a context group.

For the full storage policy, see What a company brain captures. For the product overview, see Capture decisions from Slack.

A concrete example

On the Horizon Logistics demo, Operator holds a decision for the EU payment routing call: Stripe for EU, Braintree deprecated, what finance and eng agreed on. The decision links to the Slack thread and the relevant GitHub issue. Ask returns the call and the source, not a paraphrase over every message in #eng.

Without that decision saved, the next person runs Slack search, reads half the thread, and pings the same senior anyway.

When to capture

The best time is right after the thread resolves, while the participants are still in context. The acceptable time is within a day or two, when someone sees the candidate in the capture inbox and recognizes it.

The worst time is a quarterly documentation sprint, when nobody remembers which emoji reaction meant "approved."

Timing is why read-only integration matters. Connect Office, GitHub, and Xero. Ignius watches for decision-shaped threads and surfaces them as drafts. It does not wait for someone to remember to open Confluence.

Groups keep Slack decisions usable

A finance thread about payment routing should not share retrieval space with an eng debate about service boundaries. Context groups scope Ask so a question in Operator does not pull unrelated threads from Portfolios or Partner.

How context groups keep answers scoped explains why one giant Slack archive fails even when search works.

What changes for the person who keeps getting pinged

The goal is not more documentation. The goal is fewer repeat explanations for the person who already answered once.

When a confirmed decision exists, the next asker gets the call with a citation. They can verify the source themselves. The senior stays in the customer call.

That only works if capture feels safe. Human confirm, no silent saves, private groups that stay private until published. If the tool feels like surveillance, nobody confirms candidates and the inbox stays empty.

The test

Pick one question your team answered in Slack twice in the last month. Run Slack search. Can a new hire determine who decided, what was decided, and whether it still applies, in under five minutes?

If not, the team has a capture problem, not a search problem. What is a company brain? describes how Ignius approaches it.

Try the Horizon Logistics demo to see the capture inbox and Ask with citations on sample Slack-sourced decisions.