Page MenuHomePhabricator

[Request] Continuous research / insight-->decision lifecycles
Open, In Progress, HighPublic

Description

  • Context. Provide a short paragraph with some background context for your request, please include links to relevant material.

Per @AAlhazwani-WMF's memo document, the aim is to build a cohesive, ongoing, shared understanding of newcomers that the team(s) can draw from when prioritizing work. The ideal is to focus more strategically instead of the more common emphasis on reactive, tactical solutions; hopefully finding the right solution for the right problem, instead of building the solution right (and possibly for the wrong problem).

  • Description.What is your request about?
  1. Ideating a continuous research process and/or program
  2. Executing on the concept and testing its viability and effectiveness
  • Expected Deliverable. What is the ideal outcome or result of your request?

Ongoing feed of findings and recommendations from a combination of ongoing research sessions and compiled feedback from community-facing teams such as the ambassadors informing product development and direction, and creating a backlog of actionable recommendations for future APP/team planning cycle integration.

  • Estimated Effort. Please provide an estimate of the amount of work needed to complete this task, if known.

3 months of initial process/program ideation and co-creation, and ongoing work towards the same.

  • 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.

I need this task resolved in:

  • 1 month.
  • 3 months.
  • 6 months.
  • Whenever you get to it :-)

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.

Details

Due Date
Feb 23 2026, 6:00 AM

Event Timeline

dchen changed the task status from Open to In Progress.
dchen claimed this task.
dchen triaged this task as High priority.
dchen added subscribers: Miriam, DKumar-WMF.

Reviewed existing documentation from Amin and held a meeting 11/25 discussing

  • desired outcomes/strategic impact
  • ways to frame and structure the experiments to minimize potential pushbacks and risks
  • potential candidates for initial pilot runs

Will write and/or diagram out the process and stage 1-2 pilots in Dec/Jan.

Not much additional updates this week but will be sharing a write-up of the proposed process end of week/early next.

Setting due date for when we want the first round of the continuous research sessions to happen, at the latest.

made some updates to the program brief document, and in conversation with Bethany on how best to operationalize and understand capacities/limitations/considerations.

continuing to work with the team on specifics on recruitment/survey/database structure, @Isaac on language for a related hypothesis, and legal for privacy policy and release form for use with this program.

Update week before last:

  • Clarified with Growth about the current status of the welcome survey and whether it would be a viable source of potential participants
  • Coordinating with Growth, Product Analytics and Isaac/Bethany on immediate and forward-looking recruitment paths for program participants
  • Will push for Growth to reactivate the research opt-in field
  • Ask Growth to assign some resources to maintaining the survey response-datalake integration
  • Product Analytics is primed to provide help with query review, datalake integration support if needed, etc.
  • Working with Bethany on scheduling and tracking documentation
  • For the research program overall, one first session is scheduled for next week
  • Recruitment for this specific hypothesis (core cohort of 10 participants) will begin soon and sessions are slated to begin week of 2/23

and last week:

  • Completed first interview for the overall program today, with
  • Kirsten Stoller observing! Though not a newcomer, the participant provided a lot of usable feedback relevant for Growth features/initiatives (existing features and potentially the newcomer homepage/moderator dashboard merger) and the recognition space ( Ilana Fried and the Collection team)
  • Another iteration for the overall program will include 1-2 participants and is scheduled to occur the week of 3/9
  • 3 interviews specifically for this KR are beginning/scheduled for next week. Goal is to complete the full ~10 first-round interviews with participants in the coming two weeks, and a round of follow-ups beginning 3/18
  • Continuing to coordinate with Bethany Gerdemann on scheduling and tracking documentation, and with Product Analytics to review and refine the participant recruitment queries
  • Growth may not be able to work on the full slate of welcome survey/datalake bridge currently, but we can make do with the querying approach
  • Tangentially related; Bethany and I are working with Ellen Magallanes, Leila Zia and others to push for a unified research/experimentation opt-in/out system for more clarity and ease-of-use among all parties involved
  • 5 sessions completed this week and all 3/5 of the timezone-aligned sessions were attended by Growth team members! One more is scheduled in about an hour, which if completed will bring the total sessions this week to 6
  • Shareout plan discussed with team + Isaac and shareouts will occur early next week and some synthesis in process
  • Bethany has engaged Product Analytics to review the newcomer user query template, which will conclude in 3-4 weeks. We can use this to modify in a modular way future queries so we do not have an ongoing PA dependency
  • Week of 3/9 session(s) may be bumped to a week in April, depending on whether a separate project will require my interviewing time/capacity

Progress update:

  • 6 first round sessions completed last week and 2/6 sessions were observed!
  • 11 total first round sessions completed, and 11 follow-up sessions have been scheduled for 3/18-31
  • Shareout message posted, and Kirsten/Amin/others have been sharing text-based and video clip-based snippets of interest as well

Emerging blockers or risks:

  • None that are challenging the completion of interviews, but there are some considerations to flag:
  • logistical/timing difficulties: direct observation and exposure to participants' narratives and walkthroughs is a very important component of continuous research goals. however, there are limitations in that the interviews must consider timezone and availability for at least three parties (interviewer, participant, and observer(s); internal overlap is already limited with Pacific and European/African timezones). overall, 6 of 12 sessions completed thus far have had an observer.
  • as a tangential add-on/counter; there are risks that observing once or only a couple times will crystallize limited experience as representative; this is an argument for keeping the continuous research ongoing so that exposure can be ongoing for members of the team
  • legal limitations: shareouts are ideally limited to google drive recording links with associated timestamps. ideally, we would be able to download, clip with third party tools and share the clip, or upload to a 3rd party cloud service and share timestamped links, but this is a legal limitation and best practice to refrain from 3rd party solutions that have not been evaluated and are otherwise unnamed in the privacy policy and release form.
  • additionally, regardless of the sharing method, reminders must be set to delete recordings and any shareouts of the same by the specified retention period for the program; this means that all related shareouts, links, notes and related data must be anonymized or deleted.
  • general need to calibrate on shareout and communications to reduce noise but increase exposure and awareness overall
  • Receiving feedback from Growth team and others on the shareout document!
  • Talking through documentation, reference, and shareout options
  • Met with Kirsten Stoller, Amin Al Hazwani, and Bethany Gerdemann earlier this week to discuss repository, live observation vs viewing recordings, clip-making tech options, and how best to achieve continuous research program goals
  • Met with Isaac Johnson early in the week as well to discuss structure/questions for follow-up sessions beginning this week
  • Will be sharing week 3 findings this week with stakeholders
  • Completed 3 sessions thus far from the round of follow-up interviews
  • Meeting with Bethany and rep from Dovetail and Reduct this week to discuss research finding repository options
  • Completed second/follow-up round of interviews with @Isaac's WE1.9.1 cohort on 3/31, wrapping the longitudinal element
  • Meeting with Isaac 4/2 to discuss preliminary findings around motivations, challenges, etc
  • Amin and I co-presented a continuous research program update at 3/31 Design and Research team meeting
  • Bethany and I met with Dovetail, Reduct, and Descript re video clipping and repository options; going through Legal review for our use and will trial once complete