This task involves the work of creating a dashboard of a set of VE-related metrics so that we can monitor its overall performance/efficiency on an ongoing basis.

This dashboard would be a compliment to the existing VisualEditor load / save Grafana dashboard.

Story

• As a member of the Editing Team responsible for ensuring the visual editor supports people in publishing edits i) they are motivated to make and ii) projects value, I need to be able to see and explore a range of metrics that, taken together, help me understand the extent to which VE editing experiences are "healthy" so that I can decide what – if any – action to prioritize taking if/when we perceive it not to be.
• As a member of a team seeking to improve VE, I need to be able to evaluate the extent to which the intervention we are working on causes any notable shifts in VE's global health metrics so that we (the team I'm representing and the Editing Team) can determine what – if anything – about the intervention needs to be revised/reconsidered before we scale it further.
  • E.g. WMDE and Sub-References | TICKET

Requirements

To be draft in collaboration with @MNeisler.

Metrics for consideration

The metrics below are ideas. The metrics we ended up prioritizing will be documented in the === Requirements section above.

• Edit completion rate
• Edit abandonment rate
• Time to save
• Revert rate
• Block rate
• Published edits

The above filtered by:

• Platform
• Experience level
• Interface (e.g. DiscussionTools, 2017 WTE, VE)
• Project

Background

Edit Check is evolving to a place where people are likely to encounter multiple Edit Checks within a single edit session.

Ideally, the people encountering Edit Checks find them supportive to the extent that they are motived to act on them and publish the change(s) they arrived to [edit ] intending to make.

With the above said, it's important to acknowledge that presenting Edit Checks to people means "asking" them to take actions they might not have otherwise taken. By extension, Edit Check could potentially cause people acting in good faith to perceive editing Wikipedia to be more involved than they expected and abandon the edit(s) they started.

Beyond Edit Check, the number of teams evolving parts of the visual editing experience is growing (think: WMDE, CommunityTech, Growth). And while teams developing these interventions are likely to evaluate the impact of each in relative isolation, it's important the Editing Team be equipped with a "birds eye view" of VE's overall "health," for both the people using it and the projects where it is available.

With this task, we want to create a dashboard that will enable members of the Editing Team to monitor – historically and in real-time – several metrics that will enable us to understand how Edit Check is impacting how people do and do not edit in VE.

• Thank you, @Sj for suggesting this.