Change Details

###Summary We would like to gather user testing feedback from Admins and Stewards about the design for a clickable component to display public data related to user account information to functionaries, so that we can ensure the component contains the most relevant information. ###Research questions - What information is most crucial to highlight and why (e.g blocks, reverted edits)? - What information is least important and why? - What order should the information be in? - What information should be displayed in the contextual menu? - What icon would you expect to click on in order to launch an account reputation card? ###Participants Aimed at users with extended rights who are regularly involved in anti-abuse mitigations: - Stewards - Admins ###Testing plan Post designs with a link to a short survey in Admin areas on a number of wikis, and share with Stewards on relevant channels. [[ https://docs.google.com/document/d/1ZolGcCnVSKB9QmBEhSFe_s0Kry75_ub0mHGRLw0Br44/edit?usp=sharing | Draft survey doc ]] ###Acceptance criteria [X] Create short survey on Qualtrics [X] Share with admins on Discord channel [X] Close survey and cleanup data [ ] Analyse survey results (in progress)

##Background We would like to share a survey to gather feedback from Admins and Stewards about the design for a clickable component to display public data related to user account information to functionaries, so that we can ensure the component contains the most relevant information. **Survey goals** - Identify the most important information to display on the card. - Understand expected usefulness of the card. - Uncover ideas for improving the account reputation card. ##Recommendations <table> <tr> <th>Now</th> <th>Later</th> </tr> <tr> <td> Re-name “Account Reputation” to “User Info” Include thanks received and thanks given Include edit count for editing activity graph Label actions more clearly (e.g. “Block user”) Add link to Global Account Information Indicate recently reverted edits (last 24 hours) Include CheckUser information/links </td> <td> Integration of menu button options with third-party tools (e.g. Twinkle) Explore other ways to visually present editing activity over 60 days </td> </tr> </table> ##Results ####Demographics - 11 responses from 8 administrators, 2 patrollers (with no admin rights), and 1 user who has never performed anti-abuse work on Wikipedia - Two thirds of respondents are experienced users, having been active on wikis for 3 years or more. - Desktop view preferred by all respondents ####Usefulness & information hierarchy > “This is a really neat concept, thank you for working on it.” - Overall the card is considered very useful - According to the ranking question: username is most important, followed by thanks received, groups, active wikis and editing activity over the last 60 days. - The least important information is: new article creation, local reverted edits, local edits and global edits. - This finding slightly contradicts the previous feedback from Stewards who said that the number of global edits was the most important information. From this we can infer that the information hierarchy will vary depending on each user and their role on the wikis. ####Improvements to make now > “If you show it to all logged-in users, don't call it reputation card (just info card)” > "As a checkuser, I am frequently interested in knowing whether an abusive account has previously been subject to a CU investigation." - Card needs re-naming so there is no mention of reputation - Include missing data points: Link to Global account information, recently reverted edits (last 24 hours) - CheckUsers would like to see CU information: number of past Checkuser investigations, links to Special:Checkuser, Special:Investigate and Special:CheckUserlog - Include thanks received and thanks given and label them clearly - Label actions more clearly: "Block user" and "Add user page to watchlist" - Include edit count on editing activity graph for additional context - Make the card available to all logged-in users: half of respondents think the card should be available to all logged-in users ####Ideas to explore later > If at all possible, please ensure that integration with Twinkle (and other third-party tools) is facilitated as much as possible (for example by ensuring that the Hamburger menu can easily be extended, for example with the Twinkle Block, warning, or reporting menus) - Integration of menu button options with third-party tools (e.g. Twinkle) - Explore other ways to visually present editing activity over 60 days (e.g a numerical count of recent edits) ##Acceptance criteria [X] Create short survey on Qualtrics [X] Share with admins on Discord channel [X] Close survey and cleanup data [X] Analyse survey results

###Summary##Background We would like to gather user testingshare a survey to gather feedback from Admins and Stewards about the design for a clickable component to display public data related to user account information to functionaries, so that we can ensure the component contains the most relevant information. ###Research questions**Survey goals** - Identify the most important information to display on the card. - Understand expected usefulness of the card. - Uncover ideas for improving the account reputation card. ##Recommendations <table> <tr> - What information is most crucial to highlight and why (e.g blocks, reverted edits)?<th>Now</th> - What information is least important and why?<th>Later</th> </tr> <tr> - What order should the information be in?<td> Re-name “Account Reputation” to “User Info” Include thanks received and thanks given Include edit count for editing activity graph Label actions more clearly (e.g. “Block user”) Add link to Global Account Information Indicate recently reverted edits (last 24 hours) Include CheckUser information/links </td> - What information should be displayed in the contextual menu?<td> Integration of menu button options with third-party tools (e.g. Twinkle) Explore other ways to visually present editing activity over 60 days - What icon would you expect to click on in order to launch an account reputation card?</td> </tr> </table> ##Results ####Demographics - 11 responses from 8 administrators, 2 patrollers (with no admin rights), and 1 user who has never performed anti-abuse work on Wikipedia - Two thirds of respondents are experienced users, having been active on wikis for 3 years or more. - Desktop view preferred by all respondents ####Usefulness & information hierarchy > “This is a really neat concept, thank you for working on it.” - Overall the card is considered very useful - According to the ranking question: username is most important, followed by thanks received, groups, active wikis and editing activity over the last 60 days. - The least important information is: new article creation, local reverted edits, local edits and global edits. - This finding slightly contradicts the previous feedback from Stewards who said that the number of global edits was the most important information. From this we can infer that the information hierarchy will vary depending on each user and their role on the wikis. ####Improvements to make now > “If you show it to all logged-in users, don't call it reputation card (just info card)” ###Participants> "As a checkuser, I am frequently interested in knowing whether an abusive account has previously been subject to a CU investigation." - Card needs re-naming so there is no mention of reputation - Include missing data points: Link to Global account information, recently reverted edits (last 24 hours) - CheckUsers would like to see CU information: number of past Checkuser investigations, links to Special:Checkuser, Special:Investigate and Special:CheckUserlog Aimed at users with extended rights who are regularly involved i- Include thanks received and thanks given anti-abuse mitigations:d label them clearly - Stewards- Label actions more clearly: "Block user" and "Add user page to watchlist" - AdminInclude edit count on editing activity graph for additional context - Make the card available to all logged-in users: half of respondents think the card should be available to all logged-in users ###Testing plan####Ideas to explore later Post designs with a link to a short survey in Admin areas on a number of wikis> If at all possible, please ensure that integration with Twinkle (and other third-party tools) is facilitated as much as possible (for example by ensuring that the Hamburger menu can easily be extended, for example with the Twinkle Block, warning, and share with Stewards on relevant channels.or reporting menus) [[ https://docs.google.com/document/d/1ZolGcCnVSKB9QmBEhSFe_s0Kry75_ub0mHGRLw0Br44/edit?usp=sharing | Draft survey doc ]]- Integration of menu button options with third-party tools (e.g. Twinkle) - Explore other ways to visually present editing activity over 60 days (e.g a numerical count of recent edits) ###Acceptance criteria [X] Create short survey on Qualtrics [X] Share with admins on Discord channel [X] Close survey and cleanup data [ X] Analyse survey results (in progress)s