-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a note about making a non-technical thread for critical support issues #63
Comments
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! |
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!). |
(:ceiling-cat: Any follow-up?) |
@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. |
Sounds exciting! |
@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? |
Yep |
Example: Technical thread - Non-technical thread
What do you think @sweir27 ?
The text was updated successfully, but these errors were encountered: