Skip to content

UX Transition for Alex Fracazo to Knowledge

Context

This issue is dedicated to the seamless transition of responsibilities for @afracazo to groupknowledge

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
17.4 Add a description

👓 Useful information

👷 Current and upcoming initiatives

The team has been operating without the designer, and we have multiple projects in-flight that would benefit from the UX oversight.

Engineers did all the UX and design. Ideally, you would connect with the DRIs of these projects and determine what UX support is needed.

Wiki comments

DRI - @himkp from the frontend and @pskorupa on the backend

We have a community contributor working with Himanshu on this project, the main discussion currently happens in those MRs:

We want a UX review on this.

Pages multi-version

DRI - @janis - both frontend and backend

It’s a big project close to Beta release. But there are many small UX inconveniences. So the project would benefit from a comprehensive UX review. You can reach out to Janis for the demo of the whole project, set it up locally, and play around.

Early-stage and future projects

GLQL

DRI - @himkp (it's 100% frontend feature)

Start by watching the Demo Video, and connecting with Himanshu on the future of this project.

One of the concerns here is the language itself. Once we deliver it to users, it can be hard to change.

🗓 Meetings and rituals

  • Optional: Bi-weekly team meeting (DRI: PM, @mmacfarlane), an invitation has been sent. First meeting will be on Thursday 2024-08-22 or you can attend this week on 2024-08-08.
  • Bi-weekly PM/Designer Conversation (DRI: PM, @mmacfarlane), and invitation has been sent. Since we're located on opposite ends of the globe this will late my time early your time. We can always adjust this. It looks like the latest you are on is 5:00am-5:45am in my time. I could do that time but would prefer the alternative, which is 7:00pm-7:45pm my time.

☑ 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.
Edited by Caitlin Steele