Emphasize differences of Senior, Staff, and Principal Product Designer roles

Why is this change being made?

This MR aims to emphasize the differences between Senior and Staff Product Designer roles, while shaping the Principal role in relation to the former.

The stage group assignment for Senior or Staff does not make it easier for them to exemplify certain responsibilities (like mentoring). Also, with the current setup, a Staff differentiates on level of expertise, not scope nor level of influence.

Among changes to responsibilities of those roles:

1. Add a one-liner at the top of each role to describe it concisely and emphasize what makes it unique.
2. Remove “Mentoring” from the Senior role — to further differentiate Senior from Staff, and set more reasonable expectations.
3. Remove “Craft” from the Staff and Principal roles — ambiguous and covered by other responsibilities.
4. Remove “Design reviews” from Staff and Principal roles — it's the same as Senior, only difference is that we mentioned “subdepartment”, but that equates to “Product Design”, which is redundant.
5. Remove “Impact” from the Principal role — ambiguous and touched on across other responsibilities.
6. Rename “Open processes” to “Operations” in the Principal role — to include more than processes.
7. Add “Supporting others” to the Principal role.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Emphasize differences of Senior, Staff, and Principal Product Designer roles

---