CDCgov
ResearchOps: Synthesis and Shareout
User story
As a ReportStream researcher, I want to complete this new ResearchOps section, so that I can help centralize and formalize new ResearchOps materials so current and new Designer/Researchers know a)what to do b)when to do it, and c)why (purpose) when undertaking new research initiatives.
Summary: Establish how we should formally close out of our research initiative. Inclusive of discussing debriefs, any shareouts, and final reports.
Sub-sections:
- Overview
- Specific channels for sharing synthesis
- Synthesis process
- Final review of materials
- TBD
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
- Beginning work on some sections may be dependent on the completion of others (see ReportStream Design and Research: Quarterly Roadmap)
- Tools and methods will change over time, requiring periodic updates to the ResearchOps doc
- TBD
Open questions
- What is the right material to create or include?
- How can I ensure that the research team will have buy-in to the section I am creating?
- TBD
Links
Acceptance criteria
- [ ] 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!
- TBD
