-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IA1: Testing & iteration #19706
Comments
|
Community testing artefacts are here - permission to access is needed on a case by case basis |
@kittykat thx. I just updated the issue with a summary of work and included this in there. On (1) In-app feedback, we're currently experimenting with using a GitHub project board so we can maintain context directly in GitHub. If you have any bright ideas around automation/adding labels based on inputs (e.g. if a user consents to be contacted) they would be greatly received! |
We are done with testing and processing results for IA1, further testing will be part of IA2. Metrics have been split out into their own epic outside of IA, so closing this issue. |
We'd like to test & research the Phase I IA experiments in chorus, to learn, iterate and gain confidence in changes to ship to production. We'll use the following methods:
1. In-app feedback (@kittykat )
2. Moderated tests, internal (@niquewoodhouse )
3. Community tests (@niquewoodhouse with support from @kittykat )
We should translate findings into separate issues, or consider tracking small snags in the final build issue.
4. Organic feedback via community (@kittykat )
5. Unmoderated tests, external (@niquewoodhouse )
6. R&D PostHog (@kittykat )
Note: While this issue is public, most of the links in this issue are private and will not be made public, to preserve folks privacy.
Small iterations, based on testing
Some of the above testing has led us to identify some iterations to the experiments that will improve them for further testing.
The text was updated successfully, but these errors were encountered: