Skip to content
Snippets Groups Projects
Commit 7ddd6e8d authored by Eric Brinkman's avatar Eric Brinkman
Browse files

Merge branch 'phikai-producthandbook-categoryvision' into 'master' 

Product Handbook Updates to Move Category Visions out of Epics

See merge request gitlab-com/www-gitlab-com!23059
parents 410893a9 27250eda
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/templates/product/category_vision_template.html.md 0 → 100644
+ 70
− 0
View file @ 7ddd6e8d
---
layout: markdown_page
title: "Category Vision - <STAGE-NAME>"
---
- TOC
{:toc}
## <STAGE-NAME>
| | |
| --- | --- |
| Stage | [<STAGE-NAME>](/direction/<STAGE-NAME>/) |
| Maturity | [<MATURITY-LEVEL>](/handbook/product/categories/maturity/) |
### Introduction and how you can help
<!-- Introduce yourself and the category. Use this as an opportunity to point users to the right places for contributing and collaborating with you as the PM -->
<!--
<EXAMPLE>
Thanks for visiting this category page on Snippets in GitLab. This page belongs to the [Editor](/handbook/product/categories/#editor-group) group of the Create stage and is maintained by <PM NAME>([E-Mail](mailto:<EMAIL@gitlab.com>) [Twitter](https://twitter.com/<TWITTER>)).
This vision is a work in progress, and everyone can contribute:
- Please comment and contribute in the linked [issues](https://gitlab.com/groups/gitlab-org/-/issues?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=snippets) and [epics]((https://gitlab.com/groups/gitlab-org/-/epics?label_name[]=snippets) on this page. Sharing your feedback directly on GitLab.com is the best way to contribute to our vision.
- Please share feedback directly via email, Twitter, or on a video call. If you're a GitLab user and have direct knowledge of your need for snippets, we'd especially love to hear from you.
</EXAMPLE>
-->
### Overview
<!-- A good description of what your category is. If there are
special considerations for your strategy or how you plan to prioritize, the
description is a great place to include it. Please include use cases, personas,
and user journeys into this section. -->
### Target Audience and Experience
<!-- An overview of the personas (https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#user-personas) involved in this category. An overview
of the evolving user journeys as the category progresses through minimal,
viable, complete and lovable maturity levels.-->
### What's Next & Why
<!-- This is almost always sourced from the following sections, which describe top
priorities for a few stakeholders. This section must provide a link to an issue
or [epic](https://about.gitlab.com/handbook/product/#epics-for-a-single-iteration) for the MVC or first/next iteration in the category.-->
### Competitive Landscape
<!-- The top two or three competitors, and what the next one or two items we should
work on to displace the competitor at customers, ideally discovered through
[customer meetings](https://about.gitlab.com/handbook/product/#customer-meetings). We’re not aiming for feature parity with competitors, and we’re not just looking at the features competitors talk
about, but we’re talking with customers about what they actually use, and
ultimately what they need.-->
### Analyst Landscape
<!-- What analysts and/or thought leaders in the space talking about, what are one or two issues
that will help us stay relevant from their perspective.-->
### Top Customer Success/Sales issue(s)
<!-- These can be sourced from the CS/Sales top issue labels when available, internal
surveys, or from your conversations with them.-->
### Top user issue(s)
<!-- This is probably the top popular issue from the category (i.e. the one with the most
thumbs-up), but you may have a different item coming out of customer calls.-->
### Top internal customer issue(s)
<!-- These are sourced from internal customers wanting to [dogfood](https://about.gitlab.com/handbook/product/#dogfood-everything)
the product.-->
### Top Vision Item(s)
<!-- What's the most important thing to move your vision forward?-->
\ No newline at end of file
source/handbook/product/index.html.md
+ 20
− 75
View file @ 7ddd6e8d
@@ -1191,7 +1191,7 @@ When the categories change, we should:
1. Update `categories.yml` and `stages.yml`, ensure all categories are assigned to a Group
1. If two categories are merging, apply the new category label to issues from both of the old categories
1. If a new category is being added, create a new category label and apply it to relevant issues
1. Update category epics to reflect the new labels and categories
1. Update category vision to reflect the new labels and categories
1. Review the handbook and other material which may link to old categories
1. Remove old category labels
 
@@ -1246,88 +1246,37 @@ becomes an enticing part of a greater whole.
 
The vision for the stage should also include:
1. A list of categories within your stage with a brief description and link to the
[category vision epic](#category-vision).
[category vision](#category-vision).
1. A link to a YouTube video recording of you presenting your vision updated in
the last three months.
 
#### Category vision
 
Create and groom epics for each of the categories within your group. When creating
these epics, it's important to focus your time and attention on specific actions and future
iterations. It's natural to want to spend significant effort predicting the future,
but [iteration is one of our primary values](https://about.gitlab.com/handbook/values/#iteration) and
that applies to category visions as well. Your category visions should contain short paragraphs with lots of references
to specific issues. [Here](https://gitlab.com/groups/gitlab-org/-/epics/531) is an example. While
we cannot create epic templates, below is the markdown template to use for category
vision epics:
* Define the [personas](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas#user-personas) related to the problem space by populating the target audience section in the issue or epic description and by labeling accordingly with the [following labels](https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A). That way everyone is aware for whom we are developing and is able to discover related problems/features.
```
Category Label: ~"ADJUST LABEL" | [ADJUST - Issue List]() | [ADJUST - Overall Vision]() | [ADJUST - Other Links]()
## Description
<!-- A good description of what your category is. If there are
special considerations for your strategy or how you plan to prioritize, the
description is a great place to include it. Please include usecases, personas,
and user journeys into this section. -->
## Target audience and experience
<!-- An overview of the personas involved in this category. An overview
of the evolving user journeys as the category progresses through minimal,
viable, complete and lovable maturity levels.-->
## What's next & why
<!-- This is almost always sourced from the following sections, which describe top
priorities for a few stakeholders. This section must provide a link to an issue
or [epic](https://about.gitlab.com/handbook/product/#epics-for-a-single-iteration) for the MVC or first/next iteration in
the category.-->
## Competitive landscape
<!-- The top two or three competitors, and what the next one or two items we should
work on to displace the competitor at customers, ideally discovered through
[customer meetings](https://about.gitlab.com/handbook/product/#customer-meetings). We’re not aiming for feature parity
with competitors, and we’re not just looking at the features competitors talk
about, but we’re talking with customers about what they actually use, and
ultimately what they need.-->
## Analyst landscape
<!-- What analysts and/or thought leaders in the space talking about, what are one or two issues
that will help us stay relevant from their perspective.-->
## Top Customer Success/Sales issue(s)
<!-- These can be sourced from the CS/Sales top issue labels when available, internal
surveys, or from your conversations with them.-->
## Top user issue(s)
<!-- This is probably the top popular issue from the category (i.e. the one with the most
thumbs-up), but you may have a different item coming out of customer calls.-->
## Top internal customer issue(s)
<!-- These are sourced from internal customers wanting to [dogfood](https://about.gitlab.com/handbook/product/#dogfood-everything)
the product.-->
## Top Vision Item(s)
<!-- What's the most important thing to move your vision forward?-->
```
In order to filter and recognize these epics more easily, you can label them with
`product category`, the [Team label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md#team-labels),
the [Stage label](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/contributing/issue_workflow.md#stage-labels),
and the label for the given category (e.g., `sast`).
A category vision is required for each category and outlines various information about
the category including vision, what's next, and competitive landscape. The category vision
should be documented in a category vision handbook page, which allows for version control
of the category vision as well as the ability to embed video assets. One of the most important
pieces of information to include in the category vision is a tangible next step or MVC
in order to push the category up the category maturity curve.
When creating a category vision, it's important to focus your time and attention on specific actions and future iterations. It's natural to want to spend significant effort predicting the future,
but [iteration is one of our primary values](https://about.gitlab.com/handbook/values/#iteration).
Your category visions should contain short paragraphs with lots of references to specific issues. [Here](/direction/release/release_orchestration/) is an example.
We use this [category vision template](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/templates/product/category_vision_template.html.md) as the outline for creating the handbook pages. If additional headings are needed
you are empowered to create and populate them in your category vision.
 
You must keep these categories in sync with `categories.yml` and for
new categories, link to the category epic from the `alt_link` in
`categories.yml`. Adding the category epic as the `alt_link` will automatically
new categories, link to the category vision from the `alt_link` in
`categories.yml`. Adding the category vision as the `alt_link` will automatically
create links in the [home page](/) and the [categories page](/handbook/product/categories/)
so people have an understanding of what each new category really means.
 
Of course for categories that have already shipped, and that have a marketing
product page, `categories.yml` should link to the product page, and the product
page should then have a link to the category epic (you can see an example for
page should then have a link to the category vision (you can see an example for
GitLab Pages with a Vision button [here](/product/pages/)). You should also, of
course, link to your category epics from your [stage vision](#stage-vision)
course, link to your category vision from your [stage vision](#stage-vision)
page.
 
It's okay if your vision changes over time. Ideally, what you'll change are
@@ -2158,10 +2107,6 @@ easily. Also, after distilling things down to a first iteration, you might
realize it’s a lot easier than you thought, and prioritize it earlier. You can
have an MVC without a Vision. But **you can't have a Vision without an MVC**.
 
##### Epics for a category vision
See [category vision](#category-vision).
#### Product Discovery Issues
 
When a product discovery step is needed to design a feature, PMs should
@@ -2253,7 +2198,7 @@ Some discouraged responsibilities:
 
- Long-term MVC definition
- Roadmap beyond 3 months
- Category Epic updates
- Category Vision updates
- Direction page updates
- Analyst engagements
- CAB presentations
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment