Close user journey map working group as complete

1. [Keep around references](/handbook/company/working-groups/keep-around-refs/)

1. [Product Accessibility](/handbook/company/working-groups/product-accessibility/)

1. [Secure Govern Database Decomposition](/handbook/company/working-groups/secure-govern-database-decomposition/)

1. [User journey map](/handbook/company/working-groups/user-journey-map/)

## Past Working Groups (alphabetic order)

1. [Upstream Diversity](/handbook/company/working-groups/upstream-diversity/)

1. [Usage Reporting](https://gitlab.com/groups/gitlab-com-top-initiatives/-/epics/1)

1. [User Engagement](https://gitlab.com/groups/gitlab-com/-/epics/1794)

1. [User journey map](/handbook/company/working-groups/user-journey-map/)

1. [Vue.js 3 Upgrade](/handbook/company/working-groups/vuejs-3-migration/)

1. [Webpack (Frontend build tooling)](/handbook/company/working-groups/webpack/)

|--------------|------------------|

| Date Created | April 23, 2025   |

| Target Date  | July 15, 2025 |

| Actual End Date | July 22, 2025 |

| Slack        | [#ujm-working-group](https://gitlab.slack.com/archives/C08PCJAM3F0) (internal only) |

| Google Doc   | [User Journey Map Working Group Agenda](https://docs.google.com/document/d/1MiN_6N3nV8A5zioI9KDex9WuxBMRs9rtxO_MiJ-brpg/edit?) (internal only) |

- Develop guidelines for various levels of journey elevation (macro, mid, micro) `=> 100%`

  - Status: [Complete](/handbook/product/ux/user-journeys/#journey-map-elevations)

- Establish templates, methodologies, and best practices for journey documentation `=> 100%`

  - Status: Complete; [Templates](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/14575), [Documentation](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/14463)

- Create a centralized system for storing, accessing, and connecting journey maps `=> 75%`

  - Status: We have [reviewed various tooling](https://gitlab.com/gitlab-com/Product/-/work_items/14209) and are exploring whether a specialized journey mapping tool is worth pursuing. In the meantime, we have set up a "Journey Mapping" team in Figma which includes templates and projects for various journey map elevations. Next, we need to document how to use this system in the handbook.

- Establish communication channels for journey insights and discoveries `=> 50%`

  - Status: We have created the #gitlab-user-journeys slack channel and included its use in our best practices. Next, we need to tie it into the various issue templates.

- Create a structure for translating journey insights into strategic opportunities based on business impact and user value `=> 50%`

  - Status: We have drafted an issue template for teams to utilize, [currently under review](https://gitlab.com/gitlab-com/Product/-/work_items/14211). We are discussing whether a dedicated research issue template should be created for user journeys or whether we can utilize existing templates.

  - Status: Complete; [Templates](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/14575), [Documentation](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/14463), [Best practices](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/14881)

- Create a centralized system for storing, accessing, and connecting journey maps `=> 100%`

  - Status: Templates have been created in Figjam and we will utilize a Figma team to hold all user journeys. Templates include a way to link to nested and parent templates. Guidance has been added to the [user journey issue template](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/198429).

- Establish communication channels for journey insights and discoveries `=> 100%`

  - Status: We have created the #gitlab-user-journeys slack channel and included its use in our best practices. This has been tied into the [user journey issue template](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/198429), as well as [best practices](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/14881).

- Create a structure for translating journey insights into strategic opportunities based on business impact and user value `=> 100%`

  - Status: We [updated existing actionable insights issues](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/198444) to include the business problem and relevant user journey metadata.

## Roles and Responsibilities