Draft: Gathering feedback as a manager on team members

Goal

With removing open testimonials from promotion documents we want to make sure to give guidance to managers on how/when/if they can gather feedback on the knowledge, skills and abilities of their team member.

Draft Proposal

• Managers can ask feedback in a 1-1 setting with peers/collaborating team members/other leaders on an ongoing basis (not a single points in time). This can help with assessing knowledge, skills and abilities for the next level role.
• There would not be a mention of the promotion or timeline - however there's room to ask about knowledge, skills and abilities to acquire for the next level.
• The feedback gathered over time which is not public would not be documented in the promotion document.
• This Draft would be ensuring we align with [point 7. from the Not Public page(https://about.gitlab.com/handbook/communication/#not-public), ensuring privacy and moving to 1-1 setting.

The above is open for further iteration and is subject to Legal review to ensure team member's privacy.

MR of first iteration

!56692 (merged)

Legal framework which this should align with:

!56692 (comment 390908789) !56692 (comment 391428215)

@brentnewton @rnienaber @marin @andrewn For your review.

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][transparency]
• Assign this change to the correct DRI
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to your manager.
  • 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][mr-buddies-slack].
  • If the changes relate to any part of the project other than updates to content and/or data files please make sure to ping @gl-static-site-editor in a comment for a review and merge. For example changes to .gitlab-ci.yml, JavaScript/CSS/Ruby code or the layout files.