Skip to content

Product handbook content re-organization

Keanon O'Keefe requested to merge product-handbook-info-reorg into master

Why is this change being made?

This MR closes Product#857 (closed) I am re-orging the Product Handbook to be more consumable for new PMs and others at GitLab. We have collected data via direct feedback from PMs over the past 6 months as well as distributed a Product Handbook specific survey (referenced below) to inform the re-org of this content.

This MR does not make any significant changes to content (written copy re processes, etc). It is focused on content organization and accessibility.

From issue 857: Currently, the product handbook as a wealth of information, some of which is not bucketed into the most appropriate categories related to job tasks (such at product development flow) or highlighted based on importances for gitlab (such as Dogfooding). This results in PMs either not finding or not being aware of certain helpful process and recommendations that would help them perform their job at Gitlab. And the amount of content on the various pages generally feels overwhelming, for any audience.

The core audience for the Product Handbook is Gitlab PMs. When PMs reference the handbook, they need clear visual organization and hierarchy of content to facilitate both discoverability and navigability of topics/processes that are most relevant to the tasks they need to complete to successfully perform their job.

Notes & References:

Survey: https://forms.gle/YpArPrTCxZsegLiN6

Main Updates are new pages and a reorg on informations in the product handbook within them for easier discoverability and understanding:

Product Principles

The Product Principles section is where you can learn about our strategy and philosophy regarding product development here at GitLab.

Product Processes

For a detailed view on how we do Product Development, read up on our established Product Processes.

Product Categorization

To learn how the GitLab product and our Teams are organized review our Product Categorization section.

About the GitLab Product

Learn about GitLab as a product, including what does it mean to be a single application, our subscription tiers and pricing model, and the basics of permissions in the platform.

Being a Product Manager at GitLab

Want to know more on what being a Product Manager at GitLab is like? Checkout our Product Manager Role guide for helpful information like our Career Development Framework and the Roles and Responsibilities of a PM.

Our Product Leadership Team

Learn about our Product Leadership Team and learn about them via their persoanl READ Me’s.

REVIEW APP https://product-handbook-info-reorg.about.gitlab-review.app/handbook/product/index.html

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.
Edited by Farnoosh Seifoddini

Merge request reports