Principles - Processes - Categorization - GitLab the Product - Being a PM - Performance Indicators - Leadership
As a Product Organization, we work to create a flexible yet concise product development framework for developing products that customers love and value. The Product Principles section is where you can learn about our strategy and philosophy regarding product development, here we discuss the processes we use tactically.
Frequent Topics:
READ-ONLY announcements which require no synchronous discussion and are for information sharing only. If any action is required, this should be highlighted specifically by the reporter.If you are a Product team member and are unable to attend the call, you may add items for READ-ONLY to the agenda.
The EVP of Product and their direct reports track our highest priority Product Team initiatives. If one of those initiatives needs to be discussed synchronously the assigned individual should add it to the meeting's GoogleDoc agenda. Directors can delegate and coordinate cross-product initiatives as needed based on the issues in this board.
As part of this Product Leadership Meeting we also review progress towards our OKRs.
Non-public items for discussion should be added directly to the agenda document for the meeting.
Every week, Product Operations holds office hours to support PMs with any aspect of the GitLab product development process. Attendees discuss and troubleshoot items on the agenda. The goal is to collectively own the GitLab product development framework, continually evolving it into a world-class system by practicing our core GitLab Values.
Some general topics for discussion:
All product investments need to generate a version of ROI, which can be measured in one of two ways.
The principle form of measurement is Incremental Annual Contract Value (IACV), which is the most important metric in the company.
The formula for measuring a feature’s effect on IACV can be: AMAU ÷ AMAU total across all actions * ARR, where AMAU stands for Action Monthly Active Users and ARR stands for Annual Recurring Revenue.
Where a feature is not generating IACV,
we measure its Return on Investment (ROI) through its product usage, as measured by AMAU ÷ SMAU for that stage, where SMAU stands for Stage Monthly Active Users.
Example: I make a new feature, and that action is taken by 1 million users. Across all of GitLab, we have 100 million SMAU and we have 1 billion AMAU; 0.10% of our ARR can be attributed to the feature I made.If you have a lot of usage in a stage, it may generate revenue and we can consider impact to IACV. If we do not have a lot of usage in stage we want to be looking at the users using it as a percentage of users using the stage to drive interest in that stage. The example here is having a feature with a 18,000 AMAU on a 20,000 SMAU stage. If 90% of the stages users are using the feature, we clearly made it more attractive and it will help to grow SMAU over time.
Aligned with the company cadence, Product planning follows:
Inspired by:
Introducing changes requires a number of steps, with some overlap, that should be completed in order.GitLab follows a dual-track product development flow spanning product, engineering, UX, and quality.
This process should be both up front and on an on-going basis when building features.
GitLab is designed and developed in a unique way.
Consistent with our value of Efficiency the product is developed with directly responsible individuals from Product, UX, Quality and Development working together.
| Product Managers | Engineering Managers | UXers | SETs |
|---|---|---|---|
| Set priorities and define what Engineering works on | Own the definition of done; decide what gets merged into Product | Proactively identify small and large strategic UX needs to aid Product Management prioritization | Own and identify test strategy and requirements to complete the definition of done |
PMs are the DRI for what GitLab Engineering team members work on. As a result contributions from the wider community and from other teams in GitLab are not subject to the processes described below nor are they prioritized by GitLab Product Managers. So long as an MR matches the definition of done, changes may make their way into Product.
The product direction is an important part of each PMs work. PMs are expected to maintain the accuracy of their plan throughout the year through stakeholder conversations and other research. Your product direction is displayed as the direction labeled issues for your group's categories which are displayed in the Section, Stage, and Category direction pages of our website.
Around November, we begin the annual planning cycle, which ties closely into the overall strategy. During this period we update the direction label and apply it to issues that have been identified as contributing to the plan that year.
PMs are able to refine their plans and strategy throughout the year, but since the these are important to be aware of, major updates to the content that happen ad-hoc should also be communicated widely - for example, using the Product FGC meetings or other communication channels.
It's important to note here that your plan is not simply a list of new features and innovation. Those are included for sure, but so are issues related to all of your sensing mechanisms.
A category upgrade from minimal to viable or delivery of a top customer issue (for example) can contribute to your plan just as much as a brilliant new innovative feature can. It's up to PMs to balance this through a coherent longer-term strategy.
Conversely, in a broad sense anything could move the plan forward in a general way. Product Direction items (i.e., with the label) should be direction-level items that move the strategy forward meaningfully. This is up to the PM to set the bar for, but there should be a clear step forward with real user value.
Finally, issues are the substance of your plan. Epics can receive the label as well, to keep things organized, but we track the delivery of our plan on a per-issue basis. Ensure you are applying the label appropriately.
In each release, you should be moving your plan forward. At least one item with this label should be included; if not, it's possible you're getting off track from where you planned to go and should assess.
Note that, by their nature, Product Direction items should not be sitting in the backlog or with no milestone. If they are this is a signal that either they are not as important as originally thought, or that something important is not getting due attention.
The purpose of our kickoff is to communicate with our community (both internal and external) a view of what improvements are being planned in the coming release. This can help other GitLab teams, community contributors and customers gain an understanding of what we are prioritizing and excited to deliver in our next iteration.
While kickoffs are commonly used to ensure visibility of work across an internal audience, our connection to a broader community and commitment to transparency means we also serve an external audience.
The process for preparing and presenting group and company wide Kickoff meetings is outlined in our Monthly Kickoff issue template. We create an issue from that template each month to collaborate on that month's Kickoff.
When planning, Product Managers plan to GitLab milestones. Here is the process for creating and maintaining them.
One quarter ahead, the Product Operations team will create all of the necessary milestones for the next quarter:
Step 1: .org
New milestone in the top rightdot release that makes sense.
.0 and further for each release with the .0 release every May.18th to the 17thStep 2: .com
.com mirrors the .org milestones for consistency in Product, Marketing etc.New milestone in the top rightdot release that matches .org.
.0 and further for each release with the .0 release every May.18th to the 17thThe release definitions are maintained by the Engineering Team and we run the end of each Milestone on the 22nd.
#product chat channels for questions that don't seem appropriate for the
issue tracker or more generic chat channels.Before shipping a new or updated feature, you are responsible for championing it, both internally and externally. When something is released, the following teams need to be aware of it as they will all need to do something about it:
You can promote your work in several ways:
Product marketers and managers should be joined at the hip. Just as a feature without documentation should not be considered shipped, benefits of GitLab that we're not actively talking about might as well not exist.
Product marketers rely on product managers to be guided to what is important and high impact. In general, you should:
As a PM you're responsible for making sure changes you've shipped are well represented
throughout GitLab's documentation and marketing materials. This means that on
release, [features.yml][features] is updated, documentation is merged and deployed, and
any existing content is updated where necessary.
It's not acceptable to do this after the release. GitLab is very complex, and features and functions are easily missed, even those that provide significant value to customers (e.g. the many ways you can authenticate with GitLab).
You can recruit the help of the marketing and technical writing team if needed, but it's highly recommended to do small updates yourself. This takes less time and overhead than communicating what needs to be done to someone else.
Major features deserve proper attention from Product and Marketing. With a proper rollout, we'll have ample marketing opportunities and receive more feedback ahead of, during, and after the release.
Here is the ideal rollout schedule. For each step there is an indication for who is responsible for it.
As a PM, you are accountable for adding new features (under your umbrella) to the monthly release post, respecting the guidelines defined in the release posts handbook and its due dates. Be sure to go over all the details.
Every month, a PM will take the leadership of the release post, and will be responsible for delivering it in time.
For every monthly release, there is a blog post announcing features. The blog post should contain everything exciting or disruptive. We want to help people understand exciting features (which are often new), and increase adoption. In general, release posts should succinctly state the problem to solve, the solution, and how customers benefit from the solution.
Some guidelines to help promote consistency of what is included in the blog post between different Product Managers are below.
Depending on the maturity level of your category should influence what you select for as a release post item.
It is recommended to start writing your release post items as a part of your Kickoff preparation. To reduce rework, use the headline of the release post as the issue or epic title. The description of the release post can simply be part of the description of the implementing issue. Writing the release post early and consistently enables you and your team to work backwards and have the following benefits:
As a PM, it is important to remember a bias towards action (and other value actions like sense of urgency, make a proposal, boring solutions, write things down, don't wait, make two way doors decisions and accepting uncertainty which enables PMs to drive an async discussion to being action oriented. Every time you write a comment or create an issue ask yourself: Will this allow us to take an action and move us forward?
As PMs we need to constantly write about the features and upgrades we ship: in a blog post, internally to promote something, and in emails sent to customers. There are some guidelines that one should take into account when writing about features, the most important being a clear communication of the problem we're solving for users.
When writing about a feature, make sure to cover these messaging guidelines which help produce clear internal and external messaging.
Let's highlight the messaging guidelines mentioned above with a concrete example, Preventing Secrets in your repositories, that we shipped in 8.12.
Reduce Security and Compliance Risk).It's a bad idea to commit secrets (such as keys and certificates) to your repositories: they'll be cloned to the machines of anyone that has access to the repository. If just a single one is insecure, the information will be compromised. Unfortunately, it can happen quite easily. You write
git commit -am 'quickfix' && git pushand suddenly you've committed files that were meant to stay local!
GitLab now has a new push rule that will prevent commits with secrets from entering the repository.
Just check the checkbox in the repository settings, under push rules and GitLab will prevent common unsafe files such as .pem and .key from being committed.
Here are some additional examples of well written release blog posts for inspiration:
In addition to the written medium, video is an important medium that caters to the different goals you are trying to accomplish and learning styles of your audience. Depending on the type of video you are recording, there are some guidelines to keep in mind.
As our documentation guidelines actively encourage linking video content, please consider following the Documentation Style Guide section on language, and working with your technical writing team to include links to your speed runs, walk-throughs and demos at relevant locations in the product documentation.
Animated gifs are an awesome way of showing of features that need a little more than just an image, either for marketing purposes or explaining a feature in more detail. Checkout our guide to Making Gifs!
Speed runs are informal videos meant to focus on a single workflow and the experience for performing that workflow. It should not require much planning and is typically short in duration (less than 5 min.). This video type is meant to inform and not necessarily to influence buyers.
Examples:
Demos are scripted recordings meant to influence buyers. Generally has higher production value and typically involves both a slide-style presentation and/or live screen-sharing. Duration varies depending on the topics being covered.
Examples:
Product walk-throughs are informal videos meant primarily for an internal audience as a recorded, visual form of product critique. Walk-throughs typically focus on the user experience across categories and workflows within a Product Manager's product scope. There are particular benefits to walk-throughs which span product hierarchy boundaries (multi-category, multi-stage, multi-section) as they help highlight disjointed experiences across our single-application.
Walk-throughs are typically longer in length as they cover more ground and often involve some "live" troubleshooting and are best performed with no planning. Use the Product walk-through issue template when creating a walk-through.
Examples:
One situation that can happen is that an epic contains many small issues that don't individually
meet the bar for the direction label, and therefore inclusion in the release post. More rarely, the last
issue of an MVC that took several releases isn't necessarily a capstone issue on its own. If you find yourself
in a situation where you have closed an epic during a release, you should also ensure that we communicate that
as a combined entity in a feature block, even if there is otherwise no single issue to mention.
The best way to understand how GitLab works is to use it for as much of your job as possible. Avoid dogfooding antipatterns and try to find ways to leverage GitLab (instead of an external tool) whenever possible. For example: try to use Issues instead of documents or spreadsheets and try to capture conversation in comments instead of Slack threads.
As a PM, but also as any GitLab team member, you should actively use every feature, or at minimum, all the features for which you are responsible. That includes features that are not directly in GitLab's UI but require server configuration.
If you can't understand the documentation, or if you struggle to install something, would anyone else bother to do it? This hands-on experience is not only beneficial for understanding what the pain points are, but it also helps you understand what can be improved and what features GitLab is missing.
When a feature is minimal and moving toward viable, designated GitLab team members (and anyone else interested!) should be using the feature extensively and actively providing feedback to the PM and team developing it.
When a feature is viable and moving toward complete, designated GitLab team members should be using the feature exclusively, and actively providing direct feedback to the PM in situations where exclusive use is not possible.
Exceptions to dogfooding:
When a feature is planned and/or moving towards minimal, dogfooding is not required.
GitLab the company works in a specific way, but GitLab the product is designed to work for lots of different companies and personas. When we have validated through research that the wider GitLab community wants a feature that doesn't align with how our organization works, dogfooding is not required.
As a Product organization, it's also our responsibility to ensure that the entire company dogfoods our product. We do this by:
Working with internal stakeholders comes with the added benefit of getting immediate feedback that reduces cycle times and de-risks early investments in new categories and features. Beyond feature velocity, internal dogfooding saves the money that we would spend on third-party tools.
Internal users can help quickly identify where workflows might break down or where potential usability or performance issues must be explored. We should heavily weigh internal feedback to shape our perspective on customer needs, and then compare it to what we know about both large and small customers (and if we’re unsure, then we should proactively ask).
We define specific DRIs in the categories.yml file. Below are the responsibilities of an Internal Customer DRI:
Dogfooding and spur
a discussion with PM. This label should never be removed so that the
decision-making process gets memorialized on the Dogfooding board.Dogfooding::Build in GitLab when a new feature should be built into GitLabDogfooding::Rebuild in GitLab when there is existing work (outside of GitLab) that needs to be rebuilt inside of GitLabDogfooding::Keep Outside GitLab when a feature is okay to build outside GitLab because they don't align with product visionDogfooding::Use Existing Feature: when a feature already exists, but isn't being used internally yet for whatever reasonDogfooding label when adding the new scoped label.Build in GitLab or Rebuild in GitLab:
Use Existing Feature:
Dogfooding::Promote Feature and promote these features in the weekly Product call and in other relevant channelsDogfooding::Build in GitLab or Dogfooding::Rebuild in GitLab are getting prioritized appropriatelyDogfooding::Keep Outside GitLab to understand why these features are explicitly staying out of the productDogfooding::Use Existing Feature to help their PMs promote these issues for internal usageTo see all the Dogfooding work that is happening, here is a board that collects all the scoped labels.
Check out this 10 minute discussion about dogfooding:
Most of GitLab is configured through the file gitlab.rb. It's tempting to
add a new parameter in this file - it's easy, fast to do, and won't require
adding a new UI element to allow the configuration of this new setting. However,
changing this file requires you to reconfigure GitLab. To do that, you have to
login to your server and type in commands to reconfigure your instance,
possibly multiple times if you have more than one server.
This is not something that we can ask our customers to do. Only by using your own product and features will you realize that some practices should be avoided as much as possible.
There is a certain failure case for MVC issues that product managers need to be aware of and actively work to prevent. Because we don't have infinite capacity to work on everything and good ideas are always coming in, it's possible (if the PM is not watching closely) for issues with good ideas to slowly but inevitably decay into something that is difficult to understand and move forward with.
As more and more comments are added, the issue slowly morphs from idea to idea without any direction from a product manager. Then, it becomes difficult to ever make complete sense of it again without losing some important context. It's also nearly impossible for someone who wants to make a community contribution to understand what the direction is. In other words, it becomes an undefined blob of ideas.
To prevent this, it is the product manager's responsibility to quickly determine whether an open-ended issue aligns with our business model and is broadly useful. If the answer to those questions is "yes," then we must turn it into something actionable, deliverable, and truly MVC as quickly as possible. If the answer is “no,” then we must close the issue to maintain our backlog’s hygiene.
The guidance for product managers is to never let an idea issue persist longer than three months without having been converted into a clear MVC. If this has not happened, you should ask yourself why this is the case: Is the idea overly broad? Is there no clear immediate deliverable? Is it just not important enough to spend time on? These are all signals that should be acted on without delay, before the issue degrades to the point that it becomes unusable without significant rework.
In practice, if the original issue was really broad and still contains great ideas, then simply converting it into an MVC that gets closed when it ships could be a disservice, because you lose valuable context when it's time to improve the MVC. In this case, consider creating a new issue for the MVC, so that it is crisp and concise, and leave the original issue as a post-MVC meta item.
Here are some guidelines to follow when exploring an MVC:
The MVC should be buildable in one iteration.
Virtually every new feature must be maintained forever (the standard for sunsetting a feature is very high). Creating a new feature means that GitLab has to continually manage the costs of maintaining that feature. Making small changes with quick feedback loops reduces the risk of introducing a new feature where the value doesn't justify the long-term costs.
A new feature also adds a tax on the user experience due to additional complexity in the product. Make sure that the benefits gained by users from the new feature more than cover the tax incurred, accounting for how frequently the new feature will be used. In particular, the new feature should satisfy this inequality:
(benefits * frequency) / (tax * (1-frequency)) > 1
Despite its minimal form, the change
After the feature freeze, it's expected of each product manager to test their own features and perform quality assurance to the best of their ability and follow up where necessary.
Product managers can use the staging environment once the release managers have deployed a release candidate to staging. Release managers should post in the #product channel in Slack that a new release candidate is available. Product managers can also use other environments as needed, such as GitLab provisioned on Kubernetes with GKE.
Before a new feature is shipped, the PM should test it out to make sure it solves the original problem effectively. This is not about quality assurance (QA), as developers are responsible for the quality of their code. This is about feature assurance (FA). FA is necessary because sometimes there are misunderstandings between the original issue proposal and the final implementation. Sometimes features don't actually solve the intended problem, even though it seemed like it would, and sometimes solutions just don't feel as useful as intended when actually implemented.
If you can test out the feature during development, pulling down branches locally (or with a review app!), that's great. But sometimes it's not feasible to test a feature until it's bundled into a release candidate and deployed to GitLab.com. If so, make sure to test out features as soon as possible so any new issues can be addressed before final release. Also, take the FA cycle into account when scheduling new milestone work.
If you are looking to test code that has not been merged to GitLab.com or is not yet part of an RC, you can pull the branch down locally and test it using the GitLab Development Kit (GDK).
Product managers should set Milestones for issues marked with the security
label to guarantee they are shipped by their due date, as defined in the
Security Team process.
Product Managers are the DRIs for prioritization.
As such they should deeply understand the implications and risks of security
related issues and balance those when prioritizing.
You may need to set a different milestone for security issues, for example
because of low capacity, but before doing that you should engage a conversation
with the Security Team.
Priority labels and Due Date designations should not be modified by product managers in any case,
since they are directly managed by the Security Team, and used to track metrics and progress.
To enhance availability and performance of GitLab, sometimes it makes sense to add configurable limits to certain features. For example, we limit the number of webhooks per project, and we allow admins to set rate limits on raw endpoints. These limits ensure more consistent performance, reduce the likelihood of outages, and offer admins tools to limit abuse or enforce specific standards.
There is a guide about developing application limits in the GitLab Docs.
If we are considering enabling or changing a limit on GitLab.com, we should do the following:
#customer-success and #support_managers to announce the upcoming change, and consider discussing in the next All CS Team Call to solicit feedback.Each Stage is responsible for building functionality that is core to their value. Even if some components of that functionality happen to cross in to spaces typically owned by other stages, they should still build it (if it's important to them).
If the feature isn't necessary or urgently needed to move forward (for example, it won't block another feature's development), then you can always consider putting it on the backlog of the stage that owns that feature.
Here are some guidelines for thinking about "Which stage should do this work?":
Ecosystem group by default. But again, if the feature is core to a stage's value proposition, they should go ahead and build it themselves.This model allows teams to be flexible and calibrate their priorities accordingly, and no team should ever be "blocked". Exceptions may be items where a change requires anything that a software engineer would not be allowed to do, such as a production change, in which case the infrastructure team would be the blocker.
While any team can contribute features to any stage, it is recommended to loop in the most relevant PM from that Group to provide strategic support to help the contributing team align to the Group's broader plan and vision.
Stages, groups, and categories serve as a common framework for organizing and communicating the scope of GitLab.
Documentation on how to make changes to stages, groups, and categories, as well as what approvals are required, can be found in our website handbook page.
After a change has been approved, we may need to globally optimize during the initial transition period, and ensure that important issues are not blocked.
There are three common scenarios we may encounter during these transition periods:
In each of these scenarios, a Group may become temporarily responsible for a future Group's issues and backlog. During this time, the responsible Group should balance the needs of our users and organization, prioritizing across the common backlog.
As the group(s) working on a Stage grow in size, a new Group may need to be formed so group sizes remain manageable. For example, today
there is a single group for Manage, but will be splitting into control and framework groups.
To prepare for splitting a Stage into multiple Groups, we should:
categories.yml and stages.yml, assigning each Group a set of Categoriesdevops::manageControl or Frameworkdevops::manage backlogOnce the first PM or EM is hired, the new Group should be formed:
Control and Framework. Ideally, each group would have at least two backend engineers, but that is not always possible.stages.yml and team.yml to reflect the current group members. You may need to add a member to the end of _categories.erb.g_control and g_framework, and close the previous Slack channel (e.g. g_manage)As the rest of the EM/PM's are hired, they take over that role for the respective group.
The categories within a Stage will change over time, based on GitLab's direction and the market landscape. The groups within a Stage will need to be able to handle these changes, without issues falling in the cracks.
When the categories change, we should:
categories.yml and stages.yml, ensure all categories are assigned to a GroupWhen GitLab decides to address additional needs within the single application, a new Stage may need to be created. For example, Defend may be created to
address additional needs beyond what Secure focuses on.
When a new Stage is added, and its Group has yet to be formed, we should:
devops::defend and DefendSecure, which will be initially responsible for the new Stagedevops::defend and devops::securecategories.yml and stages.yml, listing the new Stage with the members of the existing responsible Group. Update _categories.erb with the member name if necessary.Once the first PM or EM is hired, a new Group for the Stage should be formed:
Defend. Each Group should have at least two backend engineers.Secure on Secure and Defend on Defend.stages.yml to reflect the new Group and its members. Update _categories.erb with the member name, if necessary.As the rest of the EM/PM's are hired, they take over that role for the new Group.
Throughout the customer lifecycle, customer facing teams (Support, Sales, Professional Services, Account Managers, etc.) may need the assistance of a product manager. This can include a detailed discussion of our direction, how to address specific use cases, or gaps in functionality, with an organization.
To ensure these requests can be quickly triaged, easily scheduled, and later tracked, there is a standardized request process based on issues.
Product support requests are tracked in the Product team project. To create a request:
Product-Support-Request templateFor time sensitive and high impact requests, please paste a link to the issue in the #product Slack channel, and @mention the recommended PM's in the template.
When a support request is opened, labels will automatically be assigned to categorize the request.
Three fields are particularly important when triaging requests:
urgent requests should be treated with a high priority.All product managers should ensure they are set up to receive label notifications for their respective stages:
Each quarter we want to reach out to PNPS responders who opted-in to speak with us. This is a fantastic opportunity to build bridges to users and for product managers to get direct feedback for their specific product area.
Example email copy:
Hello, My name is X and I'm the PM for X at GitLab. Thank you for giving us the opportunity to follow up on your response to our recent survey.
I would be very interested in speaking further about some of the points you raised in your survey response. Would you be willing to do a 30 minute videoconference call to give us some more detailed feedback on your experience using GitLab? You'd be able to schedule the call at a time convenient to you.
Schedule a time for the call using this link: https://calendly.com/yourname/30min
Thank you for your feedback and let me know if you have any questions.
Best, Your name
Copy for two extra questions in Calendly invite:
To make sure we correctly represent what you say in any followup issues or discussions, we would like to record this conversation. Please indicate if you give permission to record this conversation.
Yes, you may record our conversation.
No, you MAY NOT record our conversation.
At GitLab, we value transparency. We would love to share the recording of conversation publicly on GitLab. Please indicate whether you give your permission for the recording to be shared on GitLab.
Yes, you may share the recording publicly on GitLab.
No, you MAY NOT share the recording publicly on GitLab.
If you follow the principles and workflow above, you won't be writing long, detailed specs for a part of the product for next year. So how should you be spending your time?
Invest the majority of your time (say 70%) in deeply understanding the problem. Then spend 10% of your time writing the spec for the first iteration only and handling comments, and use the remaining 20% to work on promoting it.
A problem you understand well should always have a (seemingly) simple or obvious solution. Reduce it to its simplest form (see above) and only ship that.
As a result of this DRIness for prioritization, PMs are reponsible for understanding deeply and prioritizing all types of issues.
Prioritization guidelines:
| Priority | Description | Issue label(s) |
|---|---|---|
| 1* | Security fixes | security |
| 2 | Data-loss prevention | data loss |
| 3* | Availability | availability |
| 4 | Fixing regressions (things that worked before) | regression |
| 5 | Promised to Customers | planning-priority, customer, customer+ |
| 6 | Infra/Dev and Performance Grooming | infradev, performance-refinement |
| 7 | Efficiency Initiatives | |
| 8 | IACV Drivers | |
| 9 | Identified for Dogfooding | Dogfooding::Build in GitLab, Dogfooding::Rebuild in GitLab |
| 10 | Velocity of new features, user experience improvements, technical debt, community contributions, and all other improvements | direction, feature, enhancement, technical debt |
| 11 | Behaviors that yield higher predictability (because this inevitably slows us down) | predictability |
*indicates forced prioritization items with SLAs/SLOs
Please also note the corresponding Engineering handbook section about the relative importance and prioritization of availability, security, and feature velocity. To ensure we're providing an appropriate focus on security, data loss, and availability, PMs should consider:
RICE is a useful framework for prioritization that can help you stack rank your issues. The RICE framework is a great tool for prioritizing many issues that seem to be of equal value at first glance. In order to drive clarity and alignment in the prioritization of work across the entire DevOps platform, and to help prioritize items that may compete for resources from different teams, we have set a standard for the RICE factors so all prioritization decisions based on RICE are using the same metric.
Reach How many customers will benefit in the first quarter after launch? Data sources to estimate this might include qualitative customer interviews, customer requests through Support/CS/Sales, upvotes on issues, surveys, etc.
Higher reach means a higher RICE score:
Impact How much will this impact customers? Impact could take the form of increased revenue, decreased risk, decreased cost, which makes it possible to compare revenue generating opportunities vs. non-revenue generating opportunities.
Higher impact means a higher RICE score:
Confidence How well do we understand the customer problem? How well do we understand the solution and implementation details? Higher confidence means a higher RICE score.
Effort How many person months do we estimate this will take to build? Lower effort means a higher RICE score.
Calculating RICE Score
These four factors can then be used to calculate a RICE score via the formula:
(Reach x Impact x Confidence) / Effort = RICE
Here is an example RICE calculation you can use to help prioritize work in your area. Feel free to embed this at the Epic level to provide context for why you did or did not prioritize.
| RICE Factor | Estimated Value |
|---|---|
| Reach | 1,000 |
| Impact | .5 |
| Confidence | 80% |
| Effort | 2 month |
| Score | (1,000 x .5 x .80) / 2 = 200 |
Other important considerations:
We schedule a prioritized issue by assigning it a milestone; for more on this see Planning a Future Release.
For prioritizing most issues, we should utilize the RICE framework noted above, which will capture an aggregate of customer demand.
In some cases however, we may become aware of a feature which is particularly important to deliver on by a certain date. Examples of this could include an issue necessary to embark on a new GitLab rollout, a feature needed by a partner to launch an integration, or a method to import data from a service which is being discontinued. In these instances, the responsible PM can apply the planning priority label along with a due date and initial milestone. This label can serve to indicate externally that the issue is particularly important, as well as a reminder for internal teams of its importance.
Issues with the planning priority label should be:
It is important to note that the planning priority label does not constitute a promise for the issue to be delivered in any given milestone or timeframe.
GitLab is open-source, and while PMs aren't the arbiters of community contributions, encouraging and promoting a large ecosystem of contributors is critical to our success. When making prioritization decisions, it's important to heavily weight activities which will encourage a stronger community of contributors. Some of those activities are:
Product managers are not responsible for prioritizing contributions outside of their group. These contributions should be reviewed and merged swiftly allowing everyone to contribute, including non-product teams at GitLab.
As a product manager, you will be assigned as the stable counterpart to a single group. At GitLab we abide by unique, and extremely beneficial guidelines when interacting with our groups. These include:
As an all-remote company, our crispness when it comes to responsibilities throughout the Product Delivery process was born out of necessity, but it pays untold dividends. Some of the benefits include:
As the GitLab product matures, we know we must make important workflows easier to use. As part of this effort, the UX department is collaborating with Product Management to select highly used workflows in stable areas of the product. We'll assess and score these workflows using the UX Scorecards methodology and then work together to prioritize recommended improvements.
This effort aligns with the Category Maturity goals that move areas of our product from minimal to viable to complete and, finally, lovable.
As described above, prioritization is a multi-faceted problem. In order to translate the priorities of any given group into action by our engineering teams, we need to be able to translate this multi-faceted problem into a flat list of priorities for at least the next release cycle. Product Managers are responsible for taking all these prioritization considerations and creating a clear, sequenced list of next priorities. This list should be represented as an issue board so that each team has a clear interface for making decisions about work. From this list, UXers, Engineering Managers and Product Managers can work together to determine what items will be selected for work in the immediate future.
This does not mean that items will be addressed in strict order - UXers, EMs and PMs need to be cognizant of dependencies, available skillsets, and the rock/pebbles/sand problem of time management to make the best decisions about selecting work.
Together with your Engineering Manager, you will have an important role in ensuring that the Build Plans defined for issues are created with iteration in mind. Iteration is highly valuable for the following reasons:
As a company we emphasize velocity over predictability. As a product manager this means you focus on prioritizing, not scheduling issues. Your engineering stable counterparts are responsible for velocity and delivery. However, there are instances when there is desire for predictability, including:
As the DRI for prioritization, it is the Product Manager's job to prioritize for predictability when it is needed. You should do so by ensuring you prioritize a deliverable, and its dependencies, so that it can reasonably be expected to be delivered by any committed dates. If there is time pressure to hit a date, the PM should also explore de-scoping the issue to meet the deadline, rather than pressuring engineering to move abnormally fast or cut corners.
Individual product managers must consider, and advocate for global optimizations within the teams they are assigned to. If your assigned team requires expertise (remember everyone can contribute) outside the team you should make all reasonable efforts to proceed forward without the hard dependency while advocating within the product management team for increased prioritization of your now soft dependencies.
If you have a request for additional help within your group, it is your responsibility to advocate for it. It's important to avoid generic "we need another Developer in X group" statements. Instead, create an issue which includes a concrete list of critical issues for no more than the next three months (example).
These issues should all be considered "top priority" and generally fall in one of the following three categories:
Include your proposal for other issues and groups outside of your own which should be considered a lower priority. Once you've reviewed the issue with your assigned Engineering Manager - ping your Product and Engineering Directors for review and refinement. If a global optimization which spans beyond your Department leaders is required, then the Senior Director of Engineering, VP of Product, and VP of Engineering should be pinged.
Please note: this now called a "Headcount Reset" because it shifts team members from one team to another, and can have signficant opportunity costs. Taking people who are familiar with a task and putting them on a new, unfamiliar task instead of new hires (who are also not familiar with the task) is inefficient.
The following exit plan is an initial attempt to spell out when and how the loaned engineers will be released to their original teams. A new hire is expected to be brought up to speed in this context. The plan will be iterated and amended as necessary.
Week 1 is the first week a new hire joins the team.
| Phase | Timeline (recommendation) | What happens | Notes |
|---|---|---|---|
| Onboarding | Week 1 ~ 3 | On-loan engineer works full-time on receiving team to bring up new hire. | New hire's first week priority is onboarding. |
| Collaboration | Week 4 ~ 5 | On-loan engineer works half-time on receiving team while new hire is able to submit MRs of low complexity issues. | On-loan engineer's time may be dedicated completely in pair programming or code review, not necessarily making direct contribution to issues. |
| Handoff | Week 6 ~ 8 | New hire is now the owner. On-loan engineer transitions to a consultant role, reverting back to full-time in original team. |
These information sources may be useful to help you prioritize.
As GitLab grows we will need to create new groups, stages, and categories. During this transition period we need to globally optimize, and ensure that important issues are not blocked during the creation of a new group.
There are three common scenarios which may encounter these transition periods:
In each of these scenarios, a Group may become temporarily responsible for a future Group's issues and backlog. During this time, the responsible Group should balance the needs of our users and organization, prioritizing across the common backlog.
For every scenario above, we also need to ensure that the Engineering Metrics dashboard is updated to correctly track the new label.
The label change affects both Issues and Merge Requests. The Stage and Group labels power the visualization and metrics in the Quality and GitLab Insights dashboards.
Please create a new issue in the Triage Ops with the template label-change.md.
As the group(s) working on a Stage grow in size, a new Group may need to be formed so group sizes remain manageable. For example, today
there is a single group for Manage, but will be splitting into control and framework groups.
To prepare for splitting a Stage into multiple Groups, we should:
categories.yml and stages.yml, assigning each Group a set of Categoriesdevops::manageControl or Frameworkdevops::manage backlogOnce the first PM or EM is hired, the new Group should be formed:
Control and Framework. Ideally, each group would have at least two backend engineers, but that is not always possible.stages.yml and team.yml to reflect the current group members. Update _categories.erb with the member names, if necessary.g_control and g_framework, and close the previous Slack channel (e.g. g_manage)As the rest of the EM/PM's are hired, they take over that role for the respective group.
The categories within a Stage will change over time, based on GitLab's direction and the market landscape. The groups within a Stage will need to be able to handle these changes, without issues falling in the cracks.
When the categories change, we should:
categories.yml and stages.yml, ensure all categories are assigned to a GroupWhen GitLab decides to address additional needs within the single application, a new Stage may need to be created. For example, Defend may be created to
address additional needs beyond what Secure focuses on.
When a new Stage is added, and its Group has yet to be formed, we should:
devops::defend and DefendSecure, which will be initially responsible for the new Stagedevops::defend and devops::securecategories.yml and stages.yml, listing the new Stage with the members of the existing responsible Group. Update _categories.erb with the member name, if necessary.Once the first PM or EM is hired, a new Group for the Stage should be formed:
Defend. Each Group should have at least two backend engineers.Secure on Secure and Defend on Defend.stages.yml to reflect the new Group and its members. Update _categories.erb with the member name, if necessary.As the rest of the EM/PM's are hired, they take over that role for the new Group.
As a PM, you must plan for the near term milestones (more detailed) as well as for the long term strategy (more broad), and everything in between. Considered as a spectrum, these form a nearsighted roadmap. This will enable you to efficiently communicate both internally and externally how the team is planning to deliver on the product vision.
Use calendar year (CY) dates for your issues, milestones, and labels to communicate timelines. Fiscal year (FY) does not translate well outside the company and roadmaps and vision pages are intended for external consumption. If you'd like to denote that an issue will be completed within a fiscal quarter use the month or GitLab release number for the last month in the fiscal quarter. E.g. use 12.4 (2018-10-22) instead of FY20-Q3. The issue can always be moved up in date and users/customers will seldom complain when functionality ships earlier than expected.
Creating a thoughtful direction for your section, stage, or category is a useful thought exercise that can help focus efforts, aid in prioritization, and get large groups of people on the same page. But beware of simply executing your long term plan. Our industry is incredibly dynamic, and we learn new things every day that can and should cause us to re-think our long term plans. Stay focused on creating value each and every milestone, and be quick to adjust your longer term plans as you learn more.
Section leaders are responsible for maintaining Direction pages that lay out the strategy and plan for their respective section and stages. The direction pages should include topics outlined in this template, which include:
A category strategy is required which should outline various information about the category including overall strategy, what's next, and the competitive landscape. The category strategy should be documented in a handbook page, which allows for version control of the category strategy as well as the ability to embed video assets. One of the most important pieces of information to include in the category strategy is a tangible next step or MVC in order to push the category up the category maturity curve.
When creating a category strategy, 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. Your category strategies should contain short paragraphs with lots of references to specific issues. Here is an example.
We use this category strategy template
as the outline for creating the handbook pages. If additional headings are needed you are empowered
to create and populate them in your category strategy. You must keep these categories in sync with categories.yml and for
new categories.
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 strategy (you can see an example for
GitLab Pages with a Strategy button here). You should also link
to your category strategy from your stage strategy page.
Category direction should be reviewed on a regular basis (at least monthly) by the responsible product
manager. To indicate the last time a category direction page was reviewed, please ensure pages
include Content Last Reviewed: yyyy-mm-dd at the top of the category content. Update this date with every
review, even if other content on the direction page has not changed.
Inside of the categories.yml file there are dates assigned for either achieved or anticipated maturity achievement. These should be kept inline with communicated dates for achievement and updated as required. Also inline with GitLab's Strategy Sequence, 50% of categories were determined by Product Leadership to be capable of achieving loveable by 2023-11-18. If one of your categories has this date for Loveable any changes to this should be discussed with your manager.
For each category, we track the improvements required to advance to the next level of maturity. These issues are indicated with an epic, and the planned feature set should be clearly visible from the corresponding category strategy page. e.g.:
The category epic should include:
Maturity plans adhering to the maturity framework are highly encouraged - but not required - for non-marketing categories.
For specifics of how the category strategy page should look, see the category strategy template.
In order to plan effectively around releases, as a PM you should have 3 months of detailed milestones scheduled at all times. The issues contained in these milestones are the ones you should be spending the most energy on (fleshing them out, adding detail, discussing, etc). These issues will go through a refinement period where Product, Engineering, UX, and other parties will discuss the proposal until a proper MVC proposal is reached (see Content of an MVC for more detail). Most of the communication should happen within the issue comments, but some may happen offline (such as via Slack). Ensure that any relevant information that arise as part of an offline conversation is added to the issue title and issue description. As a PM you must ensure that issues have enough detail added to them before they become actionable as part of an iteration.
These next milestones will also help planning for capacity with engineering and UX in order to commit to the contents of the next release.
Our ability to iterate quickly is a measure of our efficiency, but our effectiveness is just as critical. As a product manager you are critical to us not just working correctly, but working on the correct things. You do that by prioritizing appropriately. Your prioritization decisions will be enhanced if you maintain a sufficient understanding of the context in which you make them.
There is no limit to the amount of inputs you can utilize for making prioritization decisions. We've organized these mechanisms into three lists. One for those that primarily sense feedback from users, one that primarily senses feedback from buyers and another that senses internally generated feedback which could represent buyers or users. For new PMs consider these lists as guidance for places to ensure you are plugged in to maintain sufficient context.
User
Buyer
Market
Internal
Refer to the Product Development Timeline for details on how Product works with UX and Engineering to schedule and work on issues in upcoming releases.
Product Managers assign milestones to issues to indicate when an issue is likely to be scheduled and worked on. As we consider more distant milestones, the certainty of the scope of their assigned issues and their implementation timelines is increasingly vague. In particular, issues may be moved to another project, disassembled, or merged with other issues over time as they bounce between different milestones.
The milestone of an issue can be changed at any moment. The current assigned milestone reflects the current planning, so if the plan changes, the milestone should be updated as soon as possible to reflect the changed plan. We make sure to do this ahead of starting work on a release. Capacity is discussed between the PMs and the engineering managers.
In general, closer-to-current-time milestones are assigned to issues that are higher priority. It's best to maintain prioritization of your groups issues using a fully prioritized issue board. The timing of prioritized items broken across releases reflects an approximate product direction, with more distant milestones reflecting increasing uncertainty.
The milestones are:
9.4, 9.5, etc.Next 3-4 releasesNext 4-7 releasesThese assigned milestones should be used as a signal for GitLab stakeholders and collaborators, to help them with their own respective workflows.
In addition, we have two special milestones: Backlog and Awaiting further demand.
Product Managers assign these issues to milestones that they have reviewed and
make sense, but do not fit within the upcoming release milestones due to either
a lack of comparative urgency or because we have not yet seen enough user
demand to prioritize the item yet. The best way to demonstrate urgency on
either of these items is to vote on them and, if possible, add comments
explaining your use case and why this is important to you.
Recommendation for when to change 'Awaiting further demand': Consider the number of people who use, not just have access to, the area impacted by the issue. When you receive enough feedback to be equal to a percentage of the power users, it is likely to consider moving the issue forward. Often public feedback only comes from a small percentage of people using or evaluating a feature or product. There needs to be a balance between waiting too long and acting too fast. In addition, there may be a tendency for more negative feedback than positive feedback, remember that people are passionate enough to care about this issue and it should be taken constructively.
Recommendation when changing a previously planned issue to Backlog: When moving
a previously planned issue to Backlog, especially one planned for within the next release or two,
consider the message that this may be sending to parties that were interested in this feature.
In some cases, they may have been depending or planning upon the issue to be delivered around
the assigned milestone, and with the change to Backlog that is now unlikely to occur. In these instances,
it is best to concisely explain the rationale behind the change in a comment, so
the community can understand and potentially respond with additional justification or
context. It is also encouraged to move the issue to the Backlog as soon as it is clear that it will not be scheduled in the near future. This will help with understanding the change, as it will not seem like a last minute change.
Again, the milestone of an issue can be changed at any moment, including for both of these special milestones.
For a detailed timeline, see the product development timeline.
From time to time, there may be circumstances that change the ability for a team
to ship the features/issues they committed to at the beginning of the iteration. These steps also apply when an issue is broken into multiple issues.
When this happens, as a PM you must ensure the impacted issues and their milestones
are updated to reflect the new reality (for example, remove deliverable
tag, update milestone, etc.). Additionally, notify your manager of the shift.
Our design system provides the means to work autonomously, without always needing UX insight and feedback. When problems can be solved using an already documented paradigm, you don't need to wait for UX approval to bring an issue to a reasonable state within a first iteration.
If lingering questions remain, subsequent iterations can address any shortcomings the feature might have.
As a product manager, you should carefully consider the costs and benefits when planning to introduce a breaking change. Breaking changes may heavily impact existing users, and it is your responsibility to minimize the negative effects.
If you want to introduce an urgent breaking change in a minor release (e.g. you need to provide support for a new feature that cannot be backward compatible), you have to consider how many users will be affected by the change, and whether the change can wait until the next major release instead.
If you evaluate that the impact on users is acceptable (e.g., you have evidence that the feature is not used significantly), and the change will allow many users to benefit of new features or to solve problems, follow this process:
#twitter Slack channel#customer-success and #sales Slack channels#support_self-managed and #support_gitlab-com Slack channelsEngaging directly with the community of users is an important part of a PM's job. We encourage participation and active response alongside GitLab's Community Advocates.
A general list of conferences the company is participating in can be found on our corporate marketing project.
There are a few notable conferences that we would typically always send PMs to:
If you're interested in attending, check out the issue in the corporate marketing site and volunteer there, or reach out to your manager if you don't see it listed yet.
Stakeholder collaboration and feedback is a critical competitive advantage here at GitLab. To ensure this is possible, and facilitate collaboration, you should maintain an updated single source of truth (SSOT) of your stage direction, category strategies, and plan, at all times. This equips anyone who wants to contribute to your stage’s product direction with the latest information in order to effectively collaborate. Some sections and teams use the scheduled Direction Update issue template to remind themselves of this task.
Actively and regularly reach out to stakeholders. Encourage them to view and collaborate on these artifacts via these (non-exhaustive) opportunities:
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:
It's important to get direct feedback from our customers on things we've built, are building, or should be building. Some opportunities to do that will arise during sales support meetings. As a PM you should also have dedicated customer discovery meetings with customers and prospects to better understand their pain points.
As a PM you should facilitate opportunities for your engineering group to hear directly from customers too. Try to schedule customer meetings at times that are friendly to your group, invite them, and send them the recording and notes.
Before the meeting, ensure the Sales lead on the account has provided you with sufficient background documentation to ensure a customer doesn't have to repeat information they've already provided to GitLab.
During the meeting, spend most of your time listening and obtaining information. It's not your job to sell GitLab, but it should be obvious when it's the time to give more information about our products.
For message consistency purposes, utilize the Value Drivers framework when posing questions and soliciting information.
After the meeting:
Create an interview snapshot summarizing the meeting in the gitlab-com/user-interviews project.
This project is private so that detailed and unredacted feedback can be shared internally.
Create or update related issues to publicly document feedback.
The synthesis of feedback from multiple meetings should happen publicly in an epic or issue.
Customer discovery meetings aren't UX Research. Target them to broad-based needs and plan tradeoff discussions, not specific feature review. There are two primary techniques for targeting those topics:
Follow the below guidance to prepare and conduct Customer Discovery Meetings:
Set up a meeting:
During the meeting:
After the meeting:
Document your findings. Create a folder (sharable only within GitLab) in Google Drive with a structure as follows:
You can find some additional guidance on conducting Customer Discovery Meetings from these resources:
PMs should also feel free to collect and evaluate customer feedback independently. Looking at existing research can yield helpful themes as well as potential customers to contact. You can use the following techniques to source customers directly:
GitLab Solution Architects know our customers the best, especially from a technical perspective.
GitLab Issues customers will often comments on issues, especially when the problem described by the issue is a problem they are experiencing firsthand. The best strategy is to capture their feedback directly on the issue, however, there are times when this is not possible or simply doesn't happen. You can find alternative contact info by clicking on the user's handle to see their GitLab user page; this page often includes contact information such as Twitter or LinkedIn. Another option is to directly mention users in issues to engage async. In popular issues you can just leave a general comment that you're looking for people to interview and many will often volunteer.
GitLab Broadcast Message Placeholders is a great tool for recruiting users from within the product. This tool alows users to be recruited durring or after interacting with specific workflows within the product. Currently, banner messages can be targeted by URL, and user information can be passed in order to personalize the message as well as the response.
GitLab Sales and Customer Success You can ask for help in Slack customer success channel or join the Field Sales Team Call and the All CS Team Call to present a specific request via the Zoom call.
Technical Account Managers (TAM) If a customer has a dedicated TAM, they may also have a regular meeting with a TAM. These meetings are a great opportunity to spend 15 minutes getting high-level feedback on an idea or problem. In Salesforce, TAMs are listed in the Customer Success section in the customer's account information. TAMs are also very familiar with the feature requests submitted by their customers and can help identify customers that may be interested in the feature you are working on.
Zendesk is a great tool to find users who are actively making use of a feature and either came across a question or an issue. Users who've had recent challenges using the product really appreciate PMs taking the time to learn from their expereinece. This establishes that we are willing to listen to users, even if they are not having a great experience. This is also a great opportunity to discuss the roadmap and provide context so that users understand what we are going to improve. The best way to request a chat is through the support ticket; however, you can also click on the user that initiated the interaction and their contact information will display on the left hand side panel.
If you don't have a Zendesk account, see how to request a light agent Zendesk account.
You can use Zendesk's trigger feature to receive email alerts when specific keywords relevant to your product area are mentioned in a support ticket. Additionally, it is possible to create a simple dashboard that lists all the currently active support tickets that match the trigger. Reach out int #support_managers to receive some help in setting this up.
Social Media can also be effective. If your personal account has a reasonable number of connections/followers, you can post your desire to connect with users on a specific question directly. When posting, remember to include the subject you want to discuss as well as how people can reach out. You can also reach out to the #social-media channel to have your tweet retweeted by the @gitlab account.
If you want to reach a wider audience, consider asking a community advocate to re-post using the official GitLab account for the relevant platform.
You can reach advocates on the #community-advocates Slack channel.
You can also reach out to authors of articles related to tech your team is working on, via various publications such as Medium. A clear and brief email via the publication website or LinkedIn is a good way to engage.
You're able to request a LinkedIn Recruiter license. This Unfiltered video and slide deck provide an overview on how to use Linkedin Recruiter to source participants for your study.
If you've tried these tactics and are still having challenges getting the customer feedback you need, connect with your manager for support and then consider leveraging the UX Research team. Addtionally you can connect with Product Operations directly or by attending Product Operations Office Hours for troubleshooting support.
Non-users are often more important than GitLab users. They can provide the necessary critical view to come up with ideas that might turn them into GitLab users in the end. The best non-users are the ones who don't even plan on switching to GitLab. You can reach these people at local meetups, conferences or online groups like, Hacker News. In every such case, 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.
One specific, recurring opportunity to get direct feedback from highly engaged customers is the GitLab DevOps Customer Advisory Board. You may be asked by the CAB to present your stage at these meetings. Here are some guidelines when doing so:
When someone requests a particular feature, it is the duty of the PM to investigate and understand the need for this change. This means you focus on what is the problem that the proposed solution tries to solve. Doing this often allows you to find that:
Do not take a feature request and just implement it. It is your job to find the underlying use case and address that in an elegant way that is orthogonal to existing functionality.
This prevents us from building an overly complex application.
Take this into consideration even when getting feedback or requests from colleagues. As a PM you are ultimately responsible for the quality of the solutions you ship, make sure they're the (first iteration of the) best possible solution.
When someone posts information in the #competition channel that warrants
creating an issue and/or [a change in features.yml][features], follow this
procedure:
I'm documenting thisfeatures.yml][features]Rejecting a feature request or a merge request is not an easy thing. People can feel quite protective of their ideas. They might have invested a lot of time and energy in writing those ideas. You can be tempted to accept a feature only to avoid hurting the people who thought of it. Even Worse, if you reject an idea too harshly, you might discourage other people to contribute, which is something we should strive to avoid.
However, as the number of issues and merge requests grows incessantly, we should be diligent about rejecting features we are sure will not work out. It's better for everyone: for the product team, so we don't maintain a huge backlog of things we will never do anyway, and for the users who won't have to wait for our feedback indefinitely.
Note: it's fine to not respond to issues that we think have potential until they gather momentum.
Feature requests and merge requests can be rejected for the following reasons:
Don't forget to thank the authors for the time and effort taken to submit the feature request/merge request. In all cases and without exception, you should be nice and polite when interacting with users and customers.
Part of being a product manager at GitLab is maintaining engagement with analysts, culminating in various analyst reports that are applicable to your stage. In order to ensure that this is successful and our products are rated correctly in the analyst scorecards, we follow a few guidelines:
It's important to be closely connected with your product marketing partner, since they own the overall engagement. That said, product has a key role to play and should be in the driver's seat for putting your stage's best foot forward in the responses/discussions.
Product managers should take advantage of the internal customers that their stage may have, and use them to better understand what they are really using, what they need and what they think is important to have in order to replace other products and use GitLab for all their flows.
We want to meet with our internal customers on a regular basis, setting up recurring calls (e.g., every two weeks) and to invite them to share their feedback.
This is a mutual collaboration, so we also want to keep them up to date with the new features that we release, and help them to adopt all our own features.
You should strive to maintain an updated Epic roadmap for your group (here's an example). This can take considerable effort but doing so will ensure your issues are well organized according to the principals laid out below.
As part of our planning process it is important that you maintain a prioritized
issue board for your group.
It's customary to call these boards STAGE - GROUP - Planning and to configure them to filter
to all issues with your group label and with each milestone as a column (here's an example).
As the DRI for prioritization it is your responsibility to ensure that all items on your Planning board are scheduled to a milestone and are prioritized both within and across milestones. This means the lowest priority in the current milestone would generally be the top priority in the next milestone.
In this regard your planning exercise is a complete prioritization of the near term issues.
Issues related to the same feature should be bundled together into an into an epic.
Features may include multiple issues even if we are just targeting an MVC. In this case, we should use an epic to collect all of them in one single place. This epic should have a start and an end date, and it should not span more than 3 releases, otherwise we run the risk of having epics drag on indefinitely.
When these issues are finished and closed, we should have successfully achieved the
epic's goal. A good example of this kind of epic is the first iteration on a new
feature. Epics representing MVCs should clearly state MVC at the end of the
title and should have a parent epic relationship towards a category strategy or a meta epic.
We use epics to track many issues related to a specific topic, even if there isn't a specific timeline for shipping. These epics should be marked as ~meta, they may not have a specific start or end date, and may contain single iteration epics.
This is useful to have an overview of the future so participants and observers can understand how the pieces fit together. It can be really useful to understand the context of where we think we’re going so we can do a good job with the MVC.
Also, it conveys confidence internally and externally that we understand what we need to do when the MVC is particularly minimal. But don't get too caught up in long-term epics as you risk making proposals too complex, and overrepresenting certainty in the solution. Don't work too far in the future; we'll know better once we ship something small.
When creating a meta epic, there's a natural tendency to capture it as quickly as possible and then move on, but we must always strive to create a more specific epic for the first iteration, or the next iteration if something already exists. Describing an MVC means that the community can contribute more 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 meta issue. But you can't have a meta issue without an MVC.
We use issues to define narrowly scoped items of work to be done. Issues can focus on a variety of different topics: UX problems, implementation requirements, tech debt, bugs, etc. A good guideline for experience-related issues is that they should address no more than one user story. If an issue includes multiple user stories, then it is likely an epic.
In GitLab itself, there are short definitions of feature (internal link) and bug (internal link) which are displayed when hovering over the labels. This page provides context and elaborates on these definitions.
GitLab's Iteration value means we often make small improvements to the product. We use this to get feedback on what features are important to people. It is not a bug when GitLab is missing functionality.
You should create an issue if:
You should consider not creating an issue when:
GitLab product issues will often have one of the two type labels ~bug or ~feature. There are also other higher precedence labels, as documented by Engineering throughput
Consider whether an issue is a missing feature, or a bug:
Feature issues identify work to support the implementation of a feature and/or results in an improvement in the user experience.
~feature.~feature.~"Accepting merge requests"Bug issues report undesirable or incorrect behavior, such as:
~bug.S1.When an issue is open, this signals that we're intending or considering implementing that change. It's important to close issues that we're not considering implementing in the near future, so that we avoid creating uncertainty with customers and colleagues.
When closing an issue for this reason, make sure to update the issue body and leave a comment explaining why the issue is being closed. Issues can be reopened if we change our stance on them.
Sometimes, you'll end up prioritizing an issue that was created a significant time ago. When you move these issues into an upcoming milestone, look closely to see if they need to be groomed again, so that they include current information. A good rule is to review any issue you didn't personally create or that has been open longer than 3 months.
To clearly communicate to our stakeholders what we are going to do, it's critical that you not only provide the positive view (what we will do), but also articulate the negative view (what we will not do). While this should be communicated in stage and category strategies, it starts with issues:
As a Product Manager you should close issues that are:
When closing an issue, leave a comment explaining why you're closing the issue, and link to anything of relevance (the other duplicate, the original feature that this is an iteration on, etc).
The 'not the next iteration' issues are the most important ones to resolve. It is very easy to create a large, comprehensive change with meta issues and lots of improvements, but it is essential that we iterate and ship the minimal viable change. We have to ship the iteration, wait for it to be used, and ask for feedback. As a product manager, you must think about the bigger picture when making a proposal to improve the product. It's important to avoid writing this down as a bunch of issues. Come up with a direction, but only record the first step. This way we can preserve the efficiency of our value of iteration. Closing issues whenever possible is an important part of your job and helps to keep a clear view of what is next. Consider using the following template to close an issue:
Closing this because XXX is something we should do first. When that feature is finished, we can learn from observing it in use. If we learn that this issue is still relevant, we can then reopen it. See /handbook/product/product-processes/#issues for more detail about this policy.
When relevant, you can include a wireframe in your issue to illustrate what you're thinking about. But you don't need to create wireframes on your own; our UX team has a designer embedded in every stage group who will help you figure out how to solve the problem you're addressing. They should actively participate in your planning processes, so your request won't be a surprise.
If you do want to create a wireframe, we like Balsamiq for its simplicity and low fidelity. If you are struggling for inspiration, you can also paste screenshots of similar features in other products.
A general guideline is that an issue should only span one release. If we know an issue is going to span multiple releases, split it up into multiple issues.
Epic issues are the exception to this rule, but should be kept to a minimum and only serve to guide broader subjects, not a single feature over multiple releases. This is to make sure we stick to our values of the minimally viable change. This means that feature issues should be closed after the first iteration whenever possible. We'll know more in the future and this keeps any remaining issues short and actionable.
In addition, it's often a good idea to throw away an original plan and start fresh. Try to do this more often, even more than you're comfortable with. Close the issue and create a new one.
When you don't have any specific tasks assigned, you should work on issues that are
labeled Product work, in both the EE and CE projects. These are issues that need
our attention the most.
When performing the role of Life Support PM only the following are expected:
Some discouraged responsibilities:
In order to avoid suffering in silence, encourage growth in your trade and foster collaboration and understanding across groups and stages we have a Product Buddy System whereby we designate pairs of Product Managers. These pairs should consider working together on:
The pairing for this buddy system is defined in the Product Buddy System Google Doc (internal only).
Product Managers are fully empowered to define the what and priority of what they are building. Making PMs the DRI enables our entire company to iterate faster and drive more value for users. There are two instances where it is helpful to have an outside review of your scheduled issues. Those are:
As a result, the Ops and CI/CD sections utilize an MVC & New Config issue to encourage additional review of upcoming issues that are MVCs or introduce new configuration.
As a Product Manager you may need to make a decision on whether GitLab should engineer a solution to a particular problem, or use off the shelf software to address the need.
First, consider whether our users share a similar need and if it's part of GitLab's scope. If so, strongly consider building as a feature in GitLab:
If the need is specific to GitLab, and will not be built into the product, consider a few guidelines:
If after evaluating these considerations buying a commercial solution is the best path forward:
vendor_contracts template, ensure the justification above is included in the request.When considering open source software in build vs. "buy" decisions we utilize the following general criteria to decide whether to integrate a piece of software:
Tracking feature engagement after we've shipped is an important part of product management and software development. To accomplish this in the GitLab product, we use different approaches for self-managed and GitLab.com. To visualize the data we extract from both, we use our data visualization tool.
Self-managed instances are not required to maintain a connection with GitLab, Inc. Instead, we rely on an on-by-default usage ping that can be optionally disabled by any instance. Instances attempt to send this weekly.
To visualize and explore our existing dataset, please see our data visualization tool.
Self-managed instances perform a version check-in, where GitLab collects your version and host URL.
Even though PMs are strongly encouraged to ship features with robust metrics for tracking success from day 1, they should feel free to continue iterating in order to improve data collection. (see usage_data.rb for the current schema).
For more information, see our Usage Ping documentation.
We use the open-source Snowplow for identifying users and events on GitLab.com. These events are extracted to a Snowflake data warehouse and - like usage ping - visualized in our data visualization tool.
Since GitLab.com is an GitLab EE instance, we're also able to query tables in PostgreSQL that are detailed in schema.rb for analytical purposes. As of November 2018, query access is dependent on allowing SSH access to a dedicated read-only replica.
Since GitLab.com is maintained by GitLab, Inc. and Snowplow allows for much richer event tracking, we capture better data more frequently. A comparison:
| Compared dimension | Self-managed (Usage Ping) | GitLab.com |
|---|---|---|
| Frequency | Infrequent; sent weekly from instances | Frequent; hours to see new events |
| Fidelity | Low; anonymized counts | High; page views, clicks, time spent on page, anything in schema.rb |
| User penetration | Low; most instances opt-out | High; users can opt out of event tracking in browser, but Snowplow/PSQL captures almost everything |
| Customer representation | Fair; self-managed is more representative of EE use, but opt-out remains high | Poor; high proportion of free individual users |
| SMAU eligible | Yes - events tracked with usage ping can be added to a stage's SMAU definition | No - events tracked with Snowplow are not able to be added to SMAU as user_id is not tracked. |
The last item is the most salient; analyses should consider differences in population and behavior (and ideally control for them, such as filtering individuals/non-groups out of analysis), as usage across GitLab.com will likely differ significantly from usage on a large self-managed instance.
Like Usage Ping, individual teams are free to prioritize and capture events using the existing Snowplow implementation.
Page views and page pings (time spent on page). Captured automatically. Snowplow was introduced as a configurable
setting that when enabled, sits in the header of every page on GitLab.com. As a result, we get a destination and referral URL for each page (using the trackPageView method) along with page pings every 30 seconds (using the enableActivityTracking method).
Custom click events. Capturing specific click events on individual pages requires specification of what we'd like to track. Tracking click events is accomplished by calling a generic JS function wherever desired. When clicked, the client sends a defined click event to our Snowplow endpoint. This function is based on Snowplow's built-in trackStructEvent method.
To send additional click events to Snowplow:
When adding new click events, we should add them in a way that's internally consistent. If we don't, it'll be very painful to perform analysis across features since each feature will be capturing events differently.
The current method provides 5 attributes that are sent on each click event. Please try to follow these guidelines when specifying events to capture:
| attribute | type | required | description |
|---|---|---|---|
| category | text | true | The page or backend area of the application. Unless infeasible, please use the Rails page attribute by default in the frontend (document.body.dataset.page), and namespace + classname on the backend. |
| action | text | true | The action the user is taking, or aspect that's being instrumented. The first word should always describe the action or aspect: clicks should be click, activations should be activate, creations should be create, etc. Use underscores to describe what was acted on; for example, activating a form field would be activate_form_input. An interface action like clicking on a dropdown would be click_dropdown, while a behavior like creating a project record from the backend would be create_project |
| label | text | false | The specific element, or object that's being acted on. This is either the label of the element (e.g. a tab labeled 'Create from template' may be create_from_template) or a unique identifier if no text is available (e.g. closing the Groups dropdown in the top navbar might be groups_dropdown_close), or it could be the name or title attribute of a record being created. |
| property | text | false | Any additional property of the element, or object being acted on. |
| value | decimal | false | Describes a numeric value or something directly related to the event. This could be the value of an input (e.g. 10 when clicking internal visibility). |
| context | json | false | Context is in the process of being defined. |
Other guidelines:
document.body.dataset.pageclick_tab (general action taken -> what the action was taken on).