Issue Prioritization Framework

1. You are here:
2. Meet the GitLab team
3. Organizational Structure
4. Working Groups
5. Issue Prioritization Framework

On this page

• Attributes
• Problem To Solve
• Business Goal
  • Exit Criteria
    • Step 1: Determine a viable model => 90%
    • Step 2: Implement & validate model => 100%
    • Step 3: Verify at scale and measure outcomes => 15%
• Roles and Responsibilities
• Meetings

Attributes

Problem To Solve

• We currently do not distinguish between "nice to have", "blocker", and "this will likely cause a downgrade/churn/prevent upsell." One customer may view Feature ABC as nice to have, whereas another customer desperately needs it. The time necessary to collect this information, transfer it, and then disseminate it among departments is likely to be inefficient and error prone. It also does not solve the problem of a standardized model for determining relative priority across all stages based on quantifiable data such as impact to retained ARR or net new ARR.
• We are currently proposing that we establish a highly manual process where individuals will act as bridges to transfer information across departments.
• We are not leveraging our existing data to the fullest extent. Let's understand why and solve for this.

Business Goal

• Create a standardized prioritization framework based on quantifiable data that enables us to determine urgency/value per issue/epic at scale and speed so that Product, Sales, and Customer Success can use a common language and model when discussing prioritization trade-offs.
• Product DRIs have more accurate inputs to help them globally optimize their delivery backlogs resulting in increased customer retention and acquisition.
• Positively impact Net ARR growth and improve retention of existing ARR.
• Improve the accuracy of the prioritization feedback among departments.
• Further operationalize the process of creating effective bridges between Customer Success, Sales, and Product.

Exit Criteria

(✅ Done, ✏️ In-progress)

Step 1: Determine a viable model => 90%

• ✅ Cost of Delay / Duration will serve as the primary model to run a pilot against.
• ✅ We've determined how to assign monetary value for issues with links to SFDC.
• ✏️ Determine model inputs for issues that do not have SFDC links.
• ✅ Define TAM inputs.

Step 2: Implement & validate model => 100%

• ✅ Design initial pilot and break down into tasks and DRIs.
• ✅ Identify a DRI that can complete the data related tasks.
• ✅ Implement pilot.
• ✅ Assess results and outcomes. If pass, move to Step 3. If fail, exit WG or cycle back to Step 1.

Step 3: Verify at scale and measure outcomes => 15%

• ✏️ TL;DR: Once validated, we drive adoption across Product/CS/Sales and collect measurements to confirm that this model is producing the desired business outcomes. If not, decide to go back to Step 1 or Exit.
• This will be populated with specific tasks once we are further along with step 2.

Roles and Responsibilities

Meetings

This working group meets bi-weekly (every other week.)

Meetings are recorded and available on YouTube in the Working Group - Issue Prioritization Framework playlist. Due to the subject matter of this working group and the high probability that every syncronous meeting will discuss sensitive customer information, the playlist is private and accessible by GitLab team members only.