TWE: Create Guide for Thematic Analysis

[bradyse]

Dependency

• TWE: Research: Checklist for Rapid Qualitative Analysis (RQA) #338
• TWE: Research: Guide Creation: Interview Expert (Linda) #330

Overview

We need to create a guide for the same thematic analysis that was conducted on the IS21 interview data so that future TWE UXRs can replicate the process on interview data that has yet to be analyzed.

Action Items

• Meet with UX Research Lead from IS21 (Snigdha) and walkthrough the entire analysis and taking notes along the way (see "Synthesis" section of RP1's wiki page)
• Click on TWE's Generic Report Template and click "Use Template" then move the file from your personal drive into the Internship shared drive in the following file path: Internships > Internships > Research > Guides and How-Tos
• Rename the file as TWE: [SPECIFIC SKILL] Guide (the part of the title after the colon can be whatever is most accurate and makes sense. It could be something like "Thematic Analysis using Card Sorts Guide").
• On the title page rename the title to be "How To - [enter whatever this guide is] for UX Researchers" (see in Resources example of a completed guide for the UI/UX Community of Practice)
• Use the document headings to organize the guide into logical sections.
• Provide screenshots of de-identified information.
• Update the Table of Contents and Footer when you are ready for review.
• Conduct Peer Review of Guide (see comment for action items)
• Have current UXR Lead review when you are finished.
• Have PM review and sign-off on guide.
• Update Research Guides Templates Wiki page with link to finished guide (See resources)
• Release dependency on TWE: RP006: Intern Intake Interviews: Create Data Presentation #322 and if it's the last dependency, move 322 to the new issue approval column

Resources/Instructions

Guide for Thematic Analysis

• TWE: Guide for Thematic Analysis

Other Resources

• Wiki page for RP001: IS21 Interns
• TWE: Template: Generic
• Example of a Completed Guide
• Wiki: Research Guides Templates

[adarosh]

Issue update: Reached out to Snigdha to set up a meeting. She said she will be attending the Internship UX Meeting tomorrow (9/13/2022)

[adarosh]

Issue update:

1. Progress: Found resources from Brigade Organizer’s Playbook Project on Internship drive
2. Blockers: Reached out to Snigdha with possible days/times to meet this week, waiting for response to set meeting time
3. Availability: 4-6 hrs
4. ETA: TBD after meeting
5. Pictures (if necessary): N/A

Resources from the Brigade Organizer’s Playbook Project (How To: Synthesize Research to Generate Insights)- https://docs.google.com/document/d/18piMcr9mSBXauTyhSeuFnE_UKrZLhMv1C8byLJRkJ64/edit#heading=h.mmuzn9vvc61o

[adarosh]

Issue update:

Progress: TWE guide template moved to shared drive; Scheduled meeting with Snigdha - 9/30 from 6-7:00pm EST
Blockers: Meeting with Snigdha
Availability: 4-6 hrs
ETA: TBD after meeting
Pictures (if necessary): N/A

[adarosh]

Issue update:

Progress: Meeting with Snigdha was moved to 10/7 at 1:00pm. Discussed the goal of the guide and provided her with identified resources, including BoP's How To: Synthesize Research to Generate Insights (link in comment above) and IS21 Research Slide Deck. Snigdha will begin to outline the guide based on her IS21 analyses and reach out to me with identified sections that I can help fill in. She also said she can be available via Slack to the TWE research team for any questions re: analyses.
Blockers: Waiting for draft outline
Availability: 4 hrs
ETA: Snigdha provided an estimate of 2-3 weeks for guide
Pictures (if necessary): N/A

[adarosh]

Issue update: Discussed guide in TWE UXR Team Meeting on 10/11. Team consensus was that guide should focus on Thematic Analysis from IS21.

[adarosh]

Issue update:

Progress: Snigdha drafted document on 10/23. Have adjusted formatting throughout, made minor edits, added example images to draft.
Blockers: Document is ready for UXR Lead review and peer review
Availability: N/A
ETA: N/A
Pictures (if necessary): N/A

[bradyse]

Setup for a Peer Review

@bradyse to complete the steps below:

• Confirm with UX Lead that this document needs a peer review.
• Check if the Issue Overview clearly defines why this document needs to be created or updated. If it is not clear, add that information to the overview in 1-2 sentences.
• In the Resources, clearly identify the link to the document being created or updated that requires a peer review (use subheadings if needed).
• Copy and paste the Action Items for Peer Review into a comment of the issue.
• Customize the Action Items according (adding items that are more relevant to this issue and removing items that are less relevant).
  • Replace the text in square brackets with the name of the document that requires a peer review (use the same name as it is called in the Resources).
  • If you have a specific task that you want the Peer Reviewer to accomplish for their peer review that is nuanced to your issue, add that as a final action item to the list.
• Determine who will do the peer review and unassign yourself to this issue and assign the peer reviewer to this issue.

Action Items for Peer Review

@lkawentel to complete the steps below:

• Review this issue
  • Read the issue overview to learn about why this document was created.
  • Locate draft of the document or spreadsheet in the Resources.
• Review draft
  • Preview the draft quickly to get a sense of how the draft is structured and the type of content.
  • Review the structure of the draft to ensure that the headings (in a Google Doc) or columns (Google Sheet) are clearly identified.
  • Determine if the information is communicated in a way that is concise, precise, and free from jargon.
  • Identify whether the draft adheres to the basic branding guidelines for the project (see Branding or Design wiki link in Resources).
• Provide feedback
  • Add feedback in the form of (1) questions and/or (2) explicit instructions for how the content should be improved. Feedback in a Google Doc should be given in the form of document comments. Feedback in a Google Sheet should be given in the column labeled for Peer Review.
  • Determine the accuracy of the content for each section (doc) or row (sheet). If you find an inaccuracy, error, or mis-categorization, explain how the information presented could be improved.
  • For each suggested improvement, provide a link or reference within your comment to justify your suggestion.
• Specific to this issue:
  • Add any information or comments that would be relevant to rapid qualitative analysis. If any information differs from that approach, explain how it differs and why someone might use Hamilton's process instead
• Once all the steps have been completed, reach out to the original owner of this issue to determine if they can complete the next steps in the issue.

[lkawentel]

I have provided feedback on the Google doc titled "TWE: How to Conduct Thematic Analysis." It would be helpful to have another person take on the step of reviewing the spreadsheet and Figjam file. I unfortunately do not have time to review the files for accuracy and explain how the information presented could be improved.

[ExperimentsInHonesty]

Moved this issue out of the In progress because no one was assigned. Re review issue and see if it is ready for prioritized backlog

[ExperimentsInHonesty]

• This is being moved to the icebox until Issue TWE: Research: Checklist for Rapid Qualitative Analysis (RQA) #338 and TWE: Research: Guide Creation: Interview Expert (Linda) #330 is complete, then it would be good if Brian (if he is still available) could do a compare and contrast and make a presentation at the UI/UX community of practice