Growth:Conversion planning for 13.9
The following is the Growth:Conversion group priorities for %13.9
Process and timeline
Click to expand!
Process
- https://about.gitlab.com/handbook/product-development-flow/
- https://about.gitlab.com/handbook/engineering/workflow/#product-development-timeline
- https://about.gitlab.com/handbook/engineering/development/growth/
- https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/growth/#how-we-work
- Please add/update/change any information directly in the description. Add a comment if you think the change needs an explanation.
- We link to but won't discuss details of security issues here, as this issue is public
- Previous Growth:Adoption planning issues
Timeline
- 4th - issue created, all group members can contribute ideas/issues (PM/EM/IC)
- Add proposed milestone to issues (PM)
- Label issues as ~"Growth-Deliverable" (PM)
- Update the Goals section (PM)
- Apply weight to issues for this milestone (Engineering)
- Apply the Deliverable label to issues we expect to close this milestone (Engineering)
- 15th - milestone planning finished - EM to summarize in planning summary for review in retrospective
Boards
- Validation: https://gitlab.com/groups/gitlab-org/-/boards/1506660?scope=all&utf8=%E2%9C%93&label_name[]=devops%3A%3Agrowth&label_name[]=group::conversion
- Build: https://gitlab.com/groups/gitlab-org/-/boards/1506701?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=devops%3A%3Agrowth&label_name[]=group::conversion
- Milestone https://gitlab.com/groups/gitlab-org/-/boards/1370834?scope=all&utf8=%E2%9C%93&label_name[]=devops%3A%3Agrowth&label_name[]=group::conversion
Review
- Any changes to pending or active experiments https://gitlab.com/groups/gitlab-org/-/boards/1352542?scope=all&utf8=%E2%9C%93&label_name[]=devops%3A%3Agrowth&label_name[]=growth%20experiment&label_name[]=experiment%20tracking&label_name[]=group::conversion
- Any cleanup/followup/removal issues required for completed experiments?
Note: tracking and cleanup issues are by default weight: 1
Goals for 13.9:
Goal / Epic | Detail | UX | Eng |
---|---|---|---|
continuous onboarding | This will be our first test of continuous onboarding and will help user understand if we can get namespaces to adopt more stages by having a dedicated space in the nav to access onboarding and what percent they've completed. Our team will specifically be working on the design I've linked to in our issue (design 1A). The Activation team will be working on design 1-B, the idea here is we will utilize the same backend events to measure if a namespace has completed the action (most events have already been implemented) and our respective teams will each build out a different version of the experience to test. The final goal being to run a multi-variant test between designs 1A, 1B and the control to see what design wins out over the control. Note, we're finalizing the list items and link locations in this issue but it should be ready within the next few days, related issue. | gitlab-org/gitlab#281022 (closed) @a_akgun Deliverable is %13.9, launch in %13.10 (tracking issue required) | |
Active trial status - hover modal | This is a follow up experiment to the MVC active trial status test. In this experiment, we will add an additional feature where we add the ability to hove on the trial status | gitlab-org/gitlab#298729 (closed) Deliverable @dreedy | |
highlight paid features | This MVC experiment will test highlighting a popular feature during the trial and help us understand if informing users about what features are paid within the trail helps in feature adoption and the conversion rate | gitlab-org/gitlab#273626 (closed) @dreedy | |
UX Priority 1: UX Research: Utilize credits as incentives for users or namespaces to complete specific actions | How should we think about implementing credits within GitLab? Is it something our users are interested in? What credits would they be interested in? What would they see as a fair exchange of value? All of these answers will help inform us on how we can design a reward system that our users will be excited about and will assist us in further achieving our OKRs. | gitlab-org/gitlab#298778 (closed) | |
UX Priority 2: Iterate on Continuous onboarding usability testing finding | Shall we move forward with product tours? If not how do we update our solution? | product#1647 (closed) | |
Security issue | WIP | https://gitlab.com/gitlab-org/gitlab/-/issues/25097 @a_akgun | |
Bug fix | This is required to re-enable 5 experiments | gitlab-org/gitlab#297379 (closed) @a_akgun | |
Cleanup issues weight paywal | To remove the flaky test | gitlab-org/gitlab#299590 (closed) |
Stretch goals:
Goal / Epic | Detail | UX | Eng |
---|---|---|---|
With no additional users add "invite" to nav during active trial | We see that group trials are far more successful when at least one additional user is invited to the trial. This experiment will add a menu option to invite colleagues in one user trials. | https://gitlab.com/gitlab-org/gitlab/-/issues/224692 tentatively for @a_akgun as a stretch goal (moved from goals section above) | |
Add bizible tracking to SaaS signup pages | Adding this code to the signup pages will help the marketing team understand lead quality allowing them to increase time/spend on campaigns that are driving actual signups | ||
In trial flow, only set user_target_https://gitlab.com/gitlab-org/gitlab/-/issues/249444 if user submits registration form | low priority bug fix | ||
Cleanup MVC contact sales experiment | |||
onboarding cleanup | I believe it'll be easier for us to test the continuous onboarding item above once this experiment is officially cleaned up so I'm ranking this higher in the priority order. If it's not a large impact on the rollout of the continuous onboarding test it can be reduced in priority. | @nicolasdular will handle this for groupactivation | |
UX Priority 3: Redirect in-app trial users to the feature that they requested the trial from | https://gitlab.com/gitlab-org/gitlab/-/issues/273635 |
Future planning (issues for review)
Engineering and UX notes
- Any follow up or missed deliverable issues from the previous milestone...
- Technical debt, security issues, or bugs based on severity/priority/due date...
- Any non-product led initiatives related to career development or Engineering KRs...
- ...
Planning summary (for retrospective)
- Engineering Goals: ?
- Total weight: ?
We don't count Stretch Goals or other issues unless they are dependencies, but they will be included in the retrospective summary at the end of the milestone.
Capacity:
(Vacation, other commitments)
Edited by Alper Akgun