This tasks holds the work of running a controlled experiment to evaluate the impact of presenting new(er) (≤100 cumulative edits) editors and people who are logged out
Deployment timing
| Target completion date | Milestone | Ticket | Responsible | Status | Notes |
|---|---|---|---|---|---|
| T420667 | @Quiddity | ✅Done | |||
| Monday, 20 April | Ensure first suggestion discoverability | T414518 | @EAkinloose + @Ryasmeen | ❗QA Needed❗ | |
| T419447 | @medelius | ✅ Done | |||
| T422031 | @Esanders | ✅ Done | |||
| T422032 | @Esanders | ✅ Done | |||
| Wednesday, 22 April | T422740 | @medelius | ✅ Done | ||
| T417922 | @ppelberg | ✅ Done | Per 20 April offline discussion, we will ENABLE Tone suggestions for the controlled experiment and revisit this decision prior to a potential default-on deployment (T414853) | ||
| Wednesday, 22 April | Finalize UX for indicating additional suggestions outside current section | T422979 | @bmartinezcalvo | ✅ Done | |
| Friday, 24 April | Implement and QA bucketing requirements | T421189 | Editing Engineering + QA | ✅ Done | |
| Friday, 24 April | Define and implement missing metrics | T422736 | @MNeisler | ⏳ In progress | |
| Monday, 27 April | Start experiment | T421189 | Editing Engineering | ✅ Done | |
| Thursday, 30 April | Publish basic config json pages: ko.wiki, zh.wiki | no ticket | ✅ Done | ||
| Wednesday, 15 July | End experiment | no ticket; this will happen automatically | |||
| Friday, 24 July | Publish experiment findings on-wiki | T430878 | @ppelberg | ||
Hypothesis
If we present junior contributors who enter the mobile VisualEditor with immediately actionable edit suggestions, then the proportion of edit sessions that result in someone publishing a constructive edit will increase by ≥10%.
Decision to be made
- What – if any – adjustments to the Edit Suggestions UX need to be made before we can be confident...?
- Newcomers and Junior Contributors that encounter Edit Suggestions are more likely to publish a constructive edit
- Newcomers and Junior Contributors will intuitively interact with the Edit Suggestion experience in ways that are NOT disruptive to them or the wikis.
Metrics
The main outcomes we are trying to impact through this feature. These are what we are primarily using for evaluating the hypothesis and deciding whether to deploy an intervention more widely.
| ID | Hypothesis | Metric |
|---|---|---|
| KPI | Newcomers who opened the editor out of curiosity will be compelled to publish edits they might not have made otherwise because they will be provided with edit suggestions that are clear and compelling. | Edit completion rate: Proportion of qualified newcomer and Junior Contributor edit sessions [1] on a Wikipedia main namespace that are published, based on controlled A/B test(s). |
| Secondary metric | Newcomers and Junior Contributors will be more likely to return to publish an edit in the future that is not reverted because Edit Suggestions reduced the effort required to discover and publish a constructive edit. | Second Week Retention Rate: Proportion of newcomers and Junior Contributors who return to 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. |
| Secondary | Newcomers and Junior Contributors will be likely to engage with Edit Suggestions because they will be 1) actionable, 2) straightforward, 3) draw on knowledge they already possess, and 4) related to a topic (broadly defined) they've explicitly expressed an interest in improving | Suggestion Acceptance Rate (Treatment Only metric): Proportion of contributors who see at least 1 Edit Suggestion and click to accept at least 1 suggestion during their session. [2] |
| Secondary | Brand new editors will be more likely to complete at least one constructive edit within 24 hours of creating an account because they will be presented with suggestions for smaller changes they are more equipped to make | Constructive Activation Rate: Proportion of newcomers making their first edit to an article in the main namespace within 24 hours of registration, and that edit not being reverted within 48 hours of being published. |
| Guardrail | Newcomer and Junior Contributors will engage more quickly because they will be provided with relevant and actionable suggestions that help reduce confusion in how to get started. | Time until first change: Time between the editor loaded (action = ready) and a user starting to type (action = firstChange |
| Guardrail | There will be no meaningful decreases in constructive edits because newcomers will be provided structured edit suggestions they intuitively understand and are aligned with local Wikipedia policies and guidelines | Constructive edit rate: Proportion of published edits by users with ≤100 cumulative edits that are constructive. [3] |
- Qualified edit session = edit session in which the user spent at least ≥2 seconds in VE's ready state
- Overall and by suggestion_type
- "Constructive edits" = edits to pages in any Wikipedia main namespace that are not reverted within 48 hours of being published
Experiment Decision Matrix
| ID | Scenario | Indicator(s) | Plan of Action | |||
|---|---|---|---|---|---|---|
| 1. | Suggestion Mode is disrupting, discouraging, or otherwise getting in the way of new(er) volunteers publishing constructive edits | ≥20% decrease in any of the the following metrics in edit sessions where ≥1 Suggestion is available: edit completion rate, editor load time, edit abandonment rate, revert rate | Pause scaling plans; investigate changes to the UX. | |||
| 2. | Suggestion Mode is increasing the likelihood that new(er) volunteers will publish destructive edits | Increase in the proportion of edits published in editing sessions where ≥1 suggestions were available and are reverted within 48 hours | Pause scaling plans, Review edits to try to identify any patterns in abuse and propose changes to UX to mitigate them. | |||
| 3. | Suggestion Mode is effective at increasing the rate at which people publish (read: complete) edits and the edits people publish are reverted at higher rates | Increases in both 1) the proportion of all editing sessions by logged-in users with ≤100 cumulative edits that are started on mobile web in the Wikipedia main namespace (user clicks that the edit button (action = ‘init’) that are saved (action = ‘saveSuccess’) and 2) the proportion of published edits that are reverted within 48 hours. | Pause scaling plans; analysis and manual review of reverted edits to understand why those edits are being reverted. | |||
| 4. | Suggestion Mode does not show a statistically significant impact on any KPI, secondary, or guardrail metric | See metrics above | Move forward with scaling plans | |||
| 5. | Suggestion Mode is effective at increasing the edit completion rate of qualified newcomer and Junior Contributor mobile edit sessions | See metrics above | Move forward with scaling plans[1] | |||
- Qualified edit session = edit session in which a logged-in user with ≤100 cumulative edits spent at least ≥2 seconds in VE's "ready" state.