Skip to content
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

TWE: Review Research Recruitment Process #363

Open
12 tasks
pandanista opened this issue Feb 15, 2023 · 1 comment
Open
12 tasks

TWE: Review Research Recruitment Process #363

pandanista opened this issue Feb 15, 2023 · 1 comment
Labels
complexity: medium feature: research All issues involving research Participant Type: All PBV: research all issues for the research team role: UI/UX research size: 2pt Can be done in 7-12 hours

Comments

@pandanista
Copy link
Member

pandanista commented Feb 15, 2023

Dependency

Overview

We need to review the mentor recruitment messaging in order to define potential items to include in the RP20 recruitment

Gather info (after looking at the epic of all research activities, what is needed for this research plan)

  • Selection criteria (already defined as those that worked with interns on issues)
  • Timeline
  • Identification of recruitment channels
  • setting up interviews with Google appointments
  • roll call
  • Create Research Plans and Goals
  • Recruitment Messaging for each type of channel to include participant info

Action items

  • Identify which (if any) research already performed has involved recruiting participants other than people captive in the program (e.g., interns, mentors and TWE team members were not recruited, they were already part of the program).
  • Conduct searches on wiki pages (See Resources/Instructions) and Google Drive folder (See Resources/Instructions) to see how we conducted recruitment previously
  • Identify what worked and what didn't based on the past responses
  • Identify the best practices for research recruitment in industry, including recruitment timing, cadence, channels, selection criteria, sampling, messaging/scripts, interest forms, etc
  • After gathering all the documents, set up a meeting with UX Lead and Bonnie to get some context and clarification on the previous recruitment
  • Synthesize your findings into a Google Doc named TWE: Report: Research Recruitment Best Practices using the TWE: Report: Generic Template (See link in Resources/Instructions)
  • List out previous recruitment process and outreach scripts in the Resources/Instructions section and the Google Doc you created
  • Include resources for best practices in the Resources/Instructions section and the Google Doc you created
  • Provide recommendations to the UXR Lead on how this information should be streamlined, updated, and presented on the Wiki Research Output Overview page
  • Meet with UXR Lead on your findings and confirm next steps
  • Update relevant WIKI pages (See Resources)
  • Create an issue called TWE: Create Guide for Participant Recruitment Outreach and create a script we can distribute for recruitment

Resources/Instructions

Mentors

@pandanista pandanista changed the title TWE: Review Research Recruitment Outreach TWE: Review Research Recruitment Process and Outreach Feb 16, 2023
@pandanista pandanista changed the title TWE: Review Research Recruitment Process and Outreach TWE: Review Research Recruitment Process Feb 16, 2023
@pandanista pandanista added size: 2pt Can be done in 7-12 hours and removed size: 1pt Can be done in 6 hours labels Feb 16, 2023
@pandanista
Copy link
Member Author

@oij11 This issue will require more time to dig out and collect information. After gathering all the information, please slack me so we could schedule a meeting with Bonnie for more guidance and context before compiling your findings into a document. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium feature: research All issues involving research Participant Type: All PBV: research all issues for the research team role: UI/UX research size: 2pt Can be done in 7-12 hours
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

4 participants