Commit 0c049602 authored by Christie Lenneville's avatar Christie Lenneville Committed by Brian Rhea
Browse files

Move UX handbook to Product

parent 0feecc95
......@@ -231,12 +231,12 @@ sites/uncategorized/source/company/culture/inclusion/tmrg-gitlab-latinx/ @pmejia
/sites/handbook/source/handbook/engineering/security/security-engineering-and-research/infrastructure-security/ @laurence.bierner @joe-dub
 
^[UX department]
/sites/handbook/source/handbook/engineering/ux/ @clenneville @vkarnes @asmolinski2 @jackib @mvanremmerden @jmandell @tauriedavis @rayana @susantacker @badnewsblair
/sites/handbook/source/handbook/engineering/ux/stage-group-ux-strategy/ci-cd/ @rayana
/sites/handbook/source/handbook/engineering/ux/stage-group-ux-strategy/fulfillment/ @jackib
/sites/handbook/source/handbook/engineering/ux/stage-group-ux-strategy/release/ @rayana @vkarnes
/sites/handbook/source/handbook/engineering/ux/stage-group-ux-strategy/release/release-management/ @rayana @vkarnes
/sites/handbook/source/handbook/engineering/ux/stage-group-ux-strategy/verify/ @rayana @v_mishra @nadia_sotnikova
/sites/handbook/source/handbook/product/ux/ @clenneville @vkarnes @asmolinski2 @jackib @mvanremmerden @jmandell @tauriedavis @rayana @susantacker @badnewsblair
/sites/handbook/source/handbook/product/ux/stage-group-ux-strategy/ci-cd/ @rayana
/sites/handbook/source/handbook/product/ux/stage-group-ux-strategy/fulfillment/ @jackib
/sites/handbook/source/handbook/product/ux/stage-group-ux-strategy/release/ @rayana @vkarnes
/sites/handbook/source/handbook/product/ux/stage-group-ux-strategy/release/release-management/ @rayana @vkarnes
/sites/handbook/source/handbook/product/ux/stage-group-ux-strategy/verify/ @rayana @v_mishra @nadia_sotnikova
 
^[Incubation department]
/sites/handbook/source/handbook/engineering/incubation/ @bmarnane
......@@ -699,7 +699,7 @@ sites/handbook/source/handbook/marketing/corporate-marketing/corporate-communica
/sites/handbook/source/handbook/support/workflows/team/performance_review.html.md @tcooney @lbot @lyle @shaunmccann @vparsons
 
^[Technical Writing]
/sites/handbook/source/handbook/engineering/ux/technical-writing/ @susantacker @dianalogan @kpaizee
/sites/handbook/source/handbook/product/ux/technical-writing/ @susantacker @dianalogan @kpaizee
/sites/handbook/source/handbook/documentation/ @susantacker @dianalogan @kpaizee
/sites/uncategorized/source/job-families/engineering/technical-writer/ @susantacker @dianalogan @kpaizee
/sites/uncategorized/source/job-families/engineering/technical-writing-manager/ @susantacker @dianalogan @kpaizee
......
<!--
 
Before nominating yourself as a trainee, talk with your manager and team about it, as the traineeship is likely to impact your capacity. More information in https://about.gitlab.com/handbook/engineering/ux/pajamas-design-system/design-review/#duration.
Before nominating yourself as a trainee, talk with your manager and team about it, as the traineeship is likely to impact your capacity. More information in https://about.gitlab.com/handbook/product/ux/pajamas-design-system/design-review/#duration.
 
-->
 
## Basic setup
 
1. [ ] Decide which [project and type](https://about.gitlab.com/handbook/engineering/ux/pajamas-design-system/design-review/#maintainer-types)
1. [ ] Decide which [project and type](https://about.gitlab.com/handbook/product/ux/pajamas-design-system/design-review/#maintainer-types)
you would like to become a maintainer of.
1. [ ] Change this issue title to include your name, project, and maintainer type:
`Trainee Design Maintainer ([Project], [Type]): [Your Name]`.
1. [ ] Read the [design review page in the handbook](https://about.gitlab.com/handbook/engineering/ux/pajamas-design-system/design-review).
1. [ ] Understand [how to become a maintainer](https://about.gitlab.com/handbook/engineering/ux/pajamas-design-system/design-review/#maintainer)
and add yourself as a [trainee maintainer](https://about.gitlab.com/handbook/engineering/ux/pajamas-design-system/design-review/#trainee-maintainer)
1. [ ] Read the [design review page in the handbook](https://about.gitlab.com/handbook/product/ux/pajamas-design-system/design-review).
1. [ ] Understand [how to become a maintainer](https://about.gitlab.com/handbook/product/ux/pajamas-design-system/design-review/#maintainer)
and add yourself as a [trainee maintainer](https://about.gitlab.com/handbook/product/ux/pajamas-design-system/design-review/#trainee-maintainer)
in the [team database](https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/doc/team_database.md).
Indicate your selected project and maintainer type:
1. [ ] `design.gitlab.com: trainee_maintainer Figma`
......
......@@ -27,7 +27,7 @@ The following people need to be on the merge request so they stay informed:
### After Approvals and Merge
 
- [ ] Create an issue in the [triage-ops project](https://gitlab.com/gitlab-org/quality/triage-ops/-/issues/new?issuable_template=category-label-change) to update GitLab Bot automation
- [ ] Mention the [product group Technical Writer](https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers) to update the [documentation metadata](https://docs.gitlab.com/ee/development/documentation/#stage-and-group-metadata)
- [ ] Mention the [product group Technical Writer](https://about.gitlab.com/handbook/product/ux/technical-writing/#designated-technical-writers) to update the [documentation metadata](https://docs.gitlab.com/ee/development/documentation/#stage-and-group-metadata)
- [ ] Share MR in #product, #development, and relevant #s_, #g_, and #f_ slack channels
 
<!--
......
......@@ -124,7 +124,7 @@ _Tip:_ Try using the [Review App](https://docs.gitlab.com/ee/ci/review_apps/) in
<details>
<summary>Expand for Details </summary>
 
Once **added as a Reviewer to this merge request**, the [technical writer designated to the corresponding DevOps stage/group](https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments) will perform their review according to the criteria described below.
Once **added as a Reviewer to this merge request**, the [technical writer designated to the corresponding DevOps stage/group](https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments) will perform their review according to the criteria described below.
 
**Please only mark a section as completed once you performed all individual checks!** When your review is complete, please `approve` this MR and remove yourself from Reviewers.
 
......
......@@ -50,7 +50,7 @@ _Handbook references:_
 
- [Blog handbook](https://about.gitlab.com/handbook/marketing/blog/)
- [Release post handbook](https://about.gitlab.com/handbook/marketing/blog/release-posts/)
- [Markdown guide](https://about.gitlab.com/handbook/engineering/technical-writing/markdown-guide/)
- [Markdown guide](https://about.gitlab.com/handbook/markdown-guide/)
 
_People:_
 
......
......@@ -65,7 +65,7 @@
public: 'handbook/engineering/security/performance-indicators/'
 
- source: 'data/performance_indicators/ux_department.yml'
public: 'handbook/engineering/ux/performance-indicators/'
public: 'handbook/product/ux/performance-indicators/'
 
- source: /(sites\/.+\/)?source\/includes\/_performance_indicators.html.erb/
public: 'handbook/engineering/performance-indicators/'
......
......@@ -59,7 +59,7 @@
embed: v2
- name: UX Debt
base_path: "/handbook/engineering/development/performance-indicators/"
definition: See <a href="https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt"> UX Debt</a> for the definition. We include this as part of the development PIs since we need to help to positively affect change of this metric.
definition: See <a href="https://about.gitlab.com/handbook/product/ux/performance-indicators/#ux-debt"> UX Debt</a> for the definition. We include this as part of the development PIs since we need to help to positively affect change of this metric.
target: Below 50 open "ux debt" issues
org: Development Department
is_key: false
......@@ -68,7 +68,7 @@
reasons:
- Currently following UX guidance for health where we are above target.
urls:
- "/handbook/engineering/ux/performance-indicators/#ux-debt"
- "/handbook/product/ux/performance-indicators/#ux-debt"
sisense_data:
chart: 6599301
dashboard: 462325
......
......@@ -2,7 +2,7 @@
base_path: "/handbook/engineering/incubation/performance-indicators/"
parent: "/handbook/engineering/performance-indicators/#seg-category-maturity"
definition: Incubation Engineering Single-Engineer Groups aim to reach a <a href="https://about.gitlab.com/direction/maturity/">Viable level of maturity</a> for each of our areas of focus. We aim to accomplish this within 12 months of inception. This metric focuses on our ability to ship a product, not on the success or failure of usage, market share, or revenue based metrics.
target: <a href="https://about.gitlab.com/handbook/engineering/ux/category-maturity-scorecards/">Category Maturity Scorecard</a> of 3.14
target: <a href="https://about.gitlab.com/handbook/product/ux/category-maturity-scorecards/">Category Maturity Scorecard</a> of 3.14
org: Incubation Engineering Department
is_key: true
health:
......
- name: Total open SUS-impacting issues by severity
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: The purpose of this chart is to show the total volume of existing issues that impact our SUS score. The labels we're tracking against include "Usability benchmark," "Low SUS Score," "UX scorecard-rec," "cm-scorecard-rec," "UX debt," "UI polish," "accessibility," "VP-UX Dogfooding," "learnability," "UI text," "bug::ux," "maintenance::usability," and "pajamas::integrate".
target: TBD
sisense_data:
......@@ -14,7 +14,7 @@
- We have not yet determined a target.
dri: <a href="https://gitlab.com/clenneville">Christie Lenneville</a>
- name: Technical Writer MR Rate
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: This PI tracks the number of MRs merged every month using the Technical Writing label across all GitLab projects where the team works.
target: 55 MRs per technical writer per month
org: UX Department
......@@ -29,7 +29,7 @@
dashboard: 462325
embed: v2
- name: Average research projects per Product Designer
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: Our goal is to use customer research to validate problems and solutions to ensure we
are building the right things in the right way. We use many research methods,
including interviews, surveys, usability studies, findability/navigation studies,
......@@ -48,8 +48,8 @@
- Below target for most of FY22.
dri: <a href="https://gitlab.com/asmolinski2">Adam Smolinski</a>
- name: Product Design MR review volume
base_path: "/handbook/engineering/ux/performance-indicators/"
definition: Our goal is to provide UX reviews for Merge Requests (MRs) that include user-facing changes, including those impacting screen readers, to help improve the quality of our product and reduce the amount of UX debt. Product Designers follow our <a href="/handbook/engineering/ux/product-designer/mr-reviews/">MR Review guidelines</a> to conduct these reviews.
base_path: "/handbook/product/ux/performance-indicators/"
definition: Our goal is to provide UX reviews for Merge Requests (MRs) that include user-facing changes, including those impacting screen readers, to help improve the quality of our product and reduce the amount of UX debt. Product Designers follow our <a href="/handbook/product/ux/product-designer/mr-reviews/">MR Review guidelines</a> to conduct these reviews.
target: At or greater than 200 MR Reviews per month
sisense_data:
chart: 12013056
......@@ -97,14 +97,14 @@
# - name: Department
# value: UX
- name: System Usability Scale (SUS) score
base_path: "/handbook/engineering/ux/performance-indicators/"
definition: The <a href="/handbook/engineering/ux/performance-indicators/system-usability-scale/">System Usability Scale (SUS)</a> is an industry-standard survey that
base_path: "/handbook/product/ux/performance-indicators/"
definition: The <a href="/handbook/product/ux/performance-indicators/system-usability-scale/">System Usability Scale (SUS)</a> is an industry-standard survey that
measures overall system usability based on 10 questions. Moving a SUS score upward
even a couple of points on a large system is a significant change. The goal of
this KPI is to understand how usability of the GitLab product rates against industry
standards and then track trends over time. Even though UX will be responsible
for this metric, they will need other departments such as PM and Development to
positively affect change. See <a href="/handbook/engineering/ux/performance-indicators/system-usability-scale/index.html#interpreting-sus-scores">our grading scale</a> for details on interpreting scores. To view a detailed breakdown by individual questions from SaaS users, go to the <a href="https://app.periscopedata.com/app/gitlab/816864/SaaS-SUS-Survey-Scores">SaaS dashboard</a>. SaaS SUS data is collected quarterly and Self-Managed data every other quarter. Because of this bi-quarterly collection and gaps in previous collections, Self-Managed data will appear as unlinked points in the Sisense chart below.
positively affect change. See <a href="/handbook/product/ux/performance-indicators/system-usability-scale/index.html#interpreting-sus-scores">our grading scale</a> for details on interpreting scores. To view a detailed breakdown by individual questions from SaaS users, go to the <a href="https://app.periscopedata.com/app/gitlab/816864/SaaS-SUS-Survey-Scores">SaaS dashboard</a>. SaaS SUS data is collected quarterly and Self-Managed data every other quarter. Because of this bi-quarterly collection and gaps in previous collections, Self-Managed data will appear as unlinked points in the Sisense chart below.
 
target: 77 (out of 100)
sisense_data:
......@@ -124,7 +124,7 @@
- FY23-Q1 included 331 Pajamas migrations and burn down of <a href="https://gitlab.com/gitlab-org/gitlab-design/-/issues/1854">9 S1 SUS-Impacting issues</a>.
dri: <a href="https://gitlab.com/clenneville">Christie Lenneville</a>
- name: SUS-impacting issues opened/closed each month
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: With SUS as a KPI, it's important to ensure that we are opening and closing SUS-impacting issues at an appropriate velocity. UX is responsible for ensuring that issues are opened when appropriate and advocating for their prioritization, while Product Management is the ultimate DRI for prioritization. The labels we're tracking against include "Usability benchmark," "Low SUS Score," "UX scorecard-rec," "cm-scorecard-rec," "UX debt," "UI polish," "accessibility," "VP-UX Dogfooding," "learnability," "UI text," "bug::ux," "maintenance::usability," and "pajamas::integrate".
target: TBD
sisense_data:
......@@ -139,7 +139,7 @@
- We have not yet determined a target.
dri: <a href="https://gitlab.com/clenneville">Christie Lenneville</a>
- name: Pajamas component migrations
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: Integrating Pajamas components into GitLab contributes to a cohesive and
consistent user experience, visually and functionally. This allows users to seemlessly
transition throughout different stages of the DevOps lifecycle. <a href="https://gitlab.com/groups/gitlab-org/-/epics/3107">38 foundational components</a>
......@@ -162,8 +162,8 @@
dashboard: 907214
embed: v2
- name: Usability benchmarking overall score by stage
base_path: "/handbook/engineering/ux/performance-indicators/"
definition: This PI tracks the overall stage score for <a href="https://about.gitlab.com/handbook/engineering/ux/ux-research-training/usability-benchmarking/">usability benchmarking</a> studies performed across stage groups as they change over time. The tasks and workflows that comprise each benchmarking study are derived from JTBD for one or more target personas typical for the stage running the study. The overall score for each study takes into account the performance of each task that was tested, through metrics like completion rate, severity, and customer effort score (CES). The scale is 0-100, where 90-100 is ‘Great’, 80-89 is ‘Good’, 70-79 is ‘Fair’, 69 and below is ‘Poor’.
base_path: "/handbook/product/ux/performance-indicators/"
definition: This PI tracks the overall stage score for <a href="https://about.gitlab.com/handbook/product/ux/ux-research-training/usability-benchmarking/">usability benchmarking</a> studies performed across stage groups as they change over time. The tasks and workflows that comprise each benchmarking study are derived from JTBD for one or more target personas typical for the stage running the study. The overall score for each study takes into account the performance of each task that was tested, through metrics like completion rate, severity, and customer effort score (CES). The scale is 0-100, where 90-100 is ‘Great’, 80-89 is ‘Good’, 70-79 is ‘Fair’, 69 and below is ‘Poor’.
target: 5% increase in overall score from previous benchmarking, maintaining an overall score above 79/100.
org: UX Department
is_key: false
......@@ -179,7 +179,7 @@
dashboard: 1012643
embed: v2
- name: UX Average Location Factor
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
parent: "/handbook/engineering/performance-indicators/#engineering-average-location-factor"
definition: We remain efficient financially if we are hiring globally, working asynchronously,
and hiring great people in low-cost regions where we pay market rates. We track
......@@ -198,7 +198,7 @@
dashboard: 462325
embed: v2
- name: UX Budget Plan vs Actuals
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
parent: "/handbook/engineering/performance-indicators/#engineering-non-headcount-budget-vs-plan"
definition: We need to spend our investors' money wisely. We also need to run a
responsible business to be successful.
......@@ -213,7 +213,7 @@
urls:
- https://app.periscopedata.com/app/gitlab/632490/UX-Non-Headcount-BvAs
- name: UX Handbook MR Rate
base_path: "/handbook/engineering/ux/performance-indicators/index.html#ux-handbook-update-frequency"
base_path: "/handbook/product/ux/performance-indicators/index.html#ux-handbook-update-frequency"
parent: "/handbook/engineering/performance-indicators/#engineering-handbook-update-frequency"
definition: The handbook is essential to working remote successfully, to keeping
up our transparency, and to recruiting successfully. Our processes are constantly
......@@ -234,7 +234,7 @@
shared_dashboard: a3a7d250-712d-4982-8d02-f13f7bcbbf71
embed: v2
- name: UX Department MR Rate
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
parent: "/handbook/engineering/performance-indicators/#engineering-mr-rate"
definition: UX Department MR Rate is a performance indicator showing how many changes the UX team implements
directly in the GitLab product. We currently count all members of the UX Department
......@@ -259,7 +259,7 @@
shared_dashboard: 98e50197-4564-47f1-8a70-aa156c1c52e3
embed: v2
- name: UX Department New Hire Average Location Factor
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
parent: "/handbook/engineering/performance-indicators/#engineering-division-new-hire-average-location-factor"
definition: We remain efficient financially if we are hiring globally, working asynchronously,
and hiring great people in low-cost regions where we pay market rates. We track
......@@ -299,7 +299,7 @@
- name: Breakout_Division_Department
value: Engineering - UX
- name: Actionable insights
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: Actionable insights originate from user research. They always have the 'Actionable Insight' label applied to the resulting issue and a clear follow up that needs to take place as a result of the research observation or data. An actionable insight both defines the insight and clearly calls out the next step as a recommendation. The goal of this KPI is to ensure we're documenting research insights that are actionable and tracking their closure rate.
target: TBD
sisense_data:
......@@ -314,7 +314,7 @@
- Q3 FY21 was spent establishing a baseline. Now that there's ample data available, we'll take two steps. Step 1 - investigate the oldest open actionable insights to understand why they have not been closed. Step 2 - track the average time for actionable insights to be closed.
dri: <a href="https://gitlab.com/asmolinski2">Adam Smolinski</a>
- name: UX Debt
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: <a href="https://about.gitlab.com/handbook/engineering/workflow/#ux-debt">UX Debt</a> means that for a given issue, we failed to meet defined standards
for our Design system or for usability and feature viability standards as defined
in agreed-upon design assets. When we fail to ship something according to defined
......@@ -340,7 +340,7 @@
adjustments as we see the results.
dri: <a href="https://gitlab.com/vkarnes">Valerie Karnes</a>
- name: Open UX Debt Age
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: Age of outstanding <a href="https://about.gitlab.com/handbook/engineering/workflow/#ux-debt">UX Debt</a> issues. UX Debt means that for a given issue, we failed to meet defined standards. Age represented via median of days opened.
sisense_data:
chart: 11954760
......@@ -357,7 +357,7 @@
dri: <a href="https://gitlab.com/vkarnes">Valerie Karnes</a>
 
- name: Technical Writing collaboration on UI text
base_path: "/handbook/engineering/ux/performance-indicators/"
base_path: "/handbook/product/ux/performance-indicators/"
definition: Historically, Technical Writers were not consistently included in the creation of UI text. Since UI text is critical to product usability, Technical Writing involvement can help improve the quality of our UI.
This chart includes issues and MRs with the Technical Writing and UI text labels, because Technical Writing contributions happen in both places.
target: TBD
......@@ -373,8 +373,8 @@
dashboard: 462325
embed: v2
- name: Product Designer Gearing Ratio
base_path: "/handbook/engineering/ux/performance-indicators/"
definition: Number of Product designers against the targeted <a href="https://about.gitlab.com/handbook/engineering/ux/how-we-work/#headcount-planning">gearing ratio</a>
base_path: "/handbook/product/ux/performance-indicators/"
definition: Number of Product designers against the targeted <a href="https://about.gitlab.com/handbook/product/ux/how-we-work/#headcount-planning">gearing ratio</a>
target: At 52 product designers
org: UX Department
is_key: false
......@@ -387,8 +387,8 @@
dashboard: 740180
embed: v2
- name: Technical Writer Gearing Ratio
base_path: "/handbook/engineering/ux/performance-indicators/"
definition: Number of Technical Writers against the targeted <a href="https://about.gitlab.com/handbook/engineering/ux/how-we-work/#headcount-planning">gearing ratio</a>
base_path: "/handbook/product/ux/performance-indicators/"
definition: Number of Technical Writers against the targeted <a href="https://about.gitlab.com/handbook/product/ux/how-we-work/#headcount-planning">gearing ratio</a>
target: At 17 technical writers
org: UX Department
is_key: false
......@@ -402,8 +402,8 @@
dashboard: 740180
embed: v2
- name: UX Researcher Gearing Ratio
base_path: "/handbook/engineering/ux/performance-indicators/"
definition: Number of researchers against the targeted <a href="https://about.gitlab.com/handbook/engineering/ux/how-we-work/#headcount-planning">gearing ratio</a>
base_path: "/handbook/product/ux/performance-indicators/"
definition: Number of researchers against the targeted <a href="https://about.gitlab.com/handbook/product/ux/how-we-work/#headcount-planning">gearing ratio</a>
target: At 10 researchers
org: UX Department
is_key: false
......
......@@ -970,17 +970,28 @@
- /job-families/product/technical-writer
target: /job-families/engineering/technical-writer/
comp_op: '='
- sources:
- /handbook/engineering/ux
- /handbook/engineering/ux/
target: /handbook/product/ux/
comp_op: '='
- sources:
- /handbook/engineering/ux/ux-researcher
- /handbook/engineering/ux/ux-researcher/
- /handbook/engineering/ux/uxresearcher-onboarding
- /handbook/engineering/ux/uxresearcher-onboarding/
target: /handbook/engineering/ux/ux-research/
- /handbook/product/ux/ux-researcher
- /handbook/product/ux/ux-researcher/
- /handbook/product/ux/uxresearcher-onboarding
- /handbook/product/ux/uxresearcher-onboarding/
target: /handbook/product/ux/ux-research/
comp_op: '='
- sources:
- /handbook/engineering/ux/ux-researcher-training
- /handbook/engineering/ux/ux-researcher-training/
target: /engineering/ux/ux-research-training/
- /handbook/product/ux/ux-researcher-training
- /handbook/product/ux/ux-researcher-training/
target: /product/ux/ux-research-training/
comp_op: '='
- sources:
- /job-families/legal
......@@ -2362,7 +2373,7 @@
- sources:
- /handbook/engineering/technical-writing/
- /handbook/product/technical-writing/
target: /handbook/engineering/ux/technical-writing/
target: /handbook/product/ux/technical-writing/
comp_op: '~'
- sources:
- /handbook/sales/POC
......@@ -2468,8 +2479,8 @@
target: /handbook/marketing/revenue-marketing/account-based-marketing/
comp_op: '='
- sources:
- /handbook/engineering/ux/technical-writing/markdown-guide/
- /handbook/engineering/ux/technical-writing/markdown-guide
- /handbook/product/ux/technical-writing/markdown-guide/
- /handbook/product/ux/technical-writing/markdown-guide
target: /handbook/markdown-guide/
comp_op: '='
- sources: /handbook/engineering/security/third-party-vendor-security-review.html
......@@ -3186,10 +3197,10 @@
target: /handbook/engineering/metrics/sec/govern/compliance
comp_op: '='
- sources:
- /handbook/engineering/ux/stage-group-ux-strategy/protect
- /handbook/engineering/ux/stage-group-ux-strategy/protect/
- /handbook/engineering/ux/stage-group-ux-strategy/protect/index.html
target: /handbook/engineering/ux/stage-group-ux-strategy/govern/
- /handbook/product/ux/stage-group-ux-strategy/protect
- /handbook/product/ux/stage-group-ux-strategy/protect/
- /handbook/product/ux/stage-group-ux-strategy/protect/index.html
target: /handbook/product/ux/stage-group-ux-strategy/govern/
comp_op: '='
- sources:
- /handbook/product/secure-and-protect-intern-program
......@@ -3235,10 +3246,10 @@
target: /handbook/product/sec-section-performance-indicators
comp_op: '='
- sources:
- /handbook/engineering/ux/stage-group-ux-strategy/secure-and-protect
- /handbook/engineering/ux/stage-group-ux-strategy/secure-and-protect/
- /handbook/engineering/ux/stage-group-ux-strategy/secure-and-protect/index.html
target: /handbook/engineering/ux/stage-group-ux-strategy/sec
- /handbook/product/ux/stage-group-ux-strategy/secure-and-protect
- /handbook/product/ux/stage-group-ux-strategy/secure-and-protect/
- /handbook/product/ux/stage-group-ux-strategy/secure-and-protect/index.html
target: /handbook/product/ux/stage-group-ux-strategy/sec
comp_op: '='
- sources:
- /gdpr
......@@ -3879,9 +3890,9 @@
target: /handbook/engineering/development/ops/verify/pipeline-execution/
comp_op: '='
- sources:
- /handbook/engineering/ux/stage-group-ux-strategy/ci-cd/continuous-integration/
- /handbook/engineering/ux/stage-group-ux-strategy/ci-cd/continuous-integration/index.html
target: /handbook/engineering/ux/stage-group-ux-strategy/ci-cd/pipeline-execution/
- /handbook/product/ux/stage-group-ux-strategy/ci-cd/continuous-integration/
- /handbook/product/ux/stage-group-ux-strategy/ci-cd/continuous-integration/index.html
target: /handbook/product/ux/stage-group-ux-strategy/ci-cd/pipeline-execution/
comp_op: '='
- sources:
- /handbook/sales/sales-term-glossary/acv-in-practice
......@@ -3889,8 +3900,8 @@
target: /handbook/sales/sales-term-glossary/arr-in-practice/
comp_op: '='
- sources:
- /handbook/engineering/ux/stage-group-ux-strategy/growth
- /handbook/engineering/ux/stage-group-ux-strategy/growth/
- /handbook/product/ux/stage-group-ux-strategy/growth
- /handbook/product/ux/stage-group-ux-strategy/growth/
target: /handbook/product/growth/
comp_op: '='
- sources:
......@@ -4273,7 +4284,7 @@
target: https://internal-handbook.gitlab.io/handbook/product/investment/
comp_op: '='
- sources:
- /handbook/engineering/ux/technical-writing/workflow/release.html
- /handbook/product/ux/technical-writing/workflow/release.html
target: https://gitlab.com/gitlab-org/gitlab-docs/-/blob/main/doc/releases.md
comp_op: '='
- sources:
......@@ -4317,9 +4328,9 @@
target: /handbook/engineering/security/security-engineering-and-research/infrastructure-security/
comp_op: '='
- sources:
- /handbook/engineering/ux/ux-research-training/strategic-research-at-gitlab/cross-stage-research-program.html
- /handbook/engineering/ux/ux-research-training/strategic-research-at-gitlab/devops-platform-research-program.html
target: /handbook/engineering/ux/ux-research-training/strategic-research-at-gitlab/gitlab-adoption-research-program.html
- /handbook/product/ux/ux-research-training/strategic-research-at-gitlab/cross-stage-research-program.html
- /handbook/product/ux/ux-research-training/strategic-research-at-gitlab/devops-platform-research-program.html
target: /handbook/product/ux/ux-research-training/strategic-research-at-gitlab/gitlab-adoption-research-program.html
comp_op: '='
- sources:
- /handbook/hiring/resource-guide
......
---
about: "Our [UX Showcase](/handbook/engineering/ux/ux-department-workflow/ux-showcase/) is a fortnightly presentation of notable User Experience projects, where Product Designers from every stage group take turns sharing their accomplishments to collect feedback."
about: "Our [UX Showcase](/handbook/product/ux/ux-department-workflow/ux-showcase/) is a fortnightly presentation of notable User Experience projects, where Product Designers from every stage group take turns sharing their accomplishments to collect feedback."
......@@ -61,4 +61,4 @@ before publishing, see [**Local development**](development.md) for
instructions.
 
[Blog Handbook]: https://about.gitlab.com/handbook/marketing/blog/
[mkd-guide]: https://about.gitlab.com/handbook/engineering/ux/technical-writing/markdown-guide/
[mkd-guide]: https://about.gitlab.com/handbook/product/ux/technical-writing/markdown-guide/
......@@ -118,4 +118,4 @@ follow the steps below:
[press releases]: https://about.gitlab.com/press/releases/
[press category]: https://about.gitlab.com/blog/categories/press
[blog archives]: https://about.gitlab.com/blog/archives.html
[md]: https://about.gitlab.com/handbook/engineering/ux/technical-writing/markdown-guide
[md]: https://about.gitlab.com/handbook/product/ux/technical-writing/markdown-guide
......@@ -4,7 +4,7 @@ module UxHelpers
def ux_grade(grade)
link_to(
image_tag("/images/grade/grade_#{grade}.svg", alt: "Badge level #{grade}"),
"/handbook/engineering/ux/ux-scorecards/index.html#grading-rubric"
"/handbook/product/ux/ux-scorecards/index.html#grading-rubric"
)
end
end
......@@ -685,7 +685,7 @@ The Qualtrics mailing list data pump process, also known in code as `Qualtrics S
 
During the process, the Google Sheet is updated to reflect the process' status. The first column's name is set to `processing` when the process begins, and then is set to `processed` when the mailing list and contacts have been uploaded to Qualtrics. Changing the column name informs the requester of the process' status, assists in debugging, and ensures that a mailing list is only created once for each spreadsheet.
 
The end user experience is described on the [UX Qualtrics page](/handbook/engineering/ux/qualtrics/#distributing-your-survey-to-gitlabcom-users).
The end user experience is described on the [UX Qualtrics page](/handbook/product/ux/qualtrics/#distributing-your-survey-to-gitlabcom-users).
 
##### Debugging to Qualitrics PRocesses
 
......
......@@ -60,7 +60,7 @@ The specific agenda for each offsite depends on active projects. Typical items i
1. Relevant People projects around performance, engagement, and retention
1. [Big rocks](https://www.franklincovey.com/the-5-choices/choice-3/) (large initiatives) presentation and discussion
1. Direction updates (**annual in Q4**)
1. [UX](/handbook/engineering/ux/#actionable-steps) and [Support](/handbook/support/#fy23-direction) have been using epics to track their direction progress throughout the year. This is recommended but not required.
1. [UX](/handbook/product/ux/#actionable-steps) and [Support](/handbook/support/#fy23-direction) have been using epics to track their direction progress throughout the year. This is recommended but not required.
1. OKR planning for the next quarter
1. Department-to-department feedback (always last)
 
......
......@@ -98,7 +98,7 @@ work proceeds. As the feature flag rollout proceeds, the [documentation should b
 
This avoids the rush to provide documentation that often accompanies the release cutoff.
 
[new or changed functionality]: https://about.gitlab.com/handbook/engineering/ux/technical-writing/workflow/#for-a-product-change
[new or changed functionality]: https://about.gitlab.com/handbook/product/ux/technical-writing/workflow/#for-a-product-change
[definition of done]: https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#definition-of-done
[feature flag template]: https://docs.gitlab.com/ee/development/documentation/feature_flags.html#features-disabled-by-default
[documentation should be updated]: https://docs.gitlab.com/ee/development/documentation/feature_flags.html#features-that-became-enabled-by-default
......
......@@ -175,7 +175,7 @@ work proceeds. As the feature flag rollout proceeds, the [documentation should b
 
This avoids the rush to provide documentation that often accompanies the release cutoff.
 
[new or changed functionality]: https://about.gitlab.com/handbook/engineering/ux/technical-writing/workflow/#for-a-product-change
[new or changed functionality]: https://about.gitlab.com/handbook/product/ux/technical-writing/workflow/#for-a-product-change
[definition of done]: https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#definition-of-done
[feature flag template]: https://docs.gitlab.com/ee/development/documentation/feature_flags.html#features-disabled-by-default
[documentation should be updated]: https://docs.gitlab.com/ee/development/documentation/feature_flags.html#features-that-became-enabled-by-default
......
......@@ -320,12 +320,12 @@ We follow the Quad Planning process defined [here](https://about.gitlab.com/hand
 
### User Experience
 
We strive to provide excellent usability in all of our workflows, creating a balance between user and business needs. Product Designers work closely with Product Managers and Engineers. Visit the [Fulfillment User Experience](/handbook/engineering/ux/stage-group-ux-strategy/fulfillment/) page for details.
We strive to provide excellent usability in all of our workflows, creating a balance between user and business needs. Product Designers work closely with Product Managers and Engineers. Visit the [Fulfillment User Experience](/handbook/product/ux/stage-group-ux-strategy/fulfillment/) page for details.
 
In summary,
- We follow the [Product Designer Workflows](/handbook/engineering/ux/product-designer/).
- We follow the [Product Designer Workflows](/handbook/product/ux/product-designer/).
- We track user research efforts using `UX Problem Validation` and `UX Solution Validation` labels.
- We weight issues using the [UX issue weighting process](/handbook/engineering/ux/product-designer/#ux-issue-weights).
- We weight issues using the [UX issue weighting process](/handbook/product/ux/product-designer/#ux-issue-weights).
- We create separate [UX] and [Engineering] issues to aid in tracking issue weights.
- [UX] issues are the SSOT for designs and should reflect the latest design decisions. Related implementation issues should link to the [UX] issue for the design details to maintain the SSOT.
- Fulfillment Product Designers participate in GitLab's reviewer roulette, but at this time only Fulfillment Product Designers should review CustomersDot MRs and GitLab MRs that require connection to CustomersDot (e.g., the GitLab.com purchase flow).
......@@ -344,7 +344,7 @@ In addition to the approval rules, MRs may require additional reviews as suggest
2. Security-related issues (such as changes to authentication) require a [Security review](https://about.gitlab.com/handbook/engineering/security/security-engineering-and-research/application-security/appsec-reviews.html#adding-features-to-the-queue)
3. Changes to the SFDC APIs require review by the [Sales team](https://about.gitlab.com/handbook/sales/field-operations/sales-systems/)
4. Changes to the Zuora APIs require review by the [EntApps team](https://about.gitlab.com/handbook/business-technology/enterprise-applications/)
5. Changes to the user experience require a [UX Review(/handbook/engineering/ux/product-designer/mr-reviews/)].
5. Changes to the user experience require a [UX Review(/handbook/product/ux/product-designer/mr-reviews/)].
 
### Weekly async issue updates
 
......
......@@ -49,7 +49,7 @@ As part of FY23, we want to see our team grow and continue to improve our effici
 
### SUS improvements
 
User experience is a continued focus area for FY23 working on the accomplishments of FY22. We support this effort both in the product development as well as in our architecture. This includes continued conversion of [Pajamas components](https://about.gitlab.com/handbook/engineering/ux/pajamas-design-system/) in order to continue to improve performance experienced by users. We have moved to a cadence of completing X issues per quarter. Q1 our goal is 300 and this will continue throughout the year. In parallel we will work on a SUS issues burndown. We are starting with the goal of resolving all S1s in Q1. We will continue this work into subesequent quarters on reduction in all severities.
User experience is a continued focus area for FY23 working on the accomplishments of FY22. We support this effort both in the product development as well as in our architecture. This includes continued conversion of [Pajamas components](https://about.gitlab.com/handbook/product/ux/pajamas-design-system/) in order to continue to improve performance experienced by users. We have moved to a cadence of completing X issues per quarter. Q1 our goal is 300 and this will continue throughout the year. In parallel we will work on a SUS issues burndown. We are starting with the goal of resolving all S1s in Q1. We will continue this work into subesequent quarters on reduction in all severities.
 
### Top Cross-functional initiatives
 
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment