Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 106

Adding product marketing Tiers to the Product section. (#10128)

Browse source 
Co-authored-by: Mo Zhu <mo@fleetdm.com>
Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
This commit is contained in:
Jarod Reyes 2023-02-28 17:12:23 -08:00 committed by GitHub
parent 2a11e88f3a
commit 39d337c4df
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 4 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

14
handbook/product/README.md
View file

@ -253,7 +253,7 @@ There are two types of tooltips. The two types of tooltips have some unique styl
## Release
This section outlines the communication between the product team, growth team, product team,
This section outlines the communication between the product team, marketing team, product team,
and customer success team prior to a release of Fleet.
### Goal
@ -261,13 +261,20 @@ and customer success team prior to a release of Fleet.
Keep the business up to date with improvements and changes to the Fleet product so that all stakeholders can communicate
with customers and users.
### Product marketing tiers
After the kickoff of a product sprint, the marketing and product teams should decide which features are most important to highlight. When a feature gets scheduled for release the Tier helps marketing give it the biggest impact. Once the features have been discussed the next step is to bucket them into tiers for marketing prioritization. The current tiers are 1-3.
- Tier 1: A separate product feature announcement. The most important release types, these require a specific and custom marketing package. Usually including an individual blog post, a demo video and potentially a press release or official product marketing launch. Due to limited availability there is only room for one Tier 1 product announcement per release sprint.
- Tier 2: A highlighted feature in the release notes. This product feature will be highlighted at the top of the Sprint Release blog post. Depending on the feature specifics this will include: a 1-2 paragraph write-up of the feature, a demo video (if applicable) and a link to the docs. Ideally there would be no more than 3 *Tier 2* features in a release post, otherwise the top features will be crowded.
- Tier 3: A feature worth mentioning in the changelog. In most cases a product feature will fit into this Tier. This includes 1-2 sentences in the Changelog and release blog post.
### Blog post
The product team is responsible for providing the [growth team](../growth/README.md) with the necessary information for writing
The product team is responsible for providing the [marketing team](../marketing/README.md) with the necessary information for writing
the release blog post. This is accomplished by filing a release blog post issue and adding
the issue to the growth board on GitHub.
The release blog post issue includes a list of the primary features included in the upcoming
The release blog post issue includes a list of the primary *Tier 2/3* features included in the upcoming
release. This list of features should point the reader to the GitHub issue that explains each
feature in more detail.
@ -279,7 +286,6 @@ The product team is responsible for providing the [customer success team](../cus
for writing a release customer announcement. This is accomplished by filing a release customer announcement issue and adding
the issue to the customer success board on GitHub.
The release blog post issue is filed in the private fleetdm/confidential repository because the
comment section may contain private information about Fleet's customers.