hackforla / YouthJusticeNav

A project with UCLA law school to help defendants in the Juvenile Justice system in Los Angeles County

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

YJN: Create Research Plan for RP002

ltung05 opened this issue · comments

Dependencies

  • #95
  • A research setup structure (wiki, GitHub labels, Google Drive, etc.) has been created and approved.

Overview

We need to create a Research Plan for Focus Groups so that we can test and see if our collabathon kit and application are ready to be used.

Action Items

  • Update this issue to make sure it's properly categorized and easy to manage
    • Add to the Project Board (helps with Project Management overview)
    • Add a milestone (helps with prioritization)
    • Add label of the correct research plan number associated with this research plan (e.g., Research: RP001) (helps you find related issues in the same workflow)
    • Edit title of issue with the correct research plan number (same as prior)
    • Edit placeholders in Overview of this issue with the relevant information in square brackets. (personalizes the issue to make it easier to read). Any place you see [replace...] replace both the text and the brackets with what it is asking for (including in the front matter above but not where it says name, but not where it says title.
  • Update this issue with the relevant Resources:
    • Go to the Research Output Overview Page (link in Resources) and find the relevant overview type wiki page. Then, change [Wiki [TYPE] Research Overview Page] in the Resources below with the correct wiki page of the research overview by type.
    • Go to the Research Output Overview Page again and find the relevant wiki page for this specific research plan. Then, change the [RP__ Wiki Page] in the Resources below with this RP's specific wiki page.
    • Find and link the folder you are going to put your research plan in (e.g., Research by Type>2. Intern>RP6 - Week out post-event survey)
      • Go to the Google Drive's Research by Type Folder (link in Resources)
      • Go into the relevant Type Folder (e.g., 1. Stakeholder, 2. Collabathon, etc.)
      • once inside, right-click on the relevant destination folder and copy the link. (e.g., RP6 - Week out post-event survey)
      • Add the Google Drive link in the Resources below with the link you just copied and revise the display text to include the Research Plan number (e.g., Google Drive RP__ Folder to Google Drive RP008 Folder)
  • Create the Research Plan Document.
    • Make a new document using the TWE Research Plan template (link in Resources). Follow the instructions in the How To Write a Research Plan guide (link in Resources) and mark your progress in this issue.
    • Move your document from "My Drive" to the shared drive internship folder of this specific RP.
    • Name your document to be called "TWE: RP___ : [TITLE OF RESEARCH] Research Plan".
    • Update the document with the relevant information in accordance with the research roadmap document (found on the Research Overview Page).
    • Update the Table of contents (page 2) when you are finished with the document.
  • Meet and sign-off research plan document with UX Research lead (by adding it to the research team meeting agenda).
  • Update RP Wiki Page with any changes or corrections.
  • Once research lead has signed off, add it to the PM/Research lead agenda
  • sign-off by PM
  • Does this issue have any dependency checkboxes in the action items here?
    • if yes, remove dependencies that are listed below (issues that are waiting on this issue to be completed. Sometimes they have already been made and sometimes they yet to be made).
      • close this issue
    • if no, check to see if the follow-up issues have already been made (see related structure issue). If new issues have not been made, then apply label ready for research lead and define what needs to be done in a comment below
      • close the issue
      • move to Question/Review Column

Resources

@doctorsandy please add your notes :)

@doctorsandy please add your notes :)

Edits that need to be made to RP002, based on our weekly meeting.

  1. KPIs- Need a clearly defined goal. KPI should reflect that we can measure high confidence that everyone is ready for the collabathon. If not, we need to collect data that will help us better prepare applicants for the Collabathon. KPIs should show changes in baseline. GOAL: 8 or above (Likert scale). *Need a way to measure participants' growth in their self-assessment before and after.How prepared did participants feel? Before and after? Can use card-sorts/dot voting.
  2. Research assumptions. The section/language around triggers and traumas should be kept but moved to a new document. This is namely because the ethical obligations around steering participants away from traumatic discussions does not apply to the focus groups. This activity (especially in the first iteration) won't include impacted youth. Thus, re-write the assumptions section for this exact research plan.
  3. Recruitment section. Needs to be re-written since the intake form (RP003) already includes these questions. Redundant in RP002. If we desire a "secondary" or "tertiary sort," needs to be included in RP002
  4. Icebreaker. Separate document with potential low-stakes icebreakers drafted. For a focus group specific icebreaker, include something along the lines of: "Tell us something you wan to know about the justice system."
  5. Semi-structured interviews. This section requires further explanation. Include focused activities, structured so everyone is heard. Affinity mapping (awaiting Code for America video that will be the referential framework), activities using post-its.
  6. Explicit explanation that this focus group will be conducted remotely.

@ExperimentsInHonesty
Bonnie, here's the information and links about the video (RE: Sandy) I was talking about earlier today (2022-01-27)

Reference

From 2022-11-07 Team Meeting

Remind Bonnie to access
- BoP card sort
- Video of the affinity mapping utilization that was presented to (with?) Super by Design

Wiki Search Results

Possible Assets