GitLab Design issueshttps://gitlab.com/gitlab-org/gitlab-design/-/issues2022-11-22T19:20:24Zhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1785Record or host 5 UI redesign sessions2022-11-22T19:20:24ZJeremy ElderRecord or host 5 UI redesign sessions## Purpose
Take a few sections of the product UI and redesign them with an overall goal of UI polish that:
- Removes visual clutter from the UI (think lines, bordered boxes and containers, nesting, too many icons, etc.).
- Applies [Paj...## Purpose
Take a few sections of the product UI and redesign them with an overall goal of UI polish that:
- Removes visual clutter from the UI (think lines, bordered boxes and containers, nesting, too many icons, etc.).
- Applies [Pajamas](https://design.gitlab.com/) guidelines (component use, spacing, typography, etc.).
- Applies [Gestalt Principles](https://webflow.com/blog/gestalt-principles-of-design) (our very own @timnoah's work is featured in the link :wink:).
- Considers the [5 dimensions of interaction design](https://www.interaction-design.org/literature/topics/interaction-design).
- Considers responsive layout and content malleability.
- Considers accessibility and the "content behind the content."
- Considers i18n and universal design.
Note that this isn't a prescriptive exercise — it's conceptual, iterative, and directionally aimed at applying a consistent design process to GitLab's UI. If any north star concepts :sparkles: come of it that we want to consider, it's an added bonus!
**The main outcome is that as designers we'd each be aware of ways to improve the experiences we're responsible for by leveraging a shared design direction and applying the same principles. To put it another way — UI polish that leads to better UX.**
## Sessions
- Each session will be recorded and participation will be opt-in based on scheduling availability.
- I'll have a subject to work on and spend some preliminary time working through ideas so that during the session I can more quickly recreate it and walk through my thinking and what's being applied. I'll be designing in Figma, so this'll also demonstrate my process there.
- Recordings will be posted to the Unfiltered Youtube channel.
* [ ] UI redesign session 1: Boards
* [ ] UI redesign session 2: Keys and Tokens
* [ ] UI redesign session 3: On-call Schedules/Escalation Policies
* [ ] UI redesign session 4: Profile
* [ ] UI redesign session 4: TBDJeremy ElderJeremy Elder2022-01-31https://gitlab.com/gitlab-org/gitlab-design/-/issues/1783UX coverage for Alexis Ginsberg, Plan:Product Planning - December 6-22, 20212022-02-04T05:12:42ZAlexis GinsbergUX coverage for Alexis Ginsberg, Plan:Product Planning - December 6-22, 2021## Intent
This issue describes how broader group and team members are facilitating a Product Designer to take meaningful time away from work. The intent is that the designer isn't required to "catch-up" before and after [taking a well-d...## Intent
This issue describes how broader group and team members are facilitating a Product Designer to take meaningful time away from work. The intent is that the designer isn't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
List the priorities that the responsible backups need to cover. Backups can be another product designer, your design manager, or product manager.
Responsibilities include reviewing merge requests, responding to UX related questions or providing feedback related to inflight development work, responding to Slack inquiries. [See all responsibilities in the Handbook][responsibilities]
| Priority | Responsibility | Context Link | Primary backup DRI | Secondary backup DRI |
| ----------------- | -------------------- | ------------------ | ----------- | --------- |
| [![Priority badge](https://img.shields.io/badge/Priority-High-red.svg)](https://shields.io/)` | Reviewing merge requests |As needed | @hollyreynolds | @cdybenko | @badnewsblair |
| [![Priority badge](https://img.shields.io/badge/Priority-Medium-orange.svg)](https://shields.io/) |Reviewing and overseeing hierarchy work |[Issue](https://gitlab.com/gitlab-org/gitlab/-/issues/340844/), [Survey](https://gitlab.com/gitlab-org/ux-research/-/issues/1695) | @cdybenko | @badnewsblair |
| [![Priority badge](https://img.shields.io/badge/Priority-Low-green.svg)](https://shields.io/) |Answering urgent Plan questions |As needed | @cdybenko | @badnewsblair |
|[![Priority badge](https://img.shields.io/badge/Priority-Low-green.svg)](https://shields.io/) | Answering urgent engineering & implementation questions |As needed| @donaldcook , @johnhope | Johnald :tm: |
| [![Priority badge](https://img.shields.io/badge/Priority-Low-green.svg)](https://shields.io/) | Fielding urgent copy questions| As needed| @msedlakjakubowski ||
## :muscle: Coverage Tasks
Include specific issue links for tasks to be completed.
- [ ] `Review hierarchy implementation` - https://gitlab.com/gitlab-org/gitlab/-/issues/340844 - @cdybenko
- [ ] `Finalize hierarchy survey` - https://gitlab.com/gitlab-org/ux-research/-/issues/1695 - @cdybenko with support from Anne as needed if she has capacity
- [ ] Finalize relationship widget requirements and issue documentation - @cdybenko
## 🚙 Parked tasks
Larger design responsibilities that aren't moving forward until I return, such as creating a prototype or planning/conducting research.
- Other work item type initiatives
- OKR work
## :white_check_mark: Issue Tasks
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [x] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Add any relevant references including direction pages, ux handbook pages, etc
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [x] Assign to anyone with a specific task or responsibility assigned to them
- [x] Share this issue in your section, stage and group Slack channels
- [x] Ensure your PTO Ninja auto-responder points team members to this issue
### :x: Closing Tasks
- [ ] Assign back to yourself and remove others
- [ ] Review any Retrospective items with your counterparts and manager
<!-- Do not remove the items below -->
[responsibilities]: https://about.gitlab.com/job-families/engineering/product-designer/
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1763📋 Tracking Issue: UX OKRs for Secure & Protect and Configure & Monitor UX Tea...2022-02-01T00:51:46ZJustin Mandell📋 Tracking Issue: UX OKRs for Secure & Protect and Configure & Monitor UX Teams - FY22-Q4<!--
Title should be: Tracking Issue: UX OKRs for {{Group}} - FY{{YY}}-Q{{quarter number}}
(e.g. “Tracking Issue: UX OKRs for CI/CD - FY22-Q1”)
See example issues:
https://gitlab.com/gitlab-org/ci-cd-ux/-/issues/22
https://gitlab.com...<!--
Title should be: Tracking Issue: UX OKRs for {{Group}} - FY{{YY}}-Q{{quarter number}}
(e.g. “Tracking Issue: UX OKRs for CI/CD - FY22-Q1”)
See example issues:
https://gitlab.com/gitlab-org/ci-cd-ux/-/issues/22
https://gitlab.com/gitlab-org/ci-cd-ux/-/issues/21
-->
# Overview
Hey y'all :wave:!
Here's our new issue to track our progress, discuss, and collaborate on the current [UX department OKRs](https://app.ally.io/teams/39450/objectives?tab=0&time_period_id=135092&viewId=208933) (Ally :link:). This fiscal quarter will run from `2021-01-11` through `2022-01-31`. Please leave a comment if you have any questions! 🙌
## Issue tasks
### :o: Opening Tasks
- [x] Manager: Assign to yourself and your design team.
- [x] Title the issue `Tracking Issue: UX OKRs for {{Group}} - FY{{YY}}-Q{{quarter number}}`
- [x] Fill in the KRs based on the UX Department OKRs.
- [x] Assign to team members with a specific task or responsibility assigned to them, @ them in the checklist.
- [x] Share this issue in your Slack channels and with the team members during your next 1:1.
### :x: Closing Tasks
- [x] Assign back to yourself and remove others.
- [x] Review any Retrospective items with your team.
---
## Let's Contribute!
The list below only shows KRs where our team input is required. Once you complete a KR, please check your name off the list.
### 1. [Make our UX department a "best place to work" for designers, researchers, and technical writers](https://app.ally.io/objectives/1610628?time_period_id=135092)(Ally :link:)
Key results: [Help build internal empathy for users by creating and piloting an EdCast training that shows users interacting (and struggling) with our product](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12616)
:exclamation: This KR has its own tracking checklist within the above Issue, please use it to track and discuss it.
### 2. [Increase SUS by enhancing product learnability and conducting more consistent MR Reviews](https://app.ally.io/objectives/1610638?time_period_id=135092)(Ally :link:)
[Help drive Category Maturity forward by preparing JTBDs for Q1 planned maturity](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12492)
:exclamation: This KR has its own tracking checklist within the above Issue, please use it to track and discuss it.
Affected teams:
* Secure: DAST
* Secure: Dependency Scanning
[Increase the total number of MR Reviews completed by the Product Design team from 156 per month to 173 per month (10%)](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12494)
This KR affects everyone on our team but is associated with UX/UI MR reviews, not handbook updates and the like. I know some teams don't have a lot of group work to review due to engineering limitations but you should still be reviewing community contributions (see the Slack channel #ux-community-contributions). I suggest shooting for 1 or 2 a week. That said, as the quarter goes on we should start to see more engineering activity. Bottom line, try to make a conscious effort to increase UX/UI MR reviews this quarter. If you've noticed that your engineering counterparts aren't adding you as a reviewer and you need help rectifying that, please let me know.
### 3. [Improve product usability by achieving goals for MR widget migration and Learnability](https://app.ally.io/objectives/1651625?time_period_id=135092)(Ally :link:)
[Evaluate experiences of 7 product categories to improve learnability](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12593)
:exclamation: This KR has its own tracking checklist within the above Issue, please use it to track and discuss it.
Affects:
* @mfangman
<!--
If a KR has its own tracking table, skip the checkboxes above and add the following comment:
❗ This KR has its own tracking table within the above Issue, please use it to track and discuss it.
-->Justin MandellJustin Mandell2022-01-28https://gitlab.com/gitlab-org/gitlab-design/-/issues/1738UX Showcase - Hosted by the Digital Experience team2023-10-11T14:38:52ZMarcel van Remmerdenmvanremmerden@gitlab.comUX Showcase - Hosted by the Digital Experience teamOver the recent milestones there have been more and more touch points between the Digital Experience and the UX team, e.g. on the [CE vs. EE marketing page](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12380) or the [design prin...Over the recent milestones there have been more and more touch points between the Digital Experience and the UX team, e.g. on the [CE vs. EE marketing page](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12380) or the [design principles](https://gitlab.com/gitlab-com/marketing/corporate_marketing/corporate-marketing/-/issues/5020). When chatting with @sunjungp about how we can connect our two departments better, we came up with one potential idea: **We could have the Digital Experience team take over one of our upcoming UX showcase sessions**. This would not only help us see directly what they work on and how they work, but also get to know the team members and establish a first connection, so that it would be easier afterwards to reach out to each other.
I already checked with @mpreuss22 who was very supportive of the idea and would love to see his team present their work, but also mentioned that we might need to choose a date a bit further into the future as the team is currently very busy.
@gitlab-com/gitlab-ux/managers How are you all feeling about this proposal as a first step, and is there anything specific we should be taking into account?https://gitlab.com/gitlab-org/gitlab-design/-/issues/1724Follow-up: Product Design Manager responsibility feedback2021-10-08T20:47:22ZValerie KarnesFollow-up: Product Design Manager responsibility feedbackFollow-up discussion based on comments related to the [Product Design Manager's responsibilities](https://about.gitlab.com/job-families/engineering/product-design-management/#product-design-manager) from ([adding PDMs to Product Dev Flow...Follow-up discussion based on comments related to the [Product Design Manager's responsibilities](https://about.gitlab.com/job-families/engineering/product-design-management/#product-design-manager) from ([adding PDMs to Product Dev Flow](https://gitlab.com/gitlab-com/www-gitlab-com/-/merge_requests/88171#note_673797322)). The issue is intended to bring clarity to current expectations and consider iterations (if needed).
/cc @clennevilleMarcel van Remmerdenmvanremmerden@gitlab.comValerie KarnesJacki Bauerjbauer@gitlab.comJustin MandellBlair ChristopherMarcel van Remmerdenmvanremmerden@gitlab.comhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1573UX Coverage for Alexis Ginsberg from 2021-03-29 until 2021-04-092021-05-31T10:50:28ZAlexis GinsbergUX Coverage for Alexis Ginsberg from 2021-03-29 until 2021-04-09## Intent
This issue describes how broader group and team members are facilitating a Product Designer to take meaningful time away from work. The intent is that the designer isn't required to "catch-up" before and after [taking a well-d...## Intent
This issue describes how broader group and team members are facilitating a Product Designer to take meaningful time away from work. The intent is that the designer isn't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
List the priorities that the responsible backups need to cover. Backups can be another product designer, your design manager, or product manager.
Responsibilities include reviewing merge requests, responding to UX related questions or providing feedback related to inflight development work, responding to Slack inquiries. [See all responsibilities in the Handbook][responsibilities]
| Priority | Responsibility | Context Link | Primary backup DRI | Secondary backup DRI |
| ----------------- | -------------------- | ------------------ | ----------- | --------- |
| [![Priority badge](https://img.shields.io/badge/Priority-Medium-orange.svg)](https://shields.io/)` | `Reviewing merge requests` | [MR list](https://gitlab.com/groups/gitlab-org/-/merge_requests?scope=all&utf8=%E2%9C%93&state=opened&label_name[]=group%3A%3Aproduct%20planning&label_name[]=UX) | @hollyreynolds | @mikelong |
|[![Priority badge](https://img.shields.io/badge/Priority-Low-green.svg)](https://shields.io/) | `Research questions or initiatives` | [KR](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10463), [Metadata](https://gitlab.com/groups/gitlab-org/-/epics/5214) | @alasch | @mikelong |
| [![Priority badge](https://img.shields.io/badge/Priority-Medium-orange.svg)](https://shields.io/) | `General Plan questions` | 🔮 | @cdybenko | @hollyreynolds |
## :muscle: Coverage Tasks
Include specific issue links for tasks to be completed.
- [ ] `Continuing research initiatives` - https://gitlab.com/groups/gitlab-org/-/epics/5634 - @alasch
- [ ] `Boards loading states` - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57661 - @jeldergl @jareko If this would be of interest to you, Florie could use some collaboration here. @cdybenko if you could be DRI here it would be great though.
- [ ] `Update performance bar background color to use the color variables` - https://gitlab.com/gitlab-org/gitlab/-/merge_requests/52775#note_541037198 @pedroms 🙇
- [ ] Reduce width of "color chip swatches" in the label dropdown/picker` - Reduce width of "color chip swatches" in the label dropdown/picker - https://gitlab.com/gitlab-org/gitlab/-/issues/325889#note_541036557 @jeldergl
- [ ] `Epic board support` - https://gitlab.com/groups/gitlab-org/-/epics/5079 @cdybenko
## 🚙 Parked tasks
Larger design responsibilities that aren't moving forward until I return, such as creating a prototype or planning/conducting research.
- [ ] `Synthesis of JTBD KRs, feel free to play with these though` - https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/10463
- [ ] Wrap up issue board improvements
https://gitlab.com/groups/gitlab-org/-/epics/4287
## :book: References
Here are some references for how I and my group generally works:
- [Group Process Handbook Page](https://about.gitlab.com/handbook/product/categories/plan/)
- My Product Manager friends: @cdybenko @mjwood @gweaver
- My Design peer in Plan :dancer: @hollyreynolds
- EM extraordinaires @donaldcook @johnhope
## :white_check_mark: Issue Tasks
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [x] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Add any relevant references including direction pages, ux handbook pages, etc
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [x] Assign to anyone with a specific task or responsibility assigned to them
- [x] Share this issue in your section, stage and group Slack channels
- [x] Ensure your PTO Ninja auto-responder points team members to this issue
### :x: Closing Tasks
- [ ] Assign back to yourself and remove others
- [ ] Review any Retrospective items with your counterparts and manager
<!-- Do not remove the items below -->
[responsibilities]: https://about.gitlab.com/job-families/engineering/product-designer/
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offAlexis GinsbergAlexis Ginsberghttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1547Retro on the current state of MR design reviews with product designers2021-10-04T13:52:53ZAlexis GinsbergRetro on the current state of MR design reviews with product designers## Goal
Get a baseline on how designers are feeling about the current state of MR design reviews. Most importantly, what are the biggest pain points?
This information will enable us to improve our guidelines for how designers do MR rev...## Goal
Get a baseline on how designers are feeling about the current state of MR design reviews. Most importantly, what are the biggest pain points?
This information will enable us to improve our guidelines for how designers do MR reviews.
## Method
To gather this information, we will run a short anonymous survey targeted at Product Designers.
## Results
- [🕊 Dovetail project](https://dovetailapp.com/projects/B4nnVoUJ25a7C9mfJSVzd/insights)
- [:sparkles: Insights](https://dovetailapp.com/projects/B4nnVoUJ25a7C9mfJSVzd/insights/present)
- [:tv: Insights walkthrough video](https://youtu.be/H9P_oJ3ICvw)
- [📝 Qualtrics survey](https://gitlab.eu.qualtrics.com/surveys/SV_eY7x1u0rPv90uUu/edit?SurveyID=SV_eY7x1u0rPv90uUu)14.3Pedro Moreira da SilvaPedro Moreira da Silvahttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1545Pilot | GitLab Design Talks: Career Development - From IC to Leadership2022-08-05T09:36:50ZRayana Verissimorverissimo@gitlab.comPilot | GitLab Design Talks: Career Development - From IC to Leadership## What and why
Create a series of recorded discussions looking into career development through the lens of ICs that transitioned to Leadership in the UX department. The goal is to showcase examples of the type of work Staff and Manager...## What and why
Create a series of recorded discussions looking into career development through the lens of ICs that transitioned to Leadership in the UX department. The goal is to showcase examples of the type of work Staff and Managers do, how the roles differ from each other and others while being transparent that moving into those roles are not exclusive to responsibilities performed by individuals.
We will look at career development from a number of different perspectives in 15-20m conversations. Videos will be recorded and added to GitLab Unfiltered.
By speaking about our trajectories, we also want to encourage managers to look for opportunities to work with ICs in their growth and development that may include things besides a change in title--like education, conferences, special projects, internal and external mentorship programs, etc.
## Goals
- Give other members of the UX Department clarity on Staff and Design Manager roles and responsibilities.
- Transparently share the trajectories for folks that transitioned from IC to Leadership roles.
- Give insight on how their career development looked like.
- (stretch) Update the handbook and job families pages for Staff and Product Design Manager.
## Discussion topics
- How leadership is not about your title and can come from any level.
- Design background and career path from IC to Leadership.
- What are your current responsibilities? What do you work on? What does a regular week look like?
- What are the challenges of your current role?
- Why did you decide to move into a Leadership role? How did you come to that conclusion?
- What internal and external learning and development opportunities did you seek? How did those influence your career?
- How to navigate the transition/challenges of a new role?
- What areas of your work or personal development are you hoping to explore further?
### Slack channel
`#ux-talks-leadership-pilot`
### Participants
- @rayana - https://youtu.be/Wgw8biVyay0
- @tauriedavis - https://www.youtube.com/watch?v=hgSAlh1JdE8
- @pedroms - https://www.youtube.com/watch?v=wN_CFsPL08M
- @mvanremmerden - https://youtu.be/B9SBZPeT6do
- @loriewhitaker - https://youtu.be/GoriQSbQqNARayana Verissimorverissimo@gitlab.comRayana Verissimorverissimo@gitlab.comhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1461KR2: Experts put together accessibility outline of improvements that are rele...2022-11-22T19:51:45ZTaurie DavisKR2: Experts put together accessibility outline of improvements that are relevant to GitLab => 100%[FY21-Q4 UX Department: Foundations SubTeam OKR](https://gitlab.com/groups/gitlab-org/-/epics/5234)
Objective: Develop a department of accessibility advocates and experts to help implement broad, impactful enhancements that benefit all ...[FY21-Q4 UX Department: Foundations SubTeam OKR](https://gitlab.com/groups/gitlab-org/-/epics/5234)
Objective: Develop a department of accessibility advocates and experts to help implement broad, impactful enhancements that benefit all users.
**KR2: Experts put together accessibility outline that is relevant to GitLab**
Compile an accessibility outline that is relevant to GitLab and stays true to our "Everyone can contribute" ethos by improving embedded accessibility standards.
- [x] Compile notes from https://gitlab.com/groups/gitlab-org/-/epics/5235, creating epics/issues to capture areas of improvements for GitLab. Add created issues to https://gitlab.com/groups/gitlab-org/-/epics/5854 and mark off comments in the Deque course issues using :white_check_mark: so we don't duplicate work.
---
## Action checklist
Once all relevant comments under the **How can this be applied to GitLab** section for each course have been reviewed and added to the [A11y actions spreadsheet](https://docs.google.com/spreadsheets/d/1GwI2N1NhOB3ISJJgy-n8fDkrQq91_qQks3yV1O3Ix2A/edit?usp=sharing), mark as complete.
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1462
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1463
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1464
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1465
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1466
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1467
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1468
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1469
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1470
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1471
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1472
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1473
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1474
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1475
* [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/158613.12Taurie DavisJarek OstrowskiJeremy ElderTaurie Davis2021-04-27https://gitlab.com/gitlab-org/gitlab-design/-/issues/1427Navigation bar consolidation exploration2022-03-23T15:43:07ZMichael LeNavigation bar consolidation explorationThis issue is for feedback for designs going into solution validation for consolidation of the top nav https://gitlab.com/gitlab-org/ux-research/-/issues/1169
## Proposed design for solution validation
| Updated top nav | With menu |
|...This issue is for feedback for designs going into solution validation for consolidation of the top nav https://gitlab.com/gitlab-org/ux-research/-/issues/1169
## Proposed design for solution validation
| Updated top nav | With menu |
| ------ | ------ |
| ![mini-projects](/uploads/391fd06dc5376a37152d1d3486247140/mini-projects.png) | ![mini-projects-active](/uploads/657ada6e470dcdfb2b7338498e9e911e/mini-projects-active.png) |
### Videos
Context walkthrough by Michael Le: https://youtu.be/VnSVg0xDjE8
| Prototype video |
| ------ |
| ![menu-top-nav-clickthrough](/uploads/a45f43b11d4f2e9a2bbc4c06b0de56b9/menu-top-nav-clickthrough.mp4) |
- **:joystick: Prototype** - [Experience the menu](https://www.figma.com/proto/XW35RsB1O2eLBMFyAwCzqN/Solution-validation-Navigation-bar-consolidation-1169?node-id=4%3A19&scaling=min-zoom)
### 📣 Feedback welcomed
Looking for feedback around
- General style (especially selected "stage/feature")
- Is this proposal missing any use case or scenarios that would be negatively impacted by this change?
**Where to give feedback**
- **Designs in issue** - start here https://gitlab.com/gitlab-org/gitlab-design/-/issues/1427/designs/projects.png
- **Figma feedback page** - [UX Review - 20201207](https://www.figma.com/file/54ek3zv3Zjjsrl8RP3u5ot/Navigation-bar-consolidation-exploration-1427?node-id=479%3A290)
## Issues that influenced direction
- Navigation vision ideas (Manage:Analytics POV) https://gitlab.com/gitlab-org/gitlab/-/issues/255325
- Navigation: Single project/group/more selection experience MVC https://gitlab.com/gitlab-org/gitlab/-/issues/260298
- Improve the ability to search for settings using navbar dropdown https://gitlab.com/gitlab-org/gitlab/-/issues/241317
- Navigation & sidebar north star exploration https://gitlab.com/gitlab-org/gitlab-design/-/issues/1424/
- Improve navigation between projects within a group/subgroup https://gitlab.com/gitlab-org/gitlab/-/issues/22926
## Hypotheses
#### 1. Combining Project, Groups, and More will help speed up selection of context
| Current | Proposal |
| ------ | ------ |
| ![image](/uploads/b664ac8267c44f79421e31d470c582fa/image.png) | ![image](/uploads/81e468a8bf4d35b65425417afa046187/image.png) |
#### 2. Recently visited is useful as a navigation pattern for getting back to where you need to do work
#### 3. "Menu" is not needed for users to discover where to change between projects
#### 4. When switching projects we keep the same context instead of taking them to the homepage
![image](/uploads/2019435c21326101ad91c7b09fc58ce6/image.png)
## Out of scope of validation
These are things that were considered to be in the solution validation but they require a separate session to give it the time it deserves
- By putting more emphasis on `+` users can find the button when they need to create something in GitLab
Out of scope: What should go in the list depending on context should be handled in a separate solution validation
- Combining menu selection and page context will help users understand where they are at an where they can go
- By limiting search areas to one centralized position we are reducing the decision for users of where to search to between 3 areas now (Projects, Groups, and Global search)
- Tidy up and simplify the "+" menu in the top nav bar https://gitlab.com/gitlab-org/gitlab/-/issues/284092Michael LeMichael Lehttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1394Pajamas contributions over time2021-05-27T23:17:37ZAmelia BauerlyPajamas contributions over timeHow have contributions to Pajamas trended over time?
Anecdotally, it seems like there are fewer MRs to review for Pajamas docs than there have been, in past. But, is this accurate? Are there really fewer people, overall, contributing to...How have contributions to Pajamas trended over time?
Anecdotally, it seems like there are fewer MRs to review for Pajamas docs than there have been, in past. But, is this accurate? Are there really fewer people, overall, contributing to Pajama than there were previously?
This issue aims to do the following:
- Figure out if we track number of discrete contributors to Pajamas
- If we do, figure out how those contributions are trending, over time
If we do see a downward trend, we could consider exploring why that might be the case. We could, for example, create a survey for the product design team and get a pulse on things like: do you contribute regularly to Pajamas? If not, why not?
The larger goal would be to try to address any barrier to contributing that we discover so that people feel more willing/able to contribute to Pajamas :)13.9Amelia BauerlyAmelia Bauerlyhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1391Experience Recommendations - Verify:Pipeline Authoring FY21Q3 - Pipeline auth...2022-09-22T09:50:11ZNadia Sotnikovansotnikova@gitlab.comExperience Recommendations - Verify:Pipeline Authoring FY21Q3 - Pipeline authoring experience<!--
Title should be: Experience Recommendations - {{Stage Group}} FY{{YY}}-Q{{quarter number}} - {{Title or Description of the Evaluated Workflow / JTBD}}
(e.g. “Experience Recommendations - Create:Source Code FY21-Q1 - Obtaining scree...<!--
Title should be: Experience Recommendations - {{Stage Group}} FY{{YY}}-Q{{quarter number}} - {{Title or Description of the Evaluated Workflow / JTBD}}
(e.g. “Experience Recommendations - Create:Source Code FY21-Q1 - Obtaining screenshots from testing artifacts”)
-->
- **UX Scorecard Part 1**: https://gitlab.com/gitlab-org/gitlab-design/-/issues/1376
- **Resulting Recommendations**: {{when ready, add a link to your recommendations epic}}
## Experience Recommendations Checklist
[Learn more about UX Scorecards](https://about.gitlab.com/handbook/engineering/ux/ux-scorecards/)
1. [x] Add this issue to the stage group epic for the corresponding quarter's UX scorecards.
1. [x] Brainstorm opportunities to fix or improve areas of the experience.
- Use the findings from the Emotional Grading scale to determine areas of immediate focus. For example, if parts of the experience received a “Negative” Emotional Grade, consider addressing those first.
1. [x] Create an issue for each recommendation. Alternatively, you can create a separate epic to hold all your recommendations. Add a `UX scorecard-rec` label to every issue or epic for traceability. Link to the epic or issues here.
1. [x] Think iteratively, and create dependencies where appropriate, remembering that sometimes the order of what we release is just as important as what we release.
- If you need to break recommendations into phases or over multiple milestones, create multiple epics and use the [Category Maturity Definitions](https://about.gitlab.com/direction/maturity/) in the title of each epic: **Minimal, Viable, Complete, or Lovable**.
## Recommendations
- Make the CI feature more discoverable, for example recommend it to maintainers of a project. https://gitlab.com/gitlab-org/gitlab/-/issues/280828
- Explore ways to make the distinction between DevOps and CI/CD more clear and explore ways to align the user experience. https://gitlab.com/gitlab-org/gitlab/-/issues/280572
- Provide more guidance on how to set up CI, what are the steps, what are the requirements https://gitlab.com/gitlab-org/gitlab/-/issues/269755, https://gitlab.com/gitlab-org/gitlab/-/issues/272557
- Provide at least a basic template to start with, as opposed to a blank page https://gitlab.com/gitlab-org/gitlab/-/issues/269755
- Provide more context about the templates, make them easier to browse, search, and preview, communicate the value of each template https://gitlab.com/gitlab-org/gitlab/-/issues/267009 https://gitlab.com/gitlab-org/gitlab/-/issues/259675 https://gitlab.com/gitlab-org/gitlab/-/issues/28049
- Make relevant documentation accessible from within the UI https://gitlab.com/gitlab-org/gitlab/-/issues/273203
- Make it easier to understand whether a runner is set up, and if not, how to set it up, and what are the options available
- Provide recommendations on how a template may need to be customized for any given project
- Provide immediate pipeline status feedback once CI configuration has been saved https://gitlab.com/gitlab-org/gitlab/-/issues/280829
- Make it easier to see the pipeline progress and job logs from the editor page https://gitlab.com/gitlab-org/gitlab/-/issues/280829
- Make a link to the deployed application easily discoverableNadia Sotnikovansotnikova@gitlab.comNadia Sotnikovansotnikova@gitlab.comhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1373UX Showcase Schedule: Optimize presenter rotation for sections that have fewe...2022-07-13T14:43:25ZMike LongUX Showcase Schedule: Optimize presenter rotation for sections that have fewer designersWe were struggling with the frequency and cadence of UX Showcase rotations when some sections have fewer designers than other sections.
Let's define upcoming rotations before 2020-11-11 (the last rotation on [the schedule](https://abou...We were struggling with the frequency and cadence of UX Showcase rotations when some sections have fewer designers than other sections.
Let's define upcoming rotations before 2020-11-11 (the last rotation on [the schedule](https://about.gitlab.com/handbook/engineering/ux/ux-department-workflow/ux-showcase/#schedule))Mike LongMike Long2020-10-28https://gitlab.com/gitlab-org/gitlab-design/-/issues/1351Sec/Def - Config/Monitor Async Design Review Pilot Retro2020-12-01T21:01:50ZJustin MandellSec/Def - Config/Monitor Async Design Review Pilot RetroThis is an async retrospective for our month-long pilot of trying async design reviews that started on 2020-09-02 to 2020-10-22.
Please feel free to honestly describe your thoughts and feelings about this pilot as you go or at the end o...This is an async retrospective for our month-long pilot of trying async design reviews that started on 2020-09-02 to 2020-10-22.
Please feel free to honestly describe your thoughts and feelings about this pilot as you go or at the end of the pilot.
(If there is something you are not comfortable sharing, message me directly. But note that 'Emotions are not only allowed in retrospectives, but they should also be encouraged', so I'd love to hear from you here if possible.)
@gitlab-com/gitlab-ux/secure-defend-ux @gitlab-com/gitlab-ux/configure-monitor-ux13.6Justin MandellJustin Mandell2020-11-13https://gitlab.com/gitlab-org/gitlab-design/-/issues/1339UX Coverage for Dimitrie Hoekstra from 2020-09-07 until 2020-10-022021-02-19T09:38:41ZDimitrie HoekstraUX Coverage for Dimitrie Hoekstra from 2020-09-07 until 2020-10-02## Intent
This issue describes how broader group and team members are facilitating a Product Designer to take meaningful time away from work. The intent is that the designer isn't required to "catch-up" before and after [taking a well-d...## Intent
This issue describes how broader group and team members are facilitating a Product Designer to take meaningful time away from work. The intent is that the designer isn't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
List the priorities that the responsible backups need to cover. Backups can be another product designer, your design manager, or product manager.
Responsibilities include reviewing merge requests, responding to UX related questions or providing feedback related to inflight development work, responding to Slack inquiries. [See all responsibilities in the Handbook][responsibilities]
**Note:** All my issues can also be seen at [my personal board](https://gitlab.com/groups/gitlab-org/-/boards/1381906)!
| Priority | Responsibility | Context Link | Primary backup DRI | Secondary backup DRI |
| ----------------- | -------------------- | ------------------ | ----------- | --------- |
| [![Priority badge](https://img.shields.io/badge/Priority-High-red.svg)](https://shields.io/) | General UX Coverage. Responding to UX related questions or providing feedback related to inflight development work | <ul><li>[13.4 planning issue](https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/8)</li><li>[13.5 planning issue](https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/13)</li></ul> | @rayana (week 1) & @icamacho (week 2-4) | @nudalova |
| [![Priority badge](https://img.shields.io/badge/Priority-Medium-orange.svg)](https://shields.io/) | Attending weekly meetings | <ul><li>[PD weekly](https://docs.google.com/document/d/1OvOZRYIvCkR5xLvjFYoIvdy_T7cGGiu7Efb3Be7nbdk/edit)</li></ul> | @nudalova | |
| [![Priority badge](https://img.shields.io/badge/Priority-Medium-orange.svg)](https://shields.io/) | Responding to Slack inquiries | | @rayana (week 1) & @icamacho (week 2-4) | @nudalova |
| [![Priority badge](https://img.shields.io/badge/Priority-Low-green.svg)](https://shields.io/) | Reviewer coverage | [GitLab-svg](https://gitlab.com/gitlab-org/gitlab-svgs) | @jeldergl | @andyvolpe |
<!---
Optionally, you can use the following badges:
- HIGH: [![Priority badge](https://img.shields.io/badge/Priority-High-red.svg)](https://shields.io/)
- MEDIUM: [![Priority badge](https://img.shields.io/badge/Priority-Medium-orange.svg)](https://shields.io/)
- LOW: [![Priority badge](https://img.shields.io/badge/Priority-Low-green.svg)](https://shields.io/)
--->
## :muscle: Coverage Tasks
Include specific issue links for tasks to be completed.
- [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/218139 ~"Release::P1" | `Align with ~"Technical Writing". Review ~"workflow::planning breakdown". Review merge request.` @rayana (week 1) & @icamacho (week 2-4)
- [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/35404 ~"Release::P1" | `Check design for last details with engineering and ~"Technical Writing". Review merge request` @rayana (week 1) & @icamacho (week 2-4)
- [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/235747 ~"Release::P2" | `Finish ~"workflow::planning breakdown". Consider pushing forward follow ups #243498 and #223084. Review merge request.` @rayana (week 1) & @icamacho (week 2-4)
- [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/37679 | `Align with ~"Technical Writing". Finishing touch on the design if needed. Review merge request.` @rayana (week 1) & @icamacho (week 2-4)
- [x] https://gitlab.com/gitlab-org/gitlab-design/-/issues/1343 | `Align with PM and adjust designs as needed` @rayana
- [ ] https://gitlab.com/gitlab-org/gitlab/-/issues/228650 | `Push design forward with engineering` @rayana (week 1) & @icamacho (week 2-4)
Other items that will require only `merge request reviews`:
- [ ] Follow up: Improve usability of rolling out feature flags env by env (https://gitlab.com/gitlab-org/gitlab/-/issues/235747) ~"Release::P1"
- [ ] See which commits and pipelines are run in the fork project ref VS the parent project ref (https://gitlab.com/gitlab-org/gitlab/-/issues/225513) ~"Release::P3"
- [ ] Remove repeated legend deployboard (https://gitlab.com/gitlab-org/gitlab/-/issues/219721)
- [ ] Missing tooltip for ReDeploy (https://gitlab.com/gitlab-org/gitlab/-/issues/222511)
- [ ] Update environments list page / deploy board to be more legible (https://gitlab.com/gitlab-org/gitlab/-/issues/223760)
- [ ] Allow for easier roll back from alerts page (https://gitlab.com/gitlab-org/gitlab/-/issues/232492)
- [ ] ~~Display a default list when adding environments to feature flag strategies (https://gitlab.com/gitlab-org/gitlab/-/issues/223084)~~ ~"workflow::verification"
- [ ] ~~Persist when dismissing FF will look different message (https://gitlab.com/gitlab-org/gitlab/-/issues/233092)~~ ~"workflow::verification"
- [x] Limit the number of feature flags per project (https://gitlab.com/gitlab-org/gitlab/-/issues/35132)
## 🚙 Parked tasks
Larger design responsibilities that aren't moving forward until I return, such as creating a prototype or planning/conducting research.
- [ ] `Will continue pushing forward A/B testing research after I am back from OOO` - https://gitlab.com/gitlab-org/ux-research/-/issues/676
- [ ] `Will continue pushing forward JTBD research after I am back from OOO` - https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/3
## :book: References
Here are some references for how I and my group generally works:
- [Group Process Handbook Page](https://about.gitlab.com/handbook/engineering/development/ci-cd/release/progressive-delivery/)
- [Group UX Vision Handbook Page](https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/release/progressive-delivery/)
- [Planning issues and epics](https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/release/progressive-delivery/#async-release-planning)
- [13.5 planning issue](https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/13)
- [13.5 (for 13.6) needs weight issue](#) TBD
- [13.6 planning issue](https://gitlab.com/gitlab-org/ci-cd/progressive_delivery/-/issues/22)
- [Planning process guide](https://about.gitlab.com/handbook/engineering/development/ci-cd/release/progressive-delivery/planning.html)
- [Stage + department OKRs](https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/release/progressive-delivery/#okrs)
- [Personal board where I manage my in progress, up next, and stand-by issues](https://about.gitlab.com/handbook/engineering/development/ci-cd/release/progressive-delivery/)
## :white_check_mark: Issue Tasks
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [x] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Add any relevant references including direction pages, ux handbook pages, etc
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [x] Assign to anyone with a specific task or responsibility assigned to them
- [x] Share this issue in your section, stage and group Slack channels
- [x] Ensure your PTO Ninja auto-responder points team members to this issue
- [x] List all issues that are already weighted/done so they can be included in the planning to fill in gaps (standby + weight)
- [x] List the current UX items for 13.4-13.6 and their status
### :x: Closing Tasks
- [x] Assign back to yourself and remove others
- [x] Review any Retrospective items with your counterparts and manager
<!-- Do not remove the items below -->
[responsibilities]: https://about.gitlab.com/job-families/engineering/product-designer/
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offDimitrie HoekstraDimitrie Hoekstrahttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1336Should we have UX initiative labels in order to track progress across teams?2020-09-24T20:58:28ZJacki Bauerjbauer@gitlab.comShould we have UX initiative labels in order to track progress across teams?Update: I rewrote the Growth team label descriptions to read "UX Team". [For example, Onboarding](https://gitlab.com/groups/gitlab-org/-/labels/13826339/edit). Anyone can add additional labels to track an effort across teams, so I'll clo...Update: I rewrote the Growth team label descriptions to read "UX Team". [For example, Onboarding](https://gitlab.com/groups/gitlab-org/-/labels/13826339/edit). Anyone can add additional labels to track an effort across teams, so I'll close this issue.
The Growth UX team uses labels to keep track of issues that are improving UX themes we've identified - https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/growth/#themes-and-focus-areas
I noticed that some other teams are doing something similar, with an almost duplicate label. Growth has ~"UX: Feature Discoverability" and there is also a ["UX Feature Discoverability" project label](https://gitlab.com/gitlab-org/gitlab/-/issues?label_name%5B%5D=UX+Feature+Discoverability).
I think as we focus on cross-team efforts around usability, 1st time experiences, navigation, other SUS improvements, it could be useful to track some UX themes across teams, not just Growth.
I think it would be fine to use the existing "UX: " labels that I created for the Growth team and just make everyone aware they can use them and add new themes. Anyone have any other thoughts on this? If people like this idea I can make relevant handbook updates and share with UX/Project teams.Jacki Bauerjbauer@gitlab.comJacki Bauerjbauer@gitlab.comhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1308FY21-Q3 UX OKRs for Configure & Monitor UX Team2020-10-26T22:51:59ZJustin MandellFY21-Q3 UX OKRs for Configure & Monitor UX Team### Overview
Let's use this issue to track our progress, discuss, and collaborate on the [UX department FY21-Q3 OKRs](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8363).
Also, please note that this effort is optional. Though w...### Overview
Let's use this issue to track our progress, discuss, and collaborate on the [UX department FY21-Q3 OKRs](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8363).
Also, please note that this effort is optional. Though we'd really, *really* like to accomplish this goal we're aware that there are many things that might happen to get in our way or other priorities we may have to address first. I only ask that we do our best to contribute :smile:
---
### Objective (Great Product): [Improve GitLab performance, quality, and velocity by making GitLab development Pajamas first](https://gitlab.com/groups/gitlab-com/-/epics/758)
**Key Result**: [Migrate Vue instances of buttons and pagination to Pajamas](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8365)
* [Buttons > Vue > Migrate GlDeprecatedButton instances to GlButton in GitLab](https://gitlab.com/groups/gitlab-org/-/epics/3459) - 162 issues in
* [Buttons > Vue > Migrate LoadingButton instances to GitLab UI’s GlButton in GitLab](https://gitlab.com/groups/gitlab-org/-/epics/3907) - 23 issues in total
* [Buttons > Vue > Migrate Bootstrap button to GitLab UI GlButton in vue components](https://gitlab.com/groups/gitlab-org/-/epics/3914) - 65 issues in total
##### Goal:
* Each team member should attempt to migrate around 6 Issues
* As a team that means we should strive for migrating around 18 Issues
- [x] Amelia (6 merged)
- [ ] Maria (0)
- [ ] Justin (3 not merged)
**Key Result**: [Migrate Vue instances of dropdowns, modals, and tabs](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8368)
* [Dropdowns > Vue > Migrate GlDeprecatedDropdown to GlDropdown in GitLab](https://gitlab.com/groups/gitlab-org/-/epics/4132) - 32
* [Dropdowns > Vue > Migrate Bootstrap dropdown to GitLab UI GlDropdown in vue components](https://gitlab.com/groups/gitlab-org/-/epics/4134) - 19
* [Modals > Vue > Migrate DeprecatedModal to GitLab UI Modal](https://gitlab.com/groups/gitlab-org/-/epics/3938) - 7 issues in total
* [Modals > Vue > Migrate DeprecatedModal2 to GitLab UI Modal](https://gitlab.com/groups/gitlab-org/-/epics/3939) - 14 issues in total
* [Modals > Vue > Migrate data-toggle modals to GitLab UI Modals in vue](https://gitlab.com/groups/gitlab-org/-/epics/3937) - 13 issues in total
* [Tabs > Vue > Migrate custom implementations to GlTabs in GitLab](https://gitlab.com/groups/gitlab-org/-/epics/3982) - 11 issues in total
##### Goal:
* Each team member should attempt to migrate around 2 Issue
* As a team that means we should strive for migrating around 6 Issues
- [x] Amelia (2 merged)
- [ ] Maria (0)
- [ ] Justin (0)
**Key Result**: [Migrate Vue instances of popovers and tooltips to Pajamas](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8370)
* [Popovers > Vue > Migrate popover directive to GitLab UI GlPopover in vue](https://gitlab.com/groups/gitlab-org/-/epics/3949) - 5 issues in total
* [Popovers > Vue > Migrate Bootstrap popover to GitLab UI GlPopover in vue](https://gitlab.com/groups/gitlab-org/-/epics/3948) - 6 issues in total
* [Tooltips > Vue > Migrate vue_shared tooltip to GitLab UI GlTooltip in vue](https://gitlab.com/groups/gitlab-org/-/epics/3951) - 59 issues in total
* [Tooltips > Vue > Migrate Bootstrap tooltip to GitLab UI GlTooltip in vue](https://gitlab.com/groups/gitlab-org/-/epics/3950) - 4 issues in total
##### Goal:
* Each team member should attempt to migrate around 1 Issue
* As a team that means we should strive for migrating around 3 Issues
- [x] Amelia (1 merged)
- [x] Maria (1 merged)
- [ ] Justin (0)
---
### Objective (Great Product): [Improve UX MVCs by providing iteration training to all designers](https://gitlab.com/groups/gitlab-com/-/epics/759)
* **Key Result**: [Effectively apply iterative design principles](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8373)
##### Goal: Completed Training
- [x] Amelia
- [x] Maria
---
### Objective (Great Product): [Scale UX Research to improve velocity and participation](https://gitlab.com/groups/gitlab-com/-/epics/760)
* **Key Result**: [Establish a process to identify actionable insights and track their completion](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/8376)
##### Goal: 80% of new studies in Q3 utilize the ~"Actionable Insight" label (both Problem and Solution Validation)
[Handbook page to explain in more detail](https://about.gitlab.com/handbook/engineering/ux/ux-research-training/research-insights/)
* [ ] Configure
* [x] Monitor: Health
@gitlab-com/gitlab-ux/configure-monitor-ux any thoughts / ideas?Amelia BauerlyMaria VrachniJustin MandellAmelia Bauerlyhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1303Map High Level JTBD2020-11-23T22:13:57ZJacki Bauerjbauer@gitlab.comMap High Level JTBD## What are we doing?
Mapping the high level GitLab jobs based on the [Jobs to Be Done Framework as we use it at GitLab](https://about.gitlab.com/handbook/engineering/ux/jobs-to-be-done/#jtbd-overview).
## Why are we doing this?
There ...## What are we doing?
Mapping the high level GitLab jobs based on the [Jobs to Be Done Framework as we use it at GitLab](https://about.gitlab.com/handbook/engineering/ux/jobs-to-be-done/#jtbd-overview).
## Why are we doing this?
There is value in writing down these jobs:
- writing down the obvious (we have product-market fit so shouldn’t be hard to identify these) will validate that we are all on the same page, and give us a kind of "elevator pitch" for our products.
- this should provide a framework for granularity, which is one of the hardest parts of writing Jobs. Having the high level Jobs written down should provide a sort of "ceiling" and context for the more specific jobs that come just below that level.
- could be a nice quick-start for anyone needing to quickly understand the point of a product area
## Next Steps
- [ ] UX Managers (or folks on their teams) will draft jobs for their stage and group levels. We can use this [Figma file](https://www.figma.com/file/IvUFkUlE38EocHzRG3EpLt/WIP-High-Level-Jobs?node-id=0%3A39) to start with. This shouldn't take a long time, it might actually work best if we go with our gut and then validate with other people to check for agreement.
- [ ] Each manager to review the Jobs with their team and PMs and update accordingly.
- [ ] Polish and publish (probably to handbook, location TBD)
- [ ] Since this is expected to be a learning experience, especially in terms of defining "granularity", publish handbook update in JTBD UX section. Perhaps better defining what we mean by job statement, user story, task, aspirational story, etc.
## Resources
- GitLab Direction page https://about.gitlab.com/direction/
- [Great resource from the Product Marketing team](https://about.gitlab.com/handbook/marketing/product-marketing/usecase-gtm/) - they call them Use Cases but are very similar to JTBD. See the market requirements section under each Tier.
- ...
We can discuss the task overall here, in this issue. We can discuss specifics of the Jobs in the Figma file.Marcel van Remmerdenmvanremmerden@gitlab.comJacki Bauerjbauer@gitlab.comMike LongJustin MandellMarcel van Remmerdenmvanremmerden@gitlab.comhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1275GitLab Design Talks: Iteration2020-11-11T21:45:45ZNick PostGitLab Design Talks: Iteration## Goal
Create a series of recorded discussions looking at GitLab’s [values](https://about.gitlab.com/handbook/values/) & [competencies](https://about.gitlab.com/handbook/competencies) through the lens of design.
This issue focuses on...## Goal
Create a series of recorded discussions looking at GitLab’s [values](https://about.gitlab.com/handbook/values/) & [competencies](https://about.gitlab.com/handbook/competencies) through the lens of design.
This issue focuses on `Iteration` as the MVC.
## Approach
Playlist link: https://www.youtube.com/playlist?list=PL05JrBw4t0KpgzLWbRCXf8o7iap-uoe7o
We will look at iteration from a number of different perspectives in 15-20m conversations:
- [x] @pedroms - *Think big, ship small, move fast* ([video](https://www.youtube.com/watch?v=0lhjzU-QZ2w&feature=youtu.be))
- [x] @aregnery - *A new designer's perspective on iteration at GitLab* ([video](https://www.youtube.com/watch?v=VrXQiik3Q9U))
- [ ] TBC - *The MVC*
- [x] TBC - *A researcher's take on iteration*
- [x] @mjang1 - *A technical writer's take on iteration* ([video](https://youtu.be/lgY3s1CTHms))
- [x] TBC - *A product design manager's take on iteration*
- [ ] TBC - *Managing an ever-changing UX / A user's relationship with iteration*
- [ ] TBC - *Fidelity & iteration*
- [x] @tauriedavis @jareko @jeldergl - *Design systems & iteration*
Any other suggestions?https://gitlab.com/gitlab-org/gitlab-design/-/issues/1270On Boarding stage walkthroughs (UX Perspective)2020-10-20T23:30:04ZJustin MandellOn Boarding stage walkthroughs (UX Perspective)### Problem
As new team members come on board, through new hires or transfers, it's difficult to know where to begin to learn about each stage and what they do.
### Challenge
How might we provide a light-weight, async, way to help get n...### Problem
As new team members come on board, through new hires or transfers, it's difficult to know where to begin to learn about each stage and what they do.
### Challenge
How might we provide a light-weight, async, way to help get new team members up to speed on how each of our stage groups operate and how that fits into the grand scheme of the GitLab product so that they can feel confident in working on our team.
### Solution (?)
Create a series of video walkthroughs that touch on each of our stages' purpose and how they fit within the GitLab app.
### Needs
- [ ] Need to decide on a consistent format/outline so each of our videos has a repeatable format
- [ ] Need to decide how long each video should be
- [ ] How often should the videos be updated
- [ ] Who owns each stages video, who is the DRI
- [ ] What else?
cc @andyvolpe @beckalippert @annabeldunstone @kmann @cam.x @ameliabauerly @nadia_sotnikova @mvrachniJustin MandellJustin Mandell