UX Transition for the Package Stage
Context
This issue is dedicated to the seamless transition of UX and Design responsibilities for the Package stage from @icamacho to @rayana.
The designer currently assigned to the stage group is responsible for providing the relevant content for the newly assigned designer. However, it is encouraged to partner closely with Product Management, Design leadership, and stage group counterparts to provide the necessary information for a seamless transition.
☑ Tasks
The below tasks should be completed before finalizing the transition and closing this issue.
-
Update the title of the issue to: UX Transition for _ STAGE GROUP, GROUP, OR CATEGORY_
. -
Assign the transition issue to yourself and your Product Design Manager. -
Fill out the sections below with the relevant content for the stage, group, or category. -
Inform relevant Product Managers (PMs) and Engineering Managers (EMs) of the transition -
Communicate the change with the larger team on Slack. -
When the content is ready, assign the new designer to the issue, and @mention
relevant PM, EM, and Product Design Manager. -
Newly Assigned Designer: When you feel comfortable, unassign the previous designer and close this issue.
⌛ History and timeline
Timeline for the transition
Milestone | Description |
---|---|
2021 June 30 | Iain departing from the GitLab team |
👓 Product vision
-
UX Team handbook page: UX Handbook Page
-
Stage, group, or category handbook pages: Package Team Page
-
Stage Direction: Package Direction and Vision
-
Jobs to be Done (JTBD) handbook page: JTBD
-
Section UX Strategy: Package Vision
-
14.1 Planning issue: gitlab#331743 (closed)
-
Additional resources:
- ThinkBIG Reference: ThinkBIG Sync Structures
- Design Files: SSOT Handbook Reference
- User research insights
- Insights from the Retention and Garbage Collection Problem Validation
- Insights from the Package Data Survey
- Insights from the Interviews: Understanding package data user needs
- Insights from Solution Validation of the Container Registry UI
- Insights from Solution Validation of the Dependency Proxy
- Insights from Solution Validation of the Cleanup Policies
- Opportunity Canvas
👷 Current and upcoming initiatives
Package stage
The Package stage recently wrapped up 13.12 with defining the current vision. The next major step for the Package Design was intended to be in-depth discovery research focused on identifying the "next part of the S curve" which underpins part of Package's overall success.
Priority | Due Date | Current status | Issue/MR link | Details |
---|---|---|---|---|
High | 2021-06-30 | workflowready for development | Resolve cleanup alert bug with updated experience | Proposal created in collaboration with engineering |
High | 2021-06-30 | workflowin review | Complete vision prototypes and handbook update | MR to merge Package and Container registry prototypes is ready and in review with @trizzi |
High | 2021-06-30 | workflowin dev | Complete Terraform Registry UI | MR and Reviews successful so far. Final reviews with the configure stage will resolve this issue. |
High | 2021-06-30 | workflowproblem validation | Research package data needs at the Workspace level | Created a discussion guide for @trizzi to review. Research and recruitment request issues will need to be opened by Tim when the research is ready to start. |
Med | 2021-06-30 | workflowdesign | Design alert informing admins of legacy projects Cleanup is now on | Create a notification for admins of legacy projects the cleanup feature is now available for them. |
High | 2021-06-30 | workflowdesign | Create a consistent tag, image, and package delete experience throughout the registries | Audit the current delete file/package/tag/image/repository delete patterns and create a standard interaction pattern |
MR Widgets work
As part of the Q2 OKR, Iain was leading and organizing the effort focused on creating standard patterns for the MR widget and work with individual design teams responsible for a widget to create new designs based on those patterns. End goal and measure of success is each of the widgets have at least 1 workflowready for development issue dedicated to updating the UI.
The current status of the MR Widget is that Foundations and Tech Writing are currently working on creating visual and copy patterns the widgets will need to follow. I am working with team members to be in a place to gather feedback from the broader design team by the end of next week.
Priority | Milestone | Current status | Issue/MR link | Notes |
---|---|---|---|---|
High | 2021-06-04 | workflowdesign | &5710 (closed) | Coordinate with Tim N. to set expectations at the epic level for the team. |
High | 2021-06-04 | workflowdesign | gitlab#331290 (closed) | Confirm audit completion from TW and close. |
High | 2021-06-04 | Done |
gitlab#329907 (closed) | Audit has been completed. |
High | 2021-06-04 | workflowdesign | gitlab#331290 (closed) | Support TW |
High | 2021-06-04 | workflowdesign | gitlab#328245 (closed) | Support and provide feedback to Foundations Designer |
Parked tasks
🗓 Meetings and rituals
-
Package weekly meeting -
Package weekly Quadplanning meeting -
UX/PM Weekly Sync -
UX/FE Weekly Sync -
Monthly 1 on 1 sync with BE(Ruby and Golang) -
Package weekly retro
📞 Slack channels
-
#s_package - Full package team channel -
#s_package_beux - Back End & UX Channel -
#s_package_feux - Front End & UX Channel -
#s_package_standups - Package Standups (bot) -
#s_package_strategy - Package Quadplanning chat -
#ux_ci-cd - CI/CD UX Design team chat -
#mr-widget - MR Widget planning channel.