<commit_before>---
layout: markdown_page
title: "Product Manager Responsibilities and Tasks"
---

## Development direction

- Manage CE / EE / CI features: make sure a release is more than bug fixes
- Manage customer requests: take load of support for handling this and making sure we deliver
- Create direction in development efforts: Making sure that our long term goals are closer with each release
- Make sure other products (license, version) are not snowed under with the release

## Bridge development - sales - marketing

- Give demos to customers
- Make sure marketing puts out correct information
- Shield development from sales and vice versa: be a first responder to questions to the other side
- answer feature questions on social media (twitter, stack overflow,

## Public information

- Guard the quality of any public materials, such as documentation and tweets
mailinglist)
- keep the feature request tracker up to date
- make sure developers write good docs for every function
- make sure the CE/EE comparison, GitHub comparison and battlecards
are up to date
- ensure that answers to internal questions end up being documented publicly
- Make /direction more of a high level roadmap (can link to public issues now)
- Move most of the issues from dev to .com (so our internal roadmap is public)

## Customer relations

- join customer visits if they can lead to new features
- join partner visits if they can lead to new features
- make sure the demo scripts are up to date and train people
- Move feature forum to GitLab issues (once [award emoji](https://dev.gitlab.org/gitlab/gitlabhq/issues/2388) is out)

## Marketing

- make sure the release announcements are well written and cover everything
- do regular feature highlights
- ensure sales has proper marketing materials for our features<commit_msg>update with suggestions from sytse<commit_after>---
layout: markdown_page
title: "Product Manager Responsibilities and Tasks"
---

## Development direction

- Manage CE / EE / CI features: make sure a release contains attractive new features.
- Manage customer requests: take load of support for handling this and making sure we deliver
- Create direction in development efforts: Making sure that our long term goals are closer with each release
- Make sure other products (license, version) are not snowed under with the release

## Bridge development - sales - marketing

- Handle feature requests from sales
- Answer feature questions on social media (twitter, stack overflow, mailinglist)

## Public information

- Guard the quality of any public materials, such as documentation and tweets
mailinglist)
- keep the feature request tracker up to date
- Make sure developers write good docs for every function
- Make sure the CE/EE comparison, GitHub comparison and battlecards
are up to date
- Ensure that answers to internal questions end up being documented publicly
- Make /direction more of a high level roadmap (can link to public issues now)
- Move most of the issues from dev to .com (so our internal roadmap is public)

## Customer relations

- Join customer visits if they can lead to new features
- Join partner visits if they can lead to new features
- Make sure the demo scripts are up to date and train people
- Move feature forum to GitLab issues (once [award emoji](https://dev.gitlab.org/gitlab/gitlabhq/issues/2388) is out)

## Marketing

- Make sure the release announcements are well written and cover everything
- Do regular feature highlights
- Ensure sales has proper marketing materials for our features
{'fraction_non_alphanumeric': 0.047002533070644524, 'fraction_numerical': 0.002251618350689558, 'mean_word_length': 4.2341678939617085, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2998847', 'n_tokens_mistral': 840, 'n_tokens_neox': 817, 'n_words': 512}