Revamped onboarding flow

Created by: sourcegraph-bot

User problem

• When starting with Batch Changes, users have to learn many things at the same time (new concepts, the CLI, how to define batch changes, tools to define changes). The onboarding is hard to self-serve,

• Users often seek code change examples for their specific use cases, and fail to discover them. This results in increased workload for CEs, delayed onboarding for the user that has to wait for help before getting started.

Motivation

We want more users within a company to be able top discover Batch Changes. Although enablement sessions can be ran by CEs, we aim at having users discover Batch Changes and self-serve more

Proposal

• Revamp onboarding flow from step create. Shoa a checklist, updating as the user completes actions?

  • If user never logged in through CLI, guide users through CLI installation

  • Link to how to generate a token

• Include links to the new example website

We should focus on UX quick fixes as opposed to large engineering efforts, given that server side will require a new flow.

Defining success

We don't have a baseline for this, and it will be hard to isolate from other contributions to Batch Changes MAUs.

We should start tracking the aggregated count of users completing onboarding steps:

count_users_viewed_create_page

count_users_clicked_install_CLI

count_users_generated_token

`count_users_CLI_login```

Once this flow is good enough, metrics will be removed.