-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Onboard & Offboard: UX Research #479
Comments
@layneam Assigning to both of us and moving to In Progress. I want to get this finalized and assign to the 2 new UX researchers to test the process. I'll review and add my feedback shortly. |
@jonlam27 @fedelandini Can one of you please update the template with the current details of the UX team meeting?
|
@layneam could you link the document? thanks |
Discussed with Karen the logic behind keeping the on boarding process within the same issue (copying tasks from the overview section and creating as a new comment for each person). I thought it would be cleaner and easier to understand if it was created in the same way as the UX Experience Profile in the CoP. It would also be easier to search for the issue if looking for a particular person and when they were on boarded. UX Experience Profile An issue template would need to be created with all the steps to get on boarded to the project, and each new team member would use the template to create their own issue and work through the steps. To be discussed further at the next PM Meeting. |
@kcoronel I see we also have Airtable and Miro accounts for BallotNav. Do you have any insight into how these have been used by the team? The UX team has mentioned Miro, and I am looking into learning more. @layneam I think it would be helpful to add a sentence or 2 about the applications the team is getting access to. How do you make changes to the section we are to copy/ paste? |
@staceyrebekahscott we used Airtable for the national civic day of hacking and tried to use it for our issue of collecting all the data but it didn't work. It looks like we used miro for a user journey and for the board of advisor persona (Jon is a good person for Miro). You can access both thru the ballotnav gmail account, I wonder if there is another way to have the ui/ux team access, maybe it is our responsibilities as PM's to add their personal emails to the project. |
Offboard: Lihui Zhang
|
@layneam @kcoronel Lihui messaged me on Slack and said she is leaving the team due to starting a new job. I created an Off boarding checklist in the comment above, and I'll check off what I have permission to do. She did not go through a structured on boarding so I think this off board should be simple, but this will be a good chance to test the checklist and make sure we included everything. |
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@staceyrebekahscott Lihui has been removed from everything except slack channels, I don't seem able to do this :( |
@kcoronel Please off board Irina, Gayathri and Federica by creating a comment in this issue for each team member and following the off board template in the overview above. (Add the boxes for Miro to the comment, as it is not part of the template. Once completed, please move issue to Prioritized Backlog. |
I feel that these on boardings should be handled as separate issues, as it would be easier for tracking purposes, but I do not want to overcomplicate the process now for the team members we need to off board immediately. Once in Prioritized Backlog, I'll address all of the off boarding issues as a whole. |
Gayathri should be off boarded from issue #468 |
Also need to offboard Seyoung |
Overview
We need to have a checklist of items to do when a UX researcher onboard and offboards so that the process can be consistent and fast.
Date Updated
Created date: 2022-03-11
Action Items
Resources/Instructions
org template updated 2022-02-23
Changelog
The text was updated successfully, but these errors were encountered: