Skip to content

Document feedback classifications for Manage

Michelle Gill requested to merge m_gill-master-patch-49839 into master

Why is this change being made?

This chart will provide a way to classify certain types of feedback given during more informal scenarios, such as inside agenda docs or slack messages.

The MR itself explains the "why" behind classifying feedback, this addition to the handbook just makes it more transparent for those of us who already use this method (me)

It can be hard to understand how you're doing in your role, because feedback can come off as formal (annual reviews, 360 surveys, career development conversations, goal check-ins) or casual (in Slack channels, 1-1's, MR reviews, team meetings.) We receive various kinds of feedback regularly and through different formats, so the type of feedback you're receiving is not always clear. In order to be more intentional about the types of feedback given, here is a classification chart based on three types of feedback:

I have also nested this under a "Career Development" section. In the future, I'd like to be more transparent with both IC's and EM's about how career development works for them. This will need to be a collaborative effort according to how EMs currently do career development today for the IC's + how I will be doing career development for the EMs.

Author Checklist

  • Provided a concise title for the 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.
  • Assign reviewers for this change to the correct DRI(s)
    • 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 in 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.
  • 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.

Merge request reports