Add a note about making a non-technical thread for critical support issues about readme HOT 7 CLOSED

@joeyAghion and I have a follow-up for the Jira ops exploration that we did-- maybe we can aim to get that out early this week. I think it would remove the need for this.

from readme.

I like this, one thread can be noisy: everyone's getting notifications, engineers are possibly using it for dev communications (although sometimes that goes off into a more relevant channel to be worked on), and stakeholders want updates.

Great idea!

from readme.

This sentiment is spot on-- it's been hard to separate setting expectations for stakeholders from actual debugging.

I'm not sure if the short or long-term solution is a separate thread or something more "meaty".

Maybe @joeyAghion and I can explore this on Friday during our "Jira Ops" future friday experiment (and follow-up here!).

from readme.

(:ceiling-cat: Any follow-up?)

from readme.

Sounds exciting!

from readme.

@orta since I believe this is solved by the new suggestion to keep the #incidents thread client-facing and take engineering discussion to a separate channel, are we good to close?

from readme.

Yep

from readme.