Design: Create a visualisation for pipeline experience - Define → Run → Analyze → Optimize

Create visualization for the following proposal:

PA team owns Define and Optimize because both involve authoring and editing a yaml file.

Define issues relate to making it easier to configure/author a pipeline.

Optimize issues relate to tuning/editing a yaml file to improve its execution.

CI team owns Run and Analyze:

Run issues relate to making it easier to run/trigger a pipeline. Example: Generate Run Pipeline form with pre-filled variables from .gitlab-ci.yml

Analyze issues relate to greenfield work on a new UI for pipeline statistics; the goal is to help the user better understand pipeline health and performance so they can ultimately optimize or tune their pipeline. Next step: UX issue#1131 to identify most useful pipeline metrics to show in a UI for the first iteration (MVC) and metrics for later iterations.

Not all of the work that CI team will continue to do falls neatly under Run or Analyze (e.g., ci::artifact issues) but generally speaking these 4 areas describe the user experience with pipelines and the distinct areas where PA and CI team contribute to the user experience.