debian-mirror-gitlab/.gitlab/issue_templates/Empty state.md

Description

Location

Use case

• Blank content
• Empty search results
• Configuration required
• Higher tier

Checklist

Blank content

• The solution follows the Blank content specifications in Pajamas.
• Follow the instructions from the After merge section below to add Snowplow tracking.

Empty search results

• The solution follows the Empty search results specifications in Pajamas.
• Follow the instructions from the After merge section below to add Snowplow tracking.

Configuration required

• The solution follows the Configuration required specifications in Pajamas.
• Ask a Growth product manager or Designer to review your solution.
• Is your solution introducing a new empty states or modifying an existing one?
  • Introducing a new empty state: Follow the instructions from the After merge section below to add Snowplow tracking.
  • Modifying an existing empty state: Follow the Experimentation process below. Note: If the empty state you want to replace hasn't been updated in a long time, doesn't pitch the value of the feature, or does not contain a next step action CTA, then we recommend you skip the experimentation process to implement and add tracking to your new empty state.

Experimentation

• Collaborate with a Growth product manager to help you determine if you can validate your solution through an experiment on SaaS.
• If an experiment is possible, create an issue using the experiment idea template and follow the template intructions. Otherwise, follow the instructions from the After merge section below to add Snowplow tracking.
• Ask a Growth product manager or Designer to review your experiment set-up.
• Implement and monitor the experiment following the implementation guide.
• Review and discuss the findings.
• Add the findings to the Growth experimentation knowledge.

Higher tier

• The solution follows the Higher tier specifications in Pajamas.
• Ask a Product Manager or Designer from the Conversion group to review your solution.
• Is your solution introducing a new empty states or modifying an existing one?
  • Introducing a new empty state: follow the instructions from the After merge section below to add Snowplow tracking.
  • Modifying an existing empty state, follow the Experimentation process below.

Experimentation

• Collaborate with a Growth product manager to help you determine if you can validate your solution through an experiment on SaaS.
• If an experiment is possible, create an issue using the experiment idea template and follow the template intructions. Otherwise, follow the instructions from the After merge section below to add Snowplow tracking.
• Add a ~"Category:Conversion Experiment" label to the experiment idea issue.
• Ask a Product Manager or Designer from the Conversion group to review your experiment set-up.
• Implement and monitor the experiment following the implementation guide .
• Review and discuss the findings.
• Add the findings to the Growth experimentation knowledge.

After merge

• Use the Snowplow event tracking issue template and open an issue to add Snowplow event tracking to your new empty state solution.
  • Add your ~devops:: and ~group:: labels to the new issue.