GitLab.com supports a wide range of customer workflows, but we don't have a shared, canonical list of the most important ones — or agreed metrics for measuring their health. This work may already exist in partial form across product analytics, UX research, support data, and stage/group documentation. The goal here is to find what's there, fill gaps, and publish it in one place so Engineering teams have a shared set of targets to work against. **First deliverable:** A published list of priority customer journeys, each with: - A user-visible description (e.g., "Review and merge an MR") - At least one candidate SLI signal (e.g., MR diff page load time) - A draft target threshold (e.g., p95 \< 3s) Child issues and follow-on work will be defined once the journey list is established. ### Top 5 — SLI instrumentation sequencing Note: Author a merge request and review an MR may already be implemented in [the dashboard](https://dashboards.gitlab.net/d/general-user-experience-sli-violations/general3a-user-experience-sli-violations?from=now-7d/m&orgId=1&timezone=utc&to=now/m&var-PROMETHEUS_DS=mimir-gitlab-gprd&var-environment-2=gprd&var-environment=gprd&var-product_stage=$__all&var-stage=main&var-stage_group=$__all). | \# | Journey | Key user action | Candidate SLI signal | Draft target | Stage Group Owner | |----|---------|-----------------|----------------------|--------------|-------------------| | 1 | **Sign in and reach the home dashboard** (https://gitlab.com/gitlab-org/gitlab/-/issues/596309) | Enter credentials → authenticate → dashboard renders | Authentication + dashboard load time (p95) | \< 2s | Authorization | | 2 | **Author a merge request** (https://gitlab.com/gitlab-org/gitlab/-/issues/596310) | Push branch → MR created → diff rendered | MR diff page load time (p95) | \< 3s | Create | | 3 | **Review and merge an MR** (https://gitlab.com/gitlab-org/gitlab/-/issues/596311) | Open MR → view diff → approve → merge | Time from MR open to merge button available (p95) | \< 5s | Create | | 4 | **Trigger a pipeline and see first job start** (https://gitlab.com/gitlab-org/gitlab/-/issues/596312) | Push commit → pipeline created → first job picked up | Job queue wait time (p95) | \< 60s | Verify | | 5 | **Investigate a failed pipeline** (https://gitlab.com/gitlab-org/gitlab/-/issues/596313) | Click failed pipeline → view job log → identify failure | Job log load time (p95) | \< 2s | Verify | | 6 | **Triage and remediate a vulnerability** (https://gitlab.com/gitlab-org/gitlab/-/issues/596316) | Open vulnerability report → filter by severity → assign for fix | Vulnerability report load + filter response time (p95) | \< 3s | Secure | ### Supplementary Journeys — SLI instrumentation sequencing | \# | Journey | Key user action | Candidate SLI signal | Draft target | Stage Group Owner | |----|---------|-----------------|----------------------|--------------|-------------------| | 6 | **Contribute to the latest update on an issue** (https://gitlab.com/gitlab-org/gitlab/-/issues/596317) | Open Issue → load relevant comment → type and send response | Issue comments load time (p95) | \< 2s | Plan | | 7 | **Break down work from epic to issues** (https://gitlab.com/gitlab-org/gitlab/-/issues/596318) | Create epic → create child issues → assign to milestone | Issue creation + hierarchy render time (p95) | \< 2s | Plan | | 8 | **Manage access and permissions** (https://gitlab.com/gitlab-org/gitlab/-/issues/596319) | Add member → assign role → verify access takes effect | Member add + permission propagation time (p95) | \< 5s | Authorization | | 9 | **Set up a pipeline from scratch** (https://gitlab.com/gitlab-org/gitlab/-/issues/596320) | Create `.gitlab-ci.yml` → validate → first successful run | Time to first green pipeline (p95) | \< 10 min | Verify | | 10 | **Onboard a new developer to a project** (https://gitlab.com/gitlab-org/gitlab/-/issues/596321) | Accept invite → clone repo → open first MR | Time from invite acceptance to first MR created (p95) | \< 30 min (funnel) | TBD |