UX Transition for Dan MH to Manage: Foundations

Context

This issue is dedicated to the seamless transition of responsibilities for groupfoundations from to @danmh.

The team member currently assigned to the stage group is responsible for providing the relevant content for the newly assigned DRI. However, it is encouraged to partner closely with Product Management, UX leadership, and stage group counterparts to provide the necessary information for a seamless transition.

Timeline for the transition

Milestone/Date	Description
15.10	Join groupfoundations

👓 Useful information

• Team handbook page
  • Taurie's note: Team members are pulled based on department on the team page. Department was recently removed from designers, so they are not showing up here. I have a todo to work on fixing this.
  • Taurie's note: I've started an MR to help with onboarding in the future which will be added to this team page
• Stage, group, or category handbook pages:
  • Manage stage handbook page
    • Foundations group handbook page
      • Pajamas design system repo
        • Pajamas component lifecycle
• Jobs to be Done (JTBD) handbook page:
  • Design system has not defined JTBD
  • Navigation has defined key themes with the top three being: Minimize feeling overwhelmed, Orient users across the platform, and Pick up where you left off to drive the north star work.
• Stage or Category Vision:
  • Foundations direction
    • Design system direction
    • Navigation and settings direction
    • Documentation direction
• Section UX Strategy:
  • Taurie's note: Foundations lives inside Manage but has always functioned independently. The section strategy is separate from the work being completed in Foundations.
• List the Category or Feature labels associated to this transition:
  • sectiondev devopsmanage groupfoundations
  • pajamasbuild / pajamasdefine / pajamasdesign / pajamasidentify / pajamasintegrate
  • ~"component::*", for example component:avatar or component:form-date-picker
  • Pajamas UI Kit Figma
• Additional resources:
  • Current board
  • Planning issue
  • Retrospective project

👷 Current and upcoming initiatives

Priority	Milestone	Current status	Issue/MR link	Resource
_PRIORITY_	_MILESTONE_	_WORKFLOW LABEL_	Add issue/MR link	Add source

Parked tasks

🗓 Meetings and rituals

• Event name - @mention

☑ Issue tasks

The below tasks should be completed before finalizing the transition and closing this issue.

Click to expand

• Update the title of this issue to: UX Transition for _ STAGE GROUP, GROUP, CATEGORY OR FEATURE_.
• Assign the transition issue to yourself and your Manager.
  • Optionally, add a link to the MR confirming the transition ADD LINK
• Fill out the sections below with the relevant content for the stage, group, or category.
• Inform relevant counterparts, such as Product Managers and Engineering Managers, of the UX transition by pinging them in this issue.
  • Optionally, schedule a sync meeting with the newly assigned DRI, their Manager, and other strategic counterparts. You can also opt for recording a walkthrough video to share with the relevant team.
• Optionally, if a category or feature is being moved, transfer the JTBDs to the relevant team by updating them in the handbook.
• Communicate the change with the stage groups on Slack by sharing a link to this issue.
• *Newly Assigned DRI: When you feel comfortable, unassign the previous DRI and close this issue.