Page MenuHomePhabricator

Set WE 1.7 KPI and impact target
Open, Needs TriagePublic

Description

This task holds the work involved with:

  1. Defining the KPI teams contributing to WE 1.7 will use to prioritize work and evaluate the impact of that work
  2. Defining the percentage by which teams contributing to WE 1.7 will seek to move the KPI we end up converging on
    1. Establishing the baseline of the KPI we end up converging on to help inform how much we will attempt to grow that number during Q3 + Q4 (FY 25 - 26)

Decision(s) to be made

  • 1. What KPI will teams use to evaluate the impact of the work they are doing during Q3 and Q4 of the 2025 - 2026 fiscal year ?
    • See above.
  • 2. By what percentage will the WE 1.7 KR attempt to grow KPI (see below) during Q3 and Q4 of the 2025 - 2026 fiscal year?
    • As part of the above, provide by the current absolute count of retained editors who spend at least 2 seconds in the mobile visual editor and return within 2 weeks.

Proposed process

StepDescriptionResponsibleStatusNotes
1.Converge on KPI@ppelberg✅ Done
2.Establish KPI baselineI@MNeislerSee T389404 for reference.
3.Form point of view on what a meaningful improvement in KPI would looke like@ppelbergThis perspective will compliment the more inductive approach "2." represents
4.Converge on KPI improvement target@ppelbergSee T389403 for reference.

KPI

Achieve a minimum #% relative increase in 2-week retention among Junior Editors who spend at least 2 seconds in the mobile visual editor, based on controlled A/B test(s) across target wikis.[i][ii]

i. "Retention" = people who publish ≥1 edit (across namespaces) within 2 weeks of an edit session in which they spent at least ≥2 seconds in VE's ready state.
ii. "Junior Editors" = editors who have published <100 cumulative edits on any wiki.

Done

  • KPI is defined
  • Baseline is established
  • KPI improvement target is set

References

Event Timeline

ppelberg updated the task description. (Show Details)