Draft: Question manager scope

Why is this change being made?

Since gitlab is unique in many ways, it seems like now is a good time to re-evaluate this premise. Since the company culture inspires a lot of benefits not seen in the wider tech sector, this commonly-repeated metric deserves some scrutiny.

Now is also a good time since the team growth is stabilizing and newer managers are being trained more on cultural adoption.

With async and handbook-first, it seems like a direct manager would be able to supplement their feedback with expert opinions and input from a company-wise process or team member satisfaction team. This would both help the managers and team member across the board.

Author Checklist

• Correct MR template applied (e.g blog post)
• 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.

For help with failing pipelines reach out in #mr-buddies in Slack

Carol: changed employee -> team member in the description