Review and improve the doc experience around 5 Experience Baseline JTBDs. About Experience Baselines and JTBD: https://about.gitlab.com/handbook/engineering/ux/experience-baseline-recommendations/ **Requirements for Each Selected JTBD** 1. **Review existing info** - Review the UX issues, walkthrough video, and recommendations. If you have any questions, ask the Product Designer who performed the experience baseline review for your JTBD. 1. **Review SEO** - Review the experience as a user searching for how to perform the JTBD, both on Google (for meaningful docs.gitlab.com results) and on the doc site's search. Determine whether relevant pages and meaningful titles/subheadings exist so that the search is successful, or any content improvements that would help with the search. 1. **Document and improve SEO** - Specify one or more search queries that a user would use for this JTBD, their current result via Google and Algolia, a grading of the current result, and a final result after changes are made to the section.* 2. **Consider potential UI doc link** - Determine if any aspect of the JTBD experience (per the UX review) could be enhanced by linking from the UI to the most relevant, contextual documentation content, and collaborate with the Product Designer to implement this.* 3. **Review and improve documentation content** - Ensure the relevant docs content is clear on what's possible in GitLab related to the JTBD, and how to go about it. 1. **Test the instructions** (to the extent they were not yet tested in the experience baseline review) and identify new content or improvements that are needed. Specifically, determine if any content is unclear, inaccessible to new users (e.g. using technical terms without defining/linking), includes incorrect or outdated information or screenshots, contains any gaps or missing information, is difficult to navigate due to headings or structure, or otherwise has an issue that may impede the user's ability to accomplish the JTBD. 1. Based on the findings, **plan documentation improvements/additions**; include any documentation recommendations from the UX issue, and further, this may include: improvements to ensure clarity, conceptual accessibility to new users e.g. backlinks to more fundamental concepts, fix outdated screenshots, reorganize information for improved use/browsing, or resolve any process/content gaps or errors. Work with SMEs from the stage group as needed, and determine best content reviewer(s) from Product, Engineering, or UX, depending on the content. 1. **Ask questions of and share plans with the Product Designer**, for review. 1. **Implement doc changes** and share for review(s). \* Improvements in search results and UI-based doc links may need to wait until documentation improvements are made, per item 3. ## Current JTBDs Identified | Stage | Tech Writer | Job to be Done (JTBD) | Q2 UX Experience Score | TW issue | UX Evaluation issue | UX recommendations issue | Clarity of doc needs | Potential doc OKR work | Notes re doc OKR | | --------- | --------- | ---------------------------------------------------- | -------------------- | ------------------------------------------------------ | ------------------------------------------------------ | ------------------------------------------------------ | -------------------- | ------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------- | | Configure | @eread | Add my existing Kubernetes cluster | C- | https://gitlab.com/gitlab-org/gitlab/issues/31688 | https://gitlab.com/groups/gitlab-org/-/epics/1380 | https://gitlab.com/groups/gitlab-org/-/epics/1382#note_198461475 | A | https://gitlab.com/gitlab-org/gitlab/issues/30577<br>https://gitlab.com/gitlab-org/gitlab/issues/30575 | | | Create | @marcel.amirault* | Create a Merge Request | C/D (desktop/mobile) | https://gitlab.com/gitlab-org/gitlab/issues/31708 | https://gitlab.com/gitlab-org/gitlab-design/issues/441 | https://gitlab.com/gitlab-org/gitlab-design/issues/444 | D | Link from UI to MR Approvals doc page<br>Ensure the steps of the MR process are sufficiently documented | | | Monitor | @axil | Identify and troubleshoot performance issues | C | https://gitlab.com/gitlab-org/gitlab/issues/31709 | https://gitlab.com/gitlab-org/gitlab/issues/11713 | | C | Ensure processs of setting up metrics page is clear | https://youtu.be/nUdSqrvWeiA?t=272 | | Plan | @rdickenson | Receive and configure Issue notifications and To Dos | D+ | https://gitlab.com/gitlab-org/gitlab/issues/31710 | https://gitlab.com/gitlab-org/gitlab-design/issues/450 | https://gitlab.com/gitlab-org/gitlab-design/issues/520 | D | When we "better educate..contextually" about what a To Do is, can link to docs | | | Release | @mattpennathe3rd* | Create a Release and update it | F | https://gitlab.com/gitlab-org/gitlab/issues/31711 | https://gitlab.com/gitlab-org/gitlab-design/issues/431 | https://gitlab.com/gitlab-org/gitlab-design/issues/505 | D- | Flesh out our releases page to show the current state of the feature; how to manage a release using the current features | https://docs.gitlab.com/ee/workflow/releases.html | | Release | @marcia | Deploy to Gitlab Pages | C | https://gitlab.com/gitlab-org/gitlab/issues/31712 | https://gitlab.com/gitlab-org/gitlab-design/issues/412 | https://gitlab.com/gitlab-org/gitlab-design/issues/513 | A | Clear doc issue | https://gitlab.com/gitlab-org/gitlab/issues/30647 | \* Not the technical writer for the stage/group; covering to share the workload. *More JTBDs may be added as they are further developed or doc needs are identified. Suggestions welcome.* **To Do** * [x] @mikelewis to take first pass at reviewing/selecting JTBDs. * [x] @mikelewis to create issues or epics for each selected JTBD.