This is one of three project announcements for Improving Review Queues. We’ve summarized the project objectives and goals here.
As a reminder, this project is still in the early stages of discovery. In this post, we are sharing proposed changes to the Onboarding and Updated Workflows/Paths. We are asking for your feedback before we begin implementation. After we collect community feedback, we will be open to including changes into the next design iteration.
Information and guidance about how to use the Review Queues is available, but it’s in several places. We are proposing different ways to include upfront instruction and guidance to better equip reviewers to use their newly earned privilege. We are continuing to make refinements to the language and copy in these messages as part of the discovery process.
Users will find an onboarding message on the homepage with general information about using the Review Queues. As they enter each new queue, they will be presented with a modal with unique instructions on how to best contribute to that queue.
- What did you wish was part of your Review Queue onboarding?
- What feature/aspect was difficult to discover as a new reviewer?
- What do you consider essential “day one” information for new reviewers?
Updated workflows and paths
We would like to update each queue with a new Actions menu that exposes all instructions and adds a bit of pause so that users can make more considered decisions. We will also be adding the new follow feature (available in the "…" button) so that reviewers can keep track of posts.
Reviewers will no longer have to open questions in a new browser tab to get more context. In addition to the post being reviewed, each review task will have the question, comments, and other answers on the review page to give context. We are also sharing a subtly different design in our user research sessions.
All changes will be supported by a Stacks update to the visual design along with responsive, mobile views.
Stack Overflow-specific changes:
We want to take a closer look at the success and failures of the First Post, Late Answers, Triage, and Help & Improvement queues.
In Triage, the Requires Editing action is sending a surplus of poor, unsalvageable posts to bloat the Help and Improvement queue. We want to remove the Requires editing action and replace it with two new actions. Selecting Improve readability will send the post to Help & Improvement. Posts that can only be salvaged by the original poster (Add clarity) will be sent to the Close vote queue.
If a reviewer selects Very low quality in the Help & Improvement queue, the post will be sent to the Low Quality Post queue. By doing this, we hope to cease the endless cycle making these queues unsuccessful in helping moderation.
Finally, we are considering closing the First Posts and Late Answers queues and combining those tasks into Triage. These queues were intended to give good posts a head start toward success and filter out bad posts, but tasks could see better, faster intervention.
- Does it feel like any important actions or functions are missing from the review page?
Does having the original post, comments, and additional answers all on the page make it easier to do a review?
Stack Overflow only:
- In Triage, do you anticipate any issues with sending Add clarity posts to the Close Votes queue?
- In Help & Improvement, do you anticipate any issues with sending Very low quality posts to the Low Quality Posts queue?
- Do you anticipate any issues with removing the First Posts and Late Answers queues?
We share improvements to the review bans and new features in this final post: Improving Review Queues - Design overview II.