Skip to content

Adding Communication Best Practices to Performance / Potential Handbook Page

Carolyn Bednarz requested to merge add-communication-best-practices into master

Why is this change being made?

Hi @gl-peoplepartners and @cteskey! As part of the performance / potential project, we crafted some best practices with regards to communicating performance factors. This content should serve as a guide for managers as they communicate the results of the performance / potential matrix to their team members. Communicating of performance factors will start in mid-December after e group approval and compensation team audits and continue through the end of January.

We welcome any feedback or suggestions you may have before we merge this into the handbook. If you can review by next Wednesday, November 18th - that would be great.

Cc - @Josh_Zimmerman I know we also discussed potentially scheduling manager training mid-December to review this content live and answer questions. Would love your review of the content and your thoughts on if that is something we would want to get on calendars.

Thank you!

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
  • 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.
    • 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.
Edited by Carolyn Bednarz

Merge request reports