Team War Room vs. running it in a Slack thread
Every team runs its first three incidents in a thread. The fourth one is when someone asks what happened in March and nobody can find it.
Feature by feature
| Factor | Team War Room | A Slack thread |
|---|---|---|
| Severity | Tiered 1-5 on the same scale every time. | Whatever the loudest person in the thread felt. |
| Ownership | Named owner and roster per incident. | Implied, contested, occasionally nobody. |
| History | A searchable feed you can point at in a review. | Scrollback, until retention eats it. |
| Postmortem | AI blameless postmortem generated from the incident record, exportable as markdown. | Someone volunteers, then doesn't. |
| Access | Sign-in required, scoped to your team. | Whoever wandered into the channel. |
Which to pick
Pick A Slack thread
It's you, it's small, and it'll be over in an hour.
The verdict
Keep talking in Slack. Keep the record in the War Room, so the pattern is visible before it becomes a quarterly theme.
Questions people ask
- Do I need a team to use CYABot?
- No. Every solo tool works signed out. The War Room is the only part that requires sign-in, because it's shared.
- Who can see War Room incidents?
- Only members of that team. Access is enforced server-side per team, not by an unlisted link.