Suggested by @JAufrecht at the DR-Editing meeting: let's sketch out several common scenarios for how DR works with product teams, including the type of research we perform and what it yields, as well as what we need from the team in terms of timelines, etc.
This seems like it fits under our overarching 'research communication' epic. Not sure what the priority is yet, though.
Joel took a first stab at an outline of two scenarios:
Goal for each task/project: Reach mutual understanding on what the scope of work should be.
- Generic outline:
- Problem definition. (As PO understands collective needs of users. As DR determines based on samples of users. Other sources)
- Generative "front-end research". User study/survey
- define question
- determine target population
- craft survey
- run survey
- analyze results
- Evaluative research. Usability Testing
- DR defines test tasks together with PO
- break problem definition into test tasks
- figure out size and characteristics
- DR recruits testers
- PO provides a working prototype (and stability)
- DR tests prototype
- feedback, review, repeat - either minor tweaks, or re-think