In T423923, we will begin collecting responses from v1 of the "Exit the editor" survey. And in T424102, we will stop collecting responses.

This task involves the work of analyzing these survey responses with the goal of helping the Editing Team, and others contributing to WE 1.7 (FY25-26), decide: What (if any) improvements will the Editing Team prioritize work on as part of WE1.7 to increase the proportion of people who curiously tap Edit on mobile and go on to publish a constructive change?

Requirements

Analysis population

While T422931 presented the survey to people regardless of how much time elapsed between the editing interface being ready and them seeking to abort, this analysis will be limited to people who spend ≥2 seconds in the editing interface after it reaches the ready state.

• Wikis: en.wiki
  • Start with en.wiki to avoid using time on translations during the initial test
• Platform(s): Mobile web
• Max edit count: ≤100 cumulative edits
• Editing interface(s): mobile VE & mobile source
• Account state: logged in and logged out

Population groupings

We'd like to be able to group and intersect respondents by the following...

• Editing interface people used: VE, source, switched to source, switched to VE
• Account state: logged in/out
• Changes made before abandoning: yes/no
• Edit count before the abandoned edit session the survey was presented at the conclusion of

Open question(s)

• 1. What level of effort would be required to make this data available in a tool like Superset that would, ideally, enable us to freely explore the data without needing to define cohorts / population groupings upfront?

Done

• An artifact (e.g. report) is published that enables the team to review survey responses defined in the Requirements section above