|
|
|
|
|
by pixelmonkey
3417 days ago
|
|
I love your strawman example of the "war room" meeting. On my remote team this has happened 3 or 4 times during production outages. The situation was nearly identical, except for lack of physical server room (we use AWS). Someone wrote an @team message in Flowdock, "Things are broken, we need a war room." Within seconds, people were in a video chat room. Within minutes (or, in one terrible case, hours), the issue was resolved. The way everyone knew it was serious is because we rarely use @team-mentions and rarely call "war rooms". Also, our automated monitoring was firing and triggering pagers in PagerDuty for the on-call engineer, the log of which was also plainly visible to everyone in our Flowdock Inbox. So yes, your example here is a nice one, but a strawman. Remote teams know how to take outages seriously. |
|