Topic on Talk:Reading/Strategy/Archive 2

Identifying problems before looking for solutions

2
Pginer-WMF (talkcontribs)

First of all, thanks for sharing the work on the strategy early, this is really great for participation.

In the bullet list on the strategy page, the second point (which seems to be the next step) is about "Q2 feature(s)". I think features (i.e., solutions) should be driven by the problems identified. That may be an assumption but it would be great to represent it more explicitly: make sure the problems to be addressed (as well as the evidence they are happening and their potentially measurable impact) will be captured before exploring solutions.

ABaso (WMF) (talkcontribs)

The Q2 work around features is interspersed mainly to acknowledge that we need to to do the strategy work in tandem with Q2 work.

I believe we should be able to do some quick user surveys to gauge sentiment for Q2 work. Failing that, I think it will be helpful to look back at data, if available, and qualitative research as a basis for prioritization.

Reply to "Identifying problems before looking for solutions"