[Research Recruitment] FRA Research

[reitermb]

Description:

Tracker for research recruitment. 🔐 Original FRA contacts excel sheet/tracker is found on Mattermost / Raft Sharepoint to protect participant identity

AC:

• [x] Research recruitment email w/ booking link has been sent
• [ ] Targeted Participants Recruited: In Progress
• [ ] Changes to recruitment criteria have been documented if recruitment/target participant pool has been expanded.

STT	Date	Time	Zoom Link	Scrubbed Transcript/Notes
1	Thursday November 14, 2024	12:30 – 1:30 EST	Join Teams	P1 Transcript
2	Thursday November 14, 2024	4:00 – 5:00 EST	Join Teams	P2 Transcript
3	Monday November 18, 2024	12:00 – 1:00 EST	Join Teams	P3 Transcript
4	Friday November 22, 2024	3:30 – 4:30 EST	Join Teams	P4 Transcript pending
5	Tuesday December 3, 2024	5:00 – 6:00 pm EST	Join Teams	P5 Transcript pending
6	TBD
7	TBD

Supporting Documentation:

• Research plan

[lhuxraft]

11/13/2024: Landed two new participants, added a tracker

[victoriaatraft]

General Takeaways From Interviews

Providing for situational awareness, transcripts found on gitbook

P1 Post Session Takeaways

• Surprised how seamless the one page submission history was. Asked about that did you notice it was on the same page and probably a good thing that the answer was no. It grabs the eye and it just worked.
• A lot of the assumptions we gone in have proved true so far. We validated the filter ideas of potentially and the needed data and here's where the problem is and the feedback. Sounded like the standalone one could work given additional data, but would be curious with folks who aren't well set up with automation and high quality data processes in house and what reactions we get there.
• The block of text at the top of the excel sheet was a good call out to processing data. -> add a prompt for future sessions, as needed.
• No fully trained person to replace which is a constant theme across research.

P2 Post Session Takeaways

• Disclosure on the Excel sheet: Nice to have disclosure but it's in the way on the since they use SAS
• Interested in the way the seem to be thinking about the reports. We think they are lumping the supplemental optional with the required one.
• County administered element is also interesting. Counties don't necessarily do it the same way. There was an impression there was a central office and people were responsible for their own jurisdiction but there may be some variability in the county level like states.
• We don't know which version of the year is captured in the exit date in the table. Is it Fiscal or Calendar. It was a good callout to be thrown off.
• People are leaning towards Version A
  • 3 measures on the work outcomes (exit date, ssn, ?)
  • 1 for secondary school attainment
  • SSN sharing agreement
  • CSV
• tripped up by exit date
• communicate pilot version availability
• UX internal experiment: Can we a csv same a filtered default when opened in excel. Can we save it and send it to each other
• Participants Interested in testing the pilot

P3 Post Session Takeaways

They will reach out to their IT person and use the original email and set up an appointment People submitting are not those doing the data prep. They are not the people doing the corrections themselves. So having the alternative person will be great.

@reitermb cc: @klinkoberstar @ADPennington @lfrohlich

[lhuxraft]

11/18: Update the calendar to additional session

[lhuxraft]

11/20: Monday session cut short, getting in touch of IT in that STT that are users. Will plan to set up a follow-up session once proper group is identified

[ADPennington]

@lhuxraft can you check with UX on ticket for the research synthesis for this work? Please tag ticket here 😄

[victoriaatraft]

@lhuxraft can you check with UX on ticket for the research synthesis for this work? Please tag ticket here 😄

Just made one as a WIP https://github.com/raft-tech/TANF-app/issues/3297 :)