diff options
Diffstat (limited to '.gitlab/issue_templates/UX Theme.md')
| -rw-r--r-- | .gitlab/issue_templates/UX Theme.md | 114 |
1 files changed, 50 insertions, 64 deletions
diff --git a/.gitlab/issue_templates/UX Theme.md b/.gitlab/issue_templates/UX Theme.md index b015c3d44e6..32e771735b1 100644 --- a/.gitlab/issue_templates/UX Theme.md +++ b/.gitlab/issue_templates/UX Theme.md @@ -1,39 +1,25 @@ -<!-- A majority of the work designers do will be on themes in the (Now) Next 1-3 milestone column of their UX Roadmap. These themes are comprised of high-confidence outcomes and validated needs. The UX theme issue is where collaboration should occur, including plans and discussion on subthemes, research, and design feedback. Related issues for design exploration and solution validation should stem from the theme issue. +<!-- Most of the work designers do will be on themes in the (Now) Next 1-3 milestone column of their UX Roadmap. These themes are comprised of high-confidence outcomes and validated needs. The UX theme issue is where collaboration should occur, including plans and discussion on subthemes, research, and design feedback. Related design exploration and solution validation issues should stem from the theme issue. -One of the advantages of working with UX themes is that it allows us to think and design holistically by designing the theme as a whole as opposed to a single issue at a time trying to piece them together as you go. For more details please refer to this section of the handbook when creating UX Themes: https://about.gitlab.com/handbook/product/ux/product-design/ux-roadmaps/#theme-structure --> +One of the advantages of working with UX themes is that it allows us to think and design holistically by designing the theme as a whole instead of a single issue at a time, trying to piece them together as we go. For more details, please refer to this section of the handbook when creating UX Themes: https://about.gitlab.com/handbook/product/ux/product-design/ux-roadmaps/#ux-theme-structure --> -<!-- Theme Issue Title {UX Theme: <theme statement here>} --> -<!-- Theme Statement: A theme is written as a statement that combines the beneficiary, their need, and the expected outcome when the work is delivered. Well-defined statements are concise without sacrificing the substance of the theme so that anyone can understand it at a glance. (For instance; Reduce the effort for security teams to identify and escalate business-critical risks) - -!!Note: The theme statement is the defacto title that will be used to reference the theme and serve as the theme issue title.!! It should be something that is easily understood, that quickly communicates the intent of the theme allowing team members to easily understand and recognize the expected work that will be done. +<!-- +!!Note: The theme statement is the defacto title that will reference the theme and serve as the theme issue title.!! It should be something that is easily understood that quickly communicates the intent of the theme allowing team members to easily understand and recognize the expected work that will be done. --> ---- -### Problem to solve -<!-- In a brief statement, summerize the problem we are intending to address with this theme. For instance, users are unable to complete [task], or, users struggle with the amount of steps required to complete [task] --> - +### Theme statement +<!-- A theme statement combines the beneficiary, their job, and their expected outcome when the work is delivered and serves as the design goal for the team who owns the theme. Well-defined statements are concise without sacrificing the substance of the theme so that anyone can understand it at a glance. Well-defined statements are concise without sacrificing the substance of the theme so that anyone can understand it at a glance. (For instance, Reduce the effort for security teams when prioritizing business-critical risks in their assets.) --> -### Beneficiary -<!-- Who is the recipient(s) of the value this theme provides; a customer, end-user, or buyer. Who benefits from this theme being executed? This can be a role, a team, or a persona. For instance: "Development teams, [or] Developers, [or], Sasha the Software Engineer". --> +<!-- Also Theme issue tile --> +{`Need/outcome` } + {`Beneficiary`} + {`Job/Small Job`} -- **[Direct beneficiary]** - -#### Need & Primary JTBD -<!-- What is the JTBD and what are the needs related to the beneficiary and theme? -- JTBD: The JTBD statement, for instance, (When I am triaging vulns, I want to address business-critical risks, So I can ensure there is no unattended risk in my orgs assets.) -- Need: Abstracted from the JTBD, for instance, (Identify and escalate business-critical risks detected in my orgs assets.) ---> - -- **JTBD:** -- **Need:** - -#### Expected outcome -<!-- What will the user be able to achieve when this theme is executed? For instance, (Users will be able to effectively triage vulnerabilities at scale across all their orgs assets.) --> +#### Main Job story +<!-- What is the [Main Job story](https://about.gitlab.com/handbook/product/ux/jobs-to-be-done/#how-to-write-a-jtbd) that this theme was derived from? (For instance, When I am on triage rotation, I want to address all the business-critical risks in my assets, So I can minimize the likelihood of my organization being compromised by a security breach.) --> #### Business objective -<!-- What business objective will result from delivering this theme? This answers why we are working on this theme from a business perspective. Examples of objectives are but are not limited to: Sales rate / conversion rate, Success rate / completion rate, Traffic / visitor count, Engagement, or other business-oriented goals. --> +<!-- Objectives (from a business point of view) that will be achieved upon completion. (For instance, Increase engagement by making the experience efficient while reducing the chances of users overlooking high-priority items. --> #### Confidence @@ -42,43 +28,24 @@ One of the advantages of working with UX themes is that it allows us to think an | Confidence | Research | | --- | --- | -| [High/Medium/Low] | [research/insight issue](Link) | - -### User-stories -<!-- Product designers should work with their PMs to gather up all of the relevant user stories. Look for alignment with the JTBD added above. Overall, the solution you and your team come up with should help to support the user stories. --> +| [High/Medium/Low] | [research/insight issue](Link) | -- [user-story here] -- [user-story here] -- [user-story here] -- [etc.] ### Requirements -<!-- Requirements can be taken from existing features or design issues that were used to build this theme. Any related issues should be linked with this issue in the Feature/solution issues section below. They are more granular validated needs, goals, and additional details that the theme encompasses. These are typically reserved for themes in the next (1-3 milestones) column. Requirements should answer “what” the beneficiary of this theme needs from the solution. - -Note: This is not a backlog. If the issue can not be delivered in the theme timeframe then the theme is too big and needs to be broken down into multiple themes. --> - -The beneficieray needs to be able to: -- [need here] -- [need here] -- [need here] -- [etc.] +<!-- Requirements can be taken from existing features or design issues used to build this theme. Any related issues should be linked with this issue in the Feature/solution issues section below. They are more granular validated needs, goals, and additional details that the theme encompasses. These are typically reserved for themes in the next (1-3 milestones) column. Requirements should answer “what” the beneficiary of this theme needs from the solution. -#### Feature/solution issues -<!-- Use this table to track feature issues related to this theme (if applicable). Not all themes require sub-issues as they are typically discovered while working on the theme itself. Think of these issues as if they were the result of breaking down the design into discrete work items. +Note: This is not a backlog. If the issue can not be delivered in the theme timeframe, then the theme is too big and needs to be broken down into multiple themes. --> -Note: if feature issues already exist then you can add them to this table. Keep in mind that these issues will require validation if they are being added to a Theme that's in the Next (1-3 milestones) container and are assumptive. +>⚠️ Related feature and research issues should be linked in the related issues section (Delete this line when this is done) -Refer to https://about.gitlab.com/handbook/product/ux/product-designer/#ux-issue-weights for calculating UX weights. ---> - -| Issue | UX Weight | -| ---------- | --------- | -| [Issue](link) | `0 - 10` | -| [Issue](link) | `0 - 10` | -| [Issue](link) | `0 - 10` | +#### The beneficiary needs to be able to: +- [Small job statement] + - [Micro job statement] + - [Micro job statement] +- [etc.] #### Research -<!-- Use this table to track UX research related to this theme. This may include, problem validation and/or solution validation activities. +<!-- Researchers and Designers; Use this table to track UX research related to this theme. This may include problem validation and solution validation activities. --> | Issue | Research type | Research status | @@ -87,16 +54,35 @@ Refer to https://about.gitlab.com/handbook/product/ux/product-designer/#ux-issue | [Issue]() | <!--Solution validation, Problem validation, etc., --> | <!-- Planned, In Progress, Complete, etc.,--> | #### Ready for design checklist -The items are self-check suggestions; they could be contributed by designers, product managers or researchers -* [ ] The stated `Problem to solve` has high confidence (derived from research or other data-gathering techniques) -* [ ] Relevant issues, research, and other background information are linked to the Related issues section -* [ ] The stated `Beneficiary` has been defined -* [ ] There is high confidence in the stated `Need & Primary JTBD` (derived from research or other data gathering techniques) -* [ ] The `Expected outcome` has been defined +The items are self-check suggestions; they could be contributed by designers, product managers, or researchers +* [ ] The `theme` has high confidence (derived from research or other data-gathering techniques) +* [ ] The `Related issues`, features, research, and other background information are linked to the related issues section * [ ] The `Business objective` has been defined -* [ ] The theme `Confidence` has been defined as High -* [ ] `User-stories` have been defined -* [ ] The `Requirements` have been defined and the scope has been agreed upon -* [ ] This UX Theme contains everyhting necessary to complete a design solution and is ready for design +* [ ] The `Requirements` have been defined, and the scope has been agreed upon +* [ ] This UX Theme contains everything necessary to complete a design solution and is ready for design + +#### [Thematic design workflow checklist](https://about.gitlab.com/handbook/product/ux/product-design/ux-roadmaps/#suggested-workflow) +<!-- please refer to the [suggested workflow](https://about.gitlab.com/handbook/product/ux/product-design/ux-roadmaps/#suggested-workflow) when working on UX themes--> +* [ ] **Theme assessed** Ready for design checklist complete +* [ ] **Ideate and Iterate** + * [ ] User flow diagram generated + * [ ] Low-fidelity wireframes of the entire theme created + * [ ] [Feedback requested](https://about.gitlab.com/handbook/product/ux/product-designer/#design-reviews) and incorporated into flow diagram and wireframes +* [ ] **Validate** + * [ ] [Solution validation](https://about.gitlab.com/handbook/product/ux/ux-research/solution-validation-and-methods/) conducted on Low/mid-fidelity flow +* [ ] **Refine** + * [ ] Resaerch findings incorporated into design + * [ ] All micro-interactions are defined + * [ ] All edge-cases are accounted for and defined + * [ ] All copy has been reviewed by tech writing + * [ ] Accessibnility guidelines have been considered + * [ ] High-fidelity designs posted + * [ ] Feedback requested from counterparts + * [ ] (If necessary) Validate high-fidelity flow in a 2nd round of user testing + * [ ] Refine final design from feedback and user research +* [ ] **Hand-off** + * [ ] Designs broken down based on the their ability to stand alone and that they provide value to the user. + * [ ] MVC plan agreement reached + * [ ] Planning breakdown complete /label ~"UX" ~"UX Theme" |