prime-reportstream icon indicating copy to clipboard operation
prime-reportstream copied to clipboard

ResearchOps: managing a roster of research participants

Open dylansmith-Nava opened this issue 1 year ago • 0 comments

User story

As a ReportStream researcher, I want to complete the Managing a Roster of Research Participants section, so that current and future researchers have a centralized playbook to know how to effectively and securely store participant information for any research initiative.

Summary: Establishing how we as researchers should collect information from the participants that we recruit, and where to maintain that information securely and safely, as, perhaps a "roster".

Dependencies:

  • Reading through the Conducting Research section

Sub-sections:

  • N/A

Background

Prior ResearchOps documents were disjointed and spread among different teams and projects. Likewise, there is not yet one source of truth for ResearchOps strategies, and as such, any previous strategies are not widely practiced within the design team. Revisiting the ResearchOps documents will be helpful to understand which guidelines are still relevant for our team, what gap(s) in knowledge and/or strategy are occurring, and what new material(s) may need to be made.

Risks/Impacts/Considerations

  • The exact folder location where participant information should be stored may be adjusted over time, and should be audited with each adjustment to make sure safety and sanitization standards are being met
  • Any new paradigms here may require shifting around prior participant data in other folders to the correct, new location
  • Beginning work on some sections may be dependent on the completion of others (see ReportStream Design and Research: Quarterly Roadmap)

Open questions

  • Where should participant info live?
  • How much participant info should be visible? How much should we be protecting PII?
  • Are there any USDS or PRIME-wide standards we should be following?

Links

Acceptance criteria

  • [x] Adjust ticket estimation, task breakdown, and sub-sections as needed
  • [ ] Create initial draft of section
  • [ ] Shareout of WIP as needed with Design Lead, Product, and Engineering for iteration
  • [ ] >90% finalization of section (barring grammar, spelling, etc.)

Out of Scope

  • Working outside of this identified section - if your work seems to be spilling into other sections, please bring this up at any Design/Research meeting!

dylansmith-Nava avatar Apr 15 '24 15:04 dylansmith-Nava