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: Research: RP017: Data: Analyze #493

Open
40 of 64 tasks
Tracked by #475
pandanista opened this issue Oct 25, 2023 · 24 comments
Open
40 of 64 tasks
Tracked by #475

TWE: Research: RP017: Data: Analyze #493

pandanista opened this issue Oct 25, 2023 · 24 comments

Comments

@pandanista
Copy link
Member

pandanista commented Oct 25, 2023

Dependencies

Overview

We need to analyze the data collected for RP017 to generate research findings, synthesize insights, and provide product recommendations.

Action Items

Customize Resource Links

  • Customize Resource for Wiki Page Link

    • Go to the wiki page: Research Output Overview (Resources # 1.01)
    • Choose the link in the Research by Plan Number section
    • Locate relevant wiki page for RP017
    • Copy the link for the wiki page
    • In Resources # 2.01, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked Screenshot 2023-02-21 at 6 47 15 PM
  • Customize Resource for this Research Plan's Google Drive Folder

    • Open the Google Drive's Research by Type Folder (Resources # 1.02)
    • Choose the Intern folder
    • Choose the RP017 folder
    • Copy the link of the RP017 folder
      1. Choose the three vertical dots on the right side of the RP017 folder Screenshot 2023-10-10 at 5 58 13 PM
      2. Choose "Share"
      3. Choose "Get link"
      4. Choose "Copy Link" and "Done"
    • In Resources # 2.02, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked
    • Open the RP017 folder in Google Drive (Resources # 2.02)
    • Locate the research plan in RP017 folder
      • Choose RP017's research plan in Google Doc
      • Copy the link of the RP017 research plan
        1. Choose the three vertical dots on the right side of the RP017 research plan Screenshot 2023-10-10 at 5 58 13 PM
        2. Choose "Share"
        3. Choose "Copy Link"
        4. The "Link copied" notification pops up
    • In Resources # 2.03, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked
    • Locate the RP017's de-identified transcript(s) in RP017 folder (Resources # 2.02)
      • Choose RP017's de-identified transcript(s)
      • Copy the link of the RP017 de-identified transcript(s)
        1. Choose the three vertical dots on the right side of the RP017 de-identified transcript(s) Screenshot 2023-10-10 at 5 58 13 PM
        2. Choose "Share"
        3. Choose "Copy Link"
        4. The "Link copied" notification pops up
    • In Resources # 2.04, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked

Review and examine the case

  • Read through research plan and de-identified transcript(s) to get familiar with study (Resources 2.03 and 2.04)
  • Review the list of resources for case study to get familiar with the case study techniques (Resources 1.03 - 1.10)
  • Consider the following factors when reviewing and examining the case:
    • Identify relevant facts and key problems
    • Consider why they exist and how they impact the organization or product
    • Review outside research/resources to uncover possible solutions/changes
    • Consider supporting evidence, pros/cons to solutions/changes
    • Are possible solutions/changes realistic?

Draft case study report

  • Create a case study report using the template with HfLA branding (Resources # 1.11)
    • Choose Use Template
    • Update the title of the case study
      • Copy the following texts
      TWE: IS22: RP017: Intern Activity Dashboard Case Study Report
      
      • Paste the texts you copied into the title page to replace the default title Screenshot 2024-05-28 at 5 11 21 PM
      • Choose File > Rename
      • Paste the texts you copied into the text box to replace the default title Screenshot 2024-05-28 at 5 10 26 PM
    • Move the file to RP017's folder in the shared Google Drive
      1. Choose File > Move > All Locations > Shared drives > Internship > Internships > Research > Research by Plan # and Name > RP017 > Move
      2. There will be a question to confirm change the ownership of the documents, and choose Move
    • Copy the link of the case study report of RP017
      1. Choose Share
      2. Choose Copy link and Done
    • In Resources # 2.05, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked
  • Complete each section of a case study report
    • Background
      • Provide a short summary about the significance of the research, rationale for conducting the research, and aims
    • Objective
      • Discuss case study method and rationale for use, participant recruitment, protocol/development of interview guide
    • Study Design/Data Collection
      • Discuss case study method and rationale for use, participant recruitment, protocol/development of interview guide
    • Data Analysis
      • Outline your data analysis plan, note themes of interest for case study
    • Key Findings
      • Provide your examination of the case, discuss findings as they relate to themes focused on during interview, present relevant facts and key problems identified
    • Recommendations
      • Present possible solutions/changes that are realistic, noting possible pros/cons
      • Support solution with outside evidence
      • Discuss any specific strategies for accomplishing proposed solutions/changes
    • Review each section
    • Update the Table of Content (page 2) of the case study report Google doc to reflect the page and section changes

Peer review stage of the case study report

  • Notify the Research Lead that the case study report is finished by leaving a comment in this issue
  • Add needs peer review label
  • Research Lead assigns a team member to conduct a peer review
  • The peer reviewer conducts the review of the case study report by leaving comments in the case report Google doc
  • The peer reviewer notifies the Research Lead and the author of the case study report that the peer review is completed
  • The author of the case study report discusses with the peer reviewer and research lead on the feedback

Finalize the case study report based on peer review feedback

  • After discussion on the feedback, the author of the case study report will incorporate any necessary changes.
  • The author of the case study report will add Ready for Research Lead label once the case study report is finalized and move the issue to Question/Review column
  • The author of the case study report will update the team about the changes made
  • Research lead will review the case study report
  • Research lead will add Ready for Product label once ready for product review
  • Product Team reviews and provides feedback
  • Product Team notifies the Research Team about any changes needed
  • Research Team incorporates any necessary feedback
  • Product sign-off

Update wiki page and action item spreadsheet

  • Update relevant WIKI page (See resources)
  • Create the action item spreadsheet for this research plan
  • Update the action item spreadsheet based on research findings and insights
  • Share the action item spreadsheet with Product
  • Product sign-off

Resources/Instructions

Resources needed to complete issue

1.01 Wiki Intern Research Overview Page
1.02 Research by Participant Type Folder on Google Drive
1.03 Overview of writing a case study analysis in business
1.04 Sample case study analysis;
1.05 Article that provides background/definition of case study - It also includes example case studies as well as a checklist for assessing the quality of a case study report;
1.06 Case Study Methodology of Qualitative Research: Key Attributes and Navigating the Conundrums in Its Application
1.07 Case Study Method: A Step-by-Step Guide for Business Researchers
1.08 Methodology or method? A critical review of qualitative case study reports
1.09 UCSF libraries case studies research guide - It includes books, resources/examples, and latest articles on case studies as a research method
1.10 a step-by-step checklist for conducting a case study - This issue comment provides more context on the checklist this issue is following
1.11 TWE: Research: Case Study Template

Resources gathered during the completion of the issue

2.01 RP017 Wiki Page
2.02 Google Drive RP017 Folder
2.03 RP017 Research Plan
2.04 RP017 De-identified Transcript
2.05 RP017 Case Study Report

@pandanista

This comment has been minimized.

@pandanista

This comment has been minimized.

@pandanista

This comment has been minimized.

@ExperimentsInHonesty ExperimentsInHonesty moved this to In progress (actively working) in P: TWE: Project Board Jun 10, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the PBV: research all issues for the research team label Jun 10, 2024
@adarosh

This comment has been minimized.

@pandanista

This comment has been minimized.

@adarosh

This comment has been minimized.

@pandanista

This comment has been minimized.

@pandanista

This comment has been minimized.

@adarosh

This comment has been minimized.

@adarosh
Copy link
Member

adarosh commented Sep 18, 2024

Hi @pandanista, please see below for update.
Progress: Met with UXR lead on 9/10 for update. Reviewed draft of themes/key findings. Based on review of transcript, the numbers used to identify interns in dashboard may not be correct. UXR lead will check with team if this is still an issue.
Blockers: None
Availability: 1-2 hours
ETA: Will provide update at next UXR meeting.
Pictures or links* (if necessary): N/A

@pandanista
Copy link
Member Author

pandanista commented Sep 24, 2024

@mayankt153

This comment has been minimized.

@pandanista

This comment has been minimized.

@pandanista

This comment has been minimized.

@pandanista

This comment has been minimized.

@pandanista

This comment has been minimized.

@pandanista pandanista moved this from In progress (actively working) to Prioritized Backlog in P: TWE: Project Board Oct 31, 2024
@ExperimentsInHonesty ExperimentsInHonesty added the Ready for product When the issue is ready for product team to review label Oct 31, 2024
@ExperimentsInHonesty ExperimentsInHonesty moved this from Prioritized Backlog to New Issue Approval in P: TWE: Project Board Oct 31, 2024
@ExperimentsInHonesty

This comment has been minimized.

@ExperimentsInHonesty
Copy link
Member

@pandanista The Dashboard team is done cleaning up the confusing comment that we left on this issue. You can have it back now. It still needs a cleanup, by research.

@ExperimentsInHonesty ExperimentsInHonesty added ready for research lead and removed Ready for product When the issue is ready for product team to review labels Jan 26, 2025
@pandanista
Copy link
Member Author

pandanista commented Jan 28, 2025

  • This issue is ready to be put into the prioritized backlog after confirming the answers to the questions with Product in the comment

@Rabia2219
Copy link
Member

  • This issue is ready to be put into the prioritized backlog after confirming the answers to the questions with Product in the comment

@pandanista

  • The dashboard is for IS21
  • The intern numbers are different because you are looking at the roster for IS22 cohort and the interview participants from the IS21 cohort

@ExperimentsInHonesty
Copy link
Member

further clarification

The person I interviewed was in both Cohorts. So he has two numbers. The dashboard was just for IS21, so use the IS21 intern number

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New Issue Approval
Status: New Issue Approval
Development

No branches or pull requests

6 participants