Added feedback session for first Severity 1 or 2 incident for an Incident Manager
Why is this change being made?
!93997 (closed) was raised a year ago to address this concern but never merged and is now more time consuming to resolve the conflict than to have a new MR.
The expansion of the Incident Manager to many more team members has provided many new ideas of how to best improve onboarding and learning. Thanks to @dsatcher for the idea of a feedback session after the first significant incident that an IM is involved in.
This is proposed to be added to the responsibilities list. It could be handled in the onboarding tasks or handbook page, but there is likely (and hopefully) a larger span of time in between onboarding and a severe incident, complicating the closure of the onboarding effort.
/cc: @mksionek @cheryl.li as you've been helping lots recently with this process.
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.