Hypothesis: If we produce designs for improvements to the onboarding and legibility of diffs, which connect reviewing a change to clear next steps, the Moderator Tools team will have a clear understanding of what to implement.
This is a Q1 design hypothesis, intended to queue up implementable work for Q2. It is relatively open-ended, and we may take this in a number of different directions based on what we learn and what feels achievable in a short time frame.
The goal of the Review Changes module in the Personal Dashboard is to engage newer editors in the practice of staying up to date with the edits that have been made to the pages they are interested in. We hypothesize that this feature can drive retention among newer editors. To make the feature as engaging as possible, we need to ensure that the full journey a user goes through with it is clear, actionable, and provides an obvious next step. So far, our efforts have focused on the entrypoint - assembling the right edits for a given user, and providing them with reasons to click on an edit. Once they land on a diff, however, they:
- May find the interface confusing
- May not be able to find the action that they want to take (e.g. Thanks, Undo)
- Are not provided with a clear way to either navigate back to the list of Review Changes edits, or to navigate to the next edit in their feed.
We would like to make changes here so that there is a clear ‘loop’ from first seeing the Review Changes module, through reviewing a given edit, reviewing more edits, and either returning to the Dashboard or moving on to other activities. We don’t want looking at a Diff to be a dead end that results in the user closing the page.
The scope of our changes could be for all users, whenever they view a diff, or they could be limited to changes which only display for users engaging with their Review Changes feed. Additionally, we may decide to limit our efforts to either the desktop or mobile experiences.
