Page MenuHomePhabricator

Data wiring requirements for Image recs
Closed, ResolvedPublic

Description

Background

The Android team is bringing Image Recommendations to the app.

We want to measure:

Metric specific Leading Indicators: Indicators to be captured after 15 days
Image rejection rate does not exceed 29%
Edit over-acceptance rate (never skip or reject recommended images) does not exceed 35%
Task completion rate is not below 30%
Revert rate does not exceed 18%

Validation

  • KR 1.1: 2000 articles have images in a 30 day period
  • KR 1.2: Average at least 8 edits per day per unique user
  • KR 1.3: 15% of eligible Suggested Editors try image recommendations task
    • by app_install_id, just by username in mediawiki_history)
  • KR 1.4: 70% of those users complete the task again on a separate day in a 15 day period
  • KR 1.5: Reject and Accept rate does not deviate from Mobile Web or MVP by more than 10% (redundant metrics from
  • KR 1.6: DAU of Suggested Edits increase overall

Guardrails

  • KR 1.1: Feature does not worsen gender or geographic bias*
  • KR 1.2: Less than 5% of users report NSFW or offensive content
  • KR 1.3: Users spend at least 10s evaluating a task before publishing it
  • KR 1.4: Bounce rate does not exceed 50%
    • Bounce rate defined as users that click Yes then abandon the flow before publishing
  • KR 1.5: At least a 35% task completion rate
    • Defined as users that click on Add an image as a task, and actually clicks Yes, No or Not sure (interact with the feature)
  • KR 1.6: Revert rate does not exceed 18%

Curiosities (nice to have)
KR 1.1: Do these numbers differ by language or user tenure?
KR 1.2: If this is a user’s first suggested edit, do they go on to try others?
KR 1.4 At what point in workflow are most frequent dropoff events?
KR 1.3: Feature perception by geographically underrepresented groups on large language wikis

Target Quant Regions and Languages

  • Spanish Wikipedia
  • Portuguese Wikipedia
  • Persian Wikipedia
  • Hindi Wikipedia

Target Qualitative Audience

  • Spanish and Portuguese speakers in LATAM and Caribbean countries
  • Hindi speakers in India
  • Persian speakers across diaspora
  • No more than 40% of our testers should identify as male

Task

  • @SNowick_WMF to create schema docs for new image recommendation schema
  • Engineers to wire up instrumentation based on schema doc from @SNowick_WMF

Designs
https://www.figma.com/file/OUC0Pql9nA4tRsDBY29Un8/add-images-2023?type=design&node-id=187-15240&mode=design&t=o9kzURPCT0RizeUk-0

Event Timeline

Draft document that outlines additional events we will need to track: Android Image Rec Instrumentation DRAFT . Some questions remain w/r/t finalized user flow design, particularly in Figma the depicted caption edit screens are identical to task Add image caption but this is unlikely to be final version.

Will be adding a schema design outline to the DRAFT doc pending further review. We have an additional schema structure that was used by Growth that we may borrow elements from.

Some questions for design/engineering came up as I was working on schema, documenting here:

  1. Mentioned in requirements - edge case mechanism for when image suggestions 'ran out' ie users cycled through all available image suggestions for the Wiki they're in. Don't see this in Figma, we will need to add this and track when this occurs. Adding @scblr since he's not on this ticket.
  1. In the rejection dialog (images 07 and 08 in Design) - rejection reason popup appears when user selects 'Not sure', the dialog should open on 'No' selection.
  1. The design spec says "No" triggers the dialog which my schema docs will reflect. Still want to verify what is next event after user submits reasons (end task or new image?)

Items below are Resolved

  • Note after discussion with @JTannerWMF - the design specs in T327534 specify that no skip option should be available for users, this deviates from Growth design. This will mean our retention and drop off rates will be different metrics, let's discuss options and/or modifications. The 'Not Sure' option functions as 'Skip'

Mentioned in requirements - edge case mechanism for when image suggestions 'ran out' ie users cycled through all available image suggestions for the Wiki they're in. Don't see this in Figma, we will need to add this and track when this occurs. Adding @scblr since he's not on this ticket.

Here you go @SNowick_WMF 👇

@SNowick_WMF
Could you please close this task if everything looks good?