Implement a experiment that splits eligible editors into a 50 percent Control and 50 percent Treatment on pilot wikis.
- Control receives the current Suggested Edits experience (Status quo Easy task set and ordering as currently configured per wiki.)
- Treatment receives “Add a Link” and “Revise Tone” as the Easy tasks shown in Suggested Edits.
Details
- Use the GEImproveToneSuggestedEditEnabled feature flag (T401192) to implement a 50/50 split, assigning half of participants to the Control experience and half to the Treatment experience.
- Which Pilot wikis will be included in this A/B test?
- TBD: We will need to limit to some or all of the wikis where Tone Check has been tested.
- Are we testing on Mobile or Desktop?
- TBD: Ideally both, but only mobile metrics will be part of the final WE1.1 measurement for success, so the Mobile UX and release should be prioritized.
- Will be set up this experiment via the Experimentation Lab?
- We should instrument and set up this experiment using the Experimentation Lab, unless there are major blockers the will significantly delay or derail experiment findings.
- How will experiment enrollment work?
- This should be answered as part of: T397247: Measurement Plan: Revise Tone Structured Task (WE1.1, FY25-26)
Acceptance Criteria:
- Add experiment bucketing and assignment
- bucketing is needed on the Homepage for who has access to Revise Tone
- in Leveling Up, Revise Tone should never be suggested, regardless of buckets
- Allow for QA testing time
- Agree on Release Date with Product and Movement Communications.
- Release date TBD
Note:
- bucketing is not available the usual way in api-endpoints
- ideally bucketing in api-endpoints should be avoided, otherwise additional parameters may need to be used
- see https://wikimedia.slack.com/archives/C01DFMX6QLB/p1761738219771889 for more detail