Feedback Collection: Growth Experiment Implementation Process

Growth Experiment Implementation Feedback

This issue serves as the central hub for collecting feedback from engineers, PMs, and UX on the process of implementing Growth experiments. We want to understand the challenges, obstacles, and chores involved in experiment implementation to improve our processes.

Instructions

For each experiment, please create a separate thread in the comments below and discuss the following topics:

What to include in each thread

• Experiment Name/ID: Clearly identify which experiment you're discussing
• Role: Specify if you're providing feedback as an Engineer, PM, or UX
• Challenges: What obstacles did you encounter during implementation?
• Process Issues: What parts of the current process created friction or inefficiency?
• Chores/Overhead: What repetitive or administrative tasks slowed down progress?
• Suggestions: How could we improve the implementation process?
• Timeline Impact: Did any issues affect delivery timelines?

Thread format example

**Experiment: [Name/ID]**
**Role: [Engineer/PM/UX]**

**Challenges:**
- [List specific challenges]

**Process Issues:**
- [Describe process friction points]

**Suggestions:**
- [Proposed improvements]

Goals

• Identify common pain points across different experiments
• Understand role-specific challenges (Engineering vs PM vs UX)
• Collect actionable suggestions for process improvements
• Create a knowledge base for future experiment implementations

Please be specific and constructive in your feedback. This information will help us streamline our Growth experiment process and reduce implementation overhead for future experiments.

/cc @gitlab-org/growth