How to use “Battle Stations” channels for better response during and after an outage.

How to use “Battle Stations” channels for better response during and after an outage:
After my Server Fire Fighting Pro Tip 1 - Bread Crumbs post another skilled server fire fighter, Karl Schmidt, reached out to me to share their insight:
Similar to the Google Doc approach, I have a dedicated “battle stations” slack channel where >the team (well, usually one person is designated to do the writing) “thinks out loud” and writes >out what they are going to do, how it went, next thing, etc into the channel. Then the transcript >can be reviewed in the post-mortem meeting afterwards. I absolutely agree. When fire fighting asynchronously I have found chat threads to be a powerful tool. Most of my clients have some form of automated CloudWatch Alarms that pipe their emergency alerts into chat. From there we just start a thread on any ongoing issue that pops up. So thank you Karl for the pro tip.
Question: Do you have your own form of a “Battle Station” channel? If so, what does that process look like?