The Incident Channel Discipline

One channel per incident. The discipline that prevents the parallel-channel sprawl that loses information.

The rule

One dedicated channel per incident, all active discussion in that channel, subordinate channels link back. Without the rule, conversation splits across vendor-investigation channels, team channels, and DMs, and the postmortem author cannot reconstruct what happened.

• One dedicated channel per incident. Named Slack channel per incident (e.g. #inc-2026-05-04-checkout). All active discussion lives there.
• Subordinate channels link back. Cross-link from #datadog-investigation, #db-team, etc. into the main channel. Side investigations stay visible.
• Named scribe per incident. Timeline keeper assigned at the start. Postmortem reconstruction has the breadcrumbs it needs.
• IC announcement pinned. "I am IC" pin per incident. Catches dual-IC confusion before it costs minutes.

Why

The single channel pays back at postmortem time and at every late-joiner moment. One source of truth, one scrollback to read, structured prefixes that make filtering possible. Without it, every postmortem starts with "let me piece together what happened from five Slack channels."

• Searchable single source. One-channel scrollback per incident. Postmortem authors find what was discussed in one place.
• Late joiners read once. Unified history per incident. New responders read scrollback once, not five times across channels.
• Indexed cross-incident archive. Org-wide channel history. Supports cross-incident pattern recognition over the year.
• Structured prefixes per update. DECISION:, STATUS:, QUESTION: tags. Supports later filtering and timeline reconstruction.

When NOT to follow

Two cases require separate channels. Sensitive discussions (HR, interpersonal) belong in a private side-channel with the outcome posted to main; customer-impact comms requiring legal review get drafted privately and posted publicly only after sign-off. Both cases close with a summary back to the main channel.

• Sensitive discussions. Private side-channel for HR or interpersonal issues. Outcomes posted to main.
• Customer-impact legal review. Legal-review channel for public statements. Drafted privately, posted publicly only after sign-off.
• Documented purpose per side-channel. Named scope per side-channel. Catches "we accidentally split the conversation."
• Post-incident summary to main. Closing recap from each side-channel back to the main incident channel. Catches information left behind.