Page MenuHomePhabricator

[Request] Qualitative feedback for WE1.6 Task Prioritization KR
Closed, InvalidPublic

Description

Please provide all the following information:

  • Description.What is your request about?
    • Since we are using qualitative feedback to measure our success on WE1.6 when it closes at the end of March 2026, we are hoping this could be driven by Design Research in partnership with the KR owner (@Cparle) and hypothesis owner (@KSiebert).
    • In our 24 Nov office hour, @dchen suggested that task prioritization/watchlist could also incorporated into continuous research.
  • Expected Deliverable. What is the ideal outcome or result of your request?
    • A document containing a synthesis of qualitative feedback from watchlist users after CommTech has released the watchlist labels feature, so that we can understand whether or not they can more easily organize their work and act more effectively on taking patrolling or editing action.
  • Estimated Effort. Please provide an estimate of the amount of work needed to complete this task, if known.
    • TBD
  • Priority Please indicate a priority of your task and a small description of what it would unlock for you. We ask you to leave this task as “needs triage” since your request will go through a Backlog refinement process where our team will prioritize the work.
    • This will be a primary input in our KR scoring for WE1.6 in early April 2026, so would classify it as high priority.

I need this task resolved in:

  • 1 month.
  • 3 months.
  • 6 months.
  • Whenever you get to it :-)
  • Other. Do you have any other questions or comments ?
    • If this work is prioritized by Design Research, would you need help from CommTech and/or Moderator Tools to find a list of users to reach out to?

For use by WMF Research team; please leave everything below as it is:

  1. Does the request serve one of the existing Research team's audiences? If yes, choose the primary audience. (1 of 4)
  2. What is the type of work requested?
  3. What is the impact of responding to this request?
    • Support a technology or policy need of one or more WM projects
    • Advance the understanding of the WM projects.
    • Something else. If you choose this option, please explain briefly the impact below.

Event Timeline

Thanks Lauren - letting you know I've seen this, and just haven't had a chance to discuss with Daisy yet because of the holidays last week and her being out sick this week.

It sounds like this is research that needs to happen after the feature launch in Jan, and concluded by the end of March 2026, if I understand correctly.

This sounds like work we should be able to take on, just depending on what Daisy and Sonja see as the highest-priority needs for Design Research for Q3, across WE1.

DKumar-WMF triaged this task as Medium priority.Dec 8 2025, 2:14 PM

Daisy has discussed this project with Sonja and confirmed its prioritization.

Moving to Research-January-March board.

Daisy, please set the due date once you have decided scoping of this work, thanks.

Conversations with Karolin, Cormac, et al regarding scoping. Decision tree unclear for a period due to the former leaving for sabbatical this week and the latter switching teams. Joy will likely be taking over the element of DR support and Sammy will take over WE1.6.1, with the KR ownership overall still TBD.

Meeting scheduled with @SonjaPerry early next week to clarify scoping, timeframes, any decisions to be made and these will then be discussed with @Samwilson asynchronously to finalize project plan.

Met with @SonjaPerry last week and a follow-up meeting has been scheduled with @TAndic to discuss a survey with some free-form fields in lieu of a full set of watchlist user interviews.

  • Met with Tanja again to discuss specifics about what is technically feasible
  • Met with Daniel (contractor with the team) to ascertain what is possible for surveys deployed on special pages
  • Next update will be later this week after Daniel has done some exploration into the containers concept (documented by Jon Robson, but not yet implemented)

There is not an immediate action item that will result from this survey, so the timeline is not as urgent. We are taking the time to experiment with the container/QS option so that it can be utilized/implemented more expeditiously in the future.

Received update from Daniel that experimentation for container/QS has not been completed yet and that the timeline for completing the deployment, response gathering, and analysis will likely take longer than being able to wrap by end of April; requested experimentation to be completed by EOW if possible. Will inform team about this update and determine next steps.

I've discussed the timeline with @SonjaPerry, and we have decided to stop the WE1.6 Task Prioritization key result at the end of April, rather than extend it a second time. We will plan to score the KR based on usage stats + any qualitative feedback we've received already.

Based on our earlier conversation about the qualitative feedback only being used for KR scoring, rather than informing immediate strategic work in the Contributors objective, this decision would free up Design Research's time to focus on higher priority projects.

Thank you for the time spent on this thus far @dchen! I'm optimistic that we'll be able to leverage the capability to enable QuickSurveys on special pages in the future, but we can consider the work removed from the WE1.6 critical path.