Remove CAB references from product handbook pages

The Product Manager is responsible for figuring all of this out, but being one step ahead of them will speed things up.

If a customer is a member of our Product [Customer Advisory Board](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/), the CSM should add two labels: `~CAB Takeaway` and `~CAB Takeaway Qx FY20xx` to the issue.

If a customer participates in [Advisory and Executive customer programs](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/#executive-advisory-board-eab-program), the CSM should add relevant labels to the issue to track their feedback.

It is highly recommended to use the feedback template below to make this easier.

#### Examples

- [Example CAB Presentation](https://docs.google.com/presentation/d/11YI6zj3qMeTwXTmdovuZLEM2i3D-eNMdNXcQgc9coc8/edit#slide=id.g85b09e34a4_0_5)

<br>

<br>

| [Group Manager](/job-families/product/product-management-leadership/) | [Director](/job-families/product/product-management-leadership/)| [Senior Director](/job-families/product/product-management-leadership/) | [VP](/job-families/product/product-management-leadership/) |

| --- | --- | --- | --- |

| Leads strategic research that spans and extends beyond product scope. Plans on an annual and quarterly product vision cadence. Spots opportunities for cross-group, cross-stage, or cross-section collaboration and learning. Demonstrates and coaches business skills to others. Regularly maintains high-level Direction and ensures Direction alignment across the scope. Develops a deep understanding of the adoption funnel across groups and stages. | Executes research and customer interviewing across the section as a GitLab representative. Plans on a 3-year to annual product vision cycle. Creates opportunities for cross-stage and cross-section collaboration. Active coach for business skills across the product organization, including feedback on opportunity canvases, product proposals, and MVCs. | Represents GitLab product in strategic customer calls, Customer Advisory Board Sessions, and prospects to inform 5-year+ product vision and strategy. Contributes to annual themes, yearlies, and OKRs to align section with broader company strategy. Provides coaching to direct reports on crafting vision in respective areas. |  |

| Leads strategic research that spans and extends beyond product scope. Plans on an annual and quarterly product vision cadence. Spots opportunities for cross-group, cross-stage, or cross-section collaboration and learning. Demonstrates and coaches business skills to others. Regularly maintains high-level Direction and ensures Direction alignment across the scope. Develops a deep understanding of the adoption funnel across groups and stages. | Executes research and customer interviewing across the section as a GitLab representative. Plans on a 3-year to annual product vision cycle. Creates opportunities for cross-stage and cross-section collaboration. Active coach for business skills across the product organization, including feedback on opportunity canvases, product proposals, and MVCs. | Represents GitLab product in strategic customer calls, [Advisory and Executive customer programs](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/#executive-advisory-board-eab-program), and prospects to inform 5-year+ product vision and strategy. Contributes to annual themes, yearlies, and OKRs to align section with broader company strategy. Provides coaching to direct reports on crafting vision in respective areas. |  |

### Sensing Mechanisms

- Engage with users in epics, issues, and merge requests on GitLab.com.

- [Meet with customers directly.](#customer-meetings)

- Participate in the [CAB](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/).

- Participate in [Advisory and Executive customer programs](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/#executive-advisory-board-eab-program).

- Talk with GitLab team-members using GitLab.

- Talk with other PMs and [Product leadership](/handbook/product/product-leaders/product-leadership/) to align your stage's product direction with the rest of GitLab.

Here is some guidance for new PMs to ensure your stage direction, category strategies and plan

are up-to-date and visible to critical stakeholders:

- Seek feedback from the [CAB](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/) once every six months.

- Seek feedback from [Advisory and Executive customer programs](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/#executive-advisory-board-eab-program) once every six months.

- Present your plan to your manager once a month.

- Present the plan and stage/category strategies to your stable counterparts

- Present your stage strategy and plan in a [customer meeting](#customer-meetings) once every two weeks.

you should not try to interview the user on spot, instead organize a separate meeting where nobody will be distracted, and

both of you can arrive prepared.

#### Customer Advisory Board meetings

#### Advisory and Executive customer program meetings

One specific, recurring opportunity to get direct feedback from highly engaged customers

is the [GitLab DevOps Customer Advisory Board](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/).

You may be asked by the CAB to present your stage at these meetings. Here are

is through [Advisory and Executive customer programs](/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/customer-advocacy/#executive-advisory-board-eab-program).

You may be asked to present your stage at these meetings. Here are

some guidelines when doing so:

You may be asked by the CAB to present your stage or a specific product offering at these meetings.  Here are some guidelines for presenting:

You may be asked to present your stage or a specific product offering at these meetings.  Here are some guidelines for presenting:

1. Product Focused Highlights: All presentation materials should be focused on products we plan to launch or evaluating products we have available to customers.

1. Prepare Targeted Questions: Develop 2-3 specific, through provoking questions to engage members in conversation. These questions should be focused on presentation, strategic decisions GitLab is currently grappling in your stage that you would like to gather customer feedback on, or a question related directly to customer workflows.

1. Connect to Previous Feedback: Reference previous feedback you have received from advisory meetings in the past. This will help illustrate to CAB members the value of their time and that GitLab takes their recommendations into consideration.

1. Connect to Previous Feedback: Reference previous feedback you have received from advisory meetings in the past. This will help illustrate to program members the value of their time and that GitLab takes their recommendations into consideration.

1. Prompt Follow Through: Document key insights and actions items during your session.

1. Be Prepared: Be sure to prepare for the meeting ahead of time independently.

Please review [GitLab Product Customer Advisory Board Page](/handbook/product/product-processes/customer-advisory-board/) for more details.

#### Working with (customer) feature proposals

When someone requests a particular feature, it is the duty of the PM to investigate

- Category Strategy updates

- Direction page updates

- Analyst engagements

- CAB presentations

- Advisory and Executive customer program presentations

### Build vs "Buy"