Add some examples for things a SSC can do
Why is this change being made?
In the past months, I've stumbled into all kinds of things as part of my SSC role. I've also learned that I'm not the only one who struggles with properly defining what the role means, and how I can be helpful. I mentioned most of these things on the Slack channel as they happened, and we've discussed some of it in the Support Stable Counterpart Office Hours. However, the most important place to put these examples is the HB, especially with links to examples – nothing helped me find my footing more than seeing what others actually do.
@gitlab-com/support/support-stable-counterparts Let me know what you think!
Some notes:
- Rough draft. Happy to make a whole subsection with more details for each bullet point, but bias for action!
- In Adds SME review to SSCs (!113273 - merged) we're adding a whole section for a similar example. I think either that should become a bullet point in this list, or everything should become a whole section. @lyle, thoughts?
- Pleeease add more examples if you have. This really is not meant to be the big Manu show.
😅 But for me personally seeing something tangible is super valueable as opposed to a list of theoretical things. - Regarding the customer outreach thing I plan to also change the corresponding process/HB page to make it official that a group should default to their SSC instead of the CMOC in non-urgent cases. I think this makes much, much more sense. Will follow up with an STM issue shortly.
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- The when to get approval handbook section explains the workflow in more detail
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Manuel Grabowski