This repository has been archived by the owner on Jun 2, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 62
Q3 2019 OKRs: Research/test plan (umbrella issue) #207
Labels
topic/design-ux
UX strategy, research, not solely visual design
Comments
jessicaschilling
added
topic/design-ux
UX strategy, research, not solely visual design
OKR: Front-Page Quiz
labels
Jul 11, 2019
ex - num total clicks of the accordion per day, decrease in bounces, etc |
7 tasks
jessicaschilling
changed the title
Quiz: Metrics/feedback followup for front-page quiz
Quiz: Metrics/testing followup for front-page quiz
Aug 19, 2019
Starting a working document for the test plan here: |
jessicaschilling
changed the title
Quiz: Metrics/testing followup for front-page quiz
Quiz: Metrics/testing test plan and followup for front-page quiz
Aug 19, 2019
jessicaschilling
changed the title
Quiz: Metrics/testing test plan and followup for front-page quiz
Quiz: Research/test plan and followup
Aug 19, 2019
jessicaschilling
changed the title
Quiz: Research/test plan and followup
Quiz and personae: Research/test plan and followup
Aug 20, 2019
jessicaschilling
changed the title
Quiz and personae: Research/test plan and followup
Quiz & Personae: Research/test plan and followup
Aug 20, 2019
jessicaschilling
changed the title
Quiz & Personae: Research/test plan and followup
Q3 2019 OKRs: Research/test plan (umbrella issue)
Aug 27, 2019
All issue dependencies closed, and all results noted in the summary document and/or in individual GitHub issues. Summary document is now also in main docs repo readme for future reference. Closing this issue -- thanks all! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is an umbrella for creating, executing and reporting on a research and test plan related to our primary Q3 OKR deliverables:
While in-stream reporting on each of those deliverables should happen within their respective GitHub issues, all results should be captured in the test plan working document that is being managed in this issue.
This issue can be closed when all the testing in the test plan is complete and learnings have been captured adequately: noted in the test plan, captured in GitHub issues for future fixing, or some combination of the two.
The text was updated successfully, but these errors were encountered: