Copied across from https://phabricator.wikimedia.org/T107592#1598337
Let's edit the description until we have clear concrete survey to run.
The impetus behind this project was that in Q1 planning, when we did the walk-throughs (with JOH playing an excellent old man) it was obvious that we all had different assumptions about what the relative weight of our primary use cases were. As someone pointed out on an unrelated thread this week, knowledge of the present can reinforce existing use cases and miss opportunities, but I believe it is a necessary first step towards identifying the usage patterns we need to protect and even improve, while we are exploring any new opportunities:
So. I want to end up with a % by platform (and ideally project and even country) of what are users are coming to WP for.
- learn what something is (summary/definition, e.g. what is strep throat)
- lookup a specific fact (e.g. "what treatments are used for strep throat")
- learn about a subject (e.g. "I need to browse around early american union activity")
- deep analysis of a specific topic (e.g. "I want to know everything about the rock dove")
- just killing time
- other _____
I want to end up a dataset from which I can derive:
Desktop, En, US, 60% learn what something is
Mobile, En, US, 10% lookup a specific fact
Thoughts on whether or not that goal is stupid or how it can be improved?
How we get that is up to Joaquin and Anne, with support from Design Research (to the extent that it is helpful). It might be that we ask each user about each option, but it also might be that we just ask one at a time in buckets and compare the "yes"/"No" ratio.
My only concern with the current plan is that the in-article embedding means that certain kinds of articles will surface the survey sooner or later (depending on lead paragraph length). We need to think seriously about how to correct that bias. A top-of-article (below banner) or overlay are the only options I can think of.