Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run A/B test on combing configuration steps of the Getting Started flow #3226

Closed
4 tasks
zchase opened this issue May 6, 2020 · 0 comments · Fixed by #3307
Closed
4 tasks

Run A/B test on combing configuration steps of the Getting Started flow #3226

zchase opened this issue May 6, 2020 · 0 comments · Fixed by #3307
Assignees
Labels
docs/get-started size/M Estimated effort to complete (up to 5 days).
Milestone

Comments

@zchase
Copy link
Contributor

zchase commented May 6, 2020

Currently one of the most problematic parts of the Getting Started flow is during the initial configuration steps. We want to understand if combing them into a single prerequisite step will help decrease the drop off rate for finishing the initial configuration steps. To do so we should run an A/B test with Variant A being the current version and Variant B being the combined steps version.

Suggested combination:

  1. Install Language Runtime
  2. Configure Cloud
  3. Install Pulumi

Steps to set up the experiment:

  • Create a combined version of configuration steps at a new URL, e.g. /docs/get-started/{cloud}/prerequisites.
  • Create an A/B test in Google Optimize.
  • Create new Segments in Google Analytics for the new Getting Started path.
  • Measure drop off rate of old path vs. new path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs/get-started size/M Estimated effort to complete (up to 5 days).
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants