Jump to content

Wikipedia:Community health initiative on English Wikipedia/Research about Administrators' Noticeboard Incidents

From Wikipedia, the free encyclopedia

Introduction

[edit]

In 2017, Wikimedia Foundation Support and Safety team (SuSa) and the Anti-Harassment Tools team surveyed English-language Wikipedia contributors about their perception of Administrators' noticeboard/Incidents (AN/I), a noticeboard that is a key part of the conflict resolution process on the English Wikipedia. This survey is intended to understand community sentiments around AN/I, and will not lead to immediate or imposed changes to AN/I from the Foundation. Rather the purpose of the survey is to fill in gaps in data that could lead to on wiki discussions about possible improvements to how AN/I cases are managed. Any changes would need to be backed by the volunteer community on the English Wikipedia.

Methodology

[edit]

The Wikimedia Foundation Support and Safety team and the Anti-Harassment Tools team recruited English Wikipedia contributors to participate in a survey about AN/I in order to identify possible areas of improvement for handling cases by learning about user experiences and satisfactions levels.

Invitations to take the survey were made on English Wikipedia noticeboards and invitations were placed on the user talk pages of 400 randomly selected active editors with recent edits to AN/I (defined as taking place within the previous 12 months, October 2016–October 2017). To involve the participation of a more diverse group of contributors, invitations to take the survey were sent to mailing lists of Wikimedia affiliates and some other known organized groups of English Wikipedia editors. The survey opened on November 28, 2017, and closed on December 8, 2017, at 23:00 UTC.

The survey asked the participants to complete 23 questions and included six with write-in answers. Answers from the six write-in questions were sorted and grouped, and then labeled to organize the feedback into cohesive ideas. Some answers received multiple labels as they provided multiple kinds of insight. The survey was broken into three parts:

  • use of AN/I;
  • satisfaction with AN/I; and
  • experiences with AN/I.

The goal was to gauge what AN/I does well, what it doesn't do well, and what needs to be improved.

A total of 136 people filled out the survey. It is important to note that the following statistical analysis draws upon a survey with a small sample size of self selected experienced editors. As the survey was a voluntary opt-in survey, the sample of people who opted to respond to it might not be representative of the general Wikimedia user base. Furthermore, the findings presented in this report are based on the respondents' own assessment and understanding of their direct or secondhand experience with AN/I and, as such, they are limited in capturing the experiences only as perceived by the respondents. Other methods need to be explored in order to validate the information. We have gathered more information on the AN/I process in our quantitative data analysis; this data supplements the results of the survey from a more metrics-based perspective.

Demographics of participants

[edit]
How long have you been a Wikimedia contributor?

0% did not select an option [?]


1 – Less than 1 year (2.21%)
2 – 1 to 2 years (6.62%)
3 – 2 to 5 years (17.65%)
4 – More than 5 years (73.53%)
Three-quarters of survey participants reported being a contributor for more than five years.

Which gender do you identify with?

0% did not select an option [?]


1 – Male (79.41%)
2 – Female (11.76%)
3 – Non-binary / third gender (0.74%)
4 – Prefer not to say (8.09%)
Almost 80% of participants identify as male.

Which region do you usually edit from?

0% did not select an option [?]


1 – North America (62.50%)
2 – Western Europe (22.79%)
3 – Oceania (6.62%)
4 – Asia (4.41%)
5 – Sub-Saharan Africa (2.94%)
6 – Other (0.74%)
More than 85% of participants are from North America or Western Europe.

Participation on AN/I

[edit]
How often have you reported incidents to AN/I in the last 12 months?

0% did not select an option [?]


1 – Never (32.35%)
2 – Once or twice (46.32%)
3 – Between 3 and 10 times (18.38%)
4 – More than 10 times (2.94%)
Almost one-third of survey participants had not reported an incident to AN/I in the past year.


How often have you been an uninvolved participant in discussions on AN/I in the last 12 months?

0.74% did not select an option [?]


1 – Never (22.96%)
2 – Once or twice (25.93%)
3 – Between 3 and 10 times (28.89%)
4 – More than 10 times (22.22%)
More than three-quarters of participants had been an uninvolved participant at AN/I in the past year.

How often have you been involved in an incident reported on AN/I in the last 12 months?

0% did not select an option [?]


1 – Never (27.94%)
2 – Once or twice (46.32%)
3 – Between 3 and 10 times (20.59%)
4 – More than 10 times (5.15%)
Almost three-quarters of survey participants reported being involved in an incident reported on AN/I in the last 12 months.

Key Findings

[edit]

Theme 1: Satisfaction/dissatisfaction with AN/I

[edit]

There are mixed opinions among respondents about how well the general process works to resolve AN/I cases. There is a stronger dissatisfaction expressed about the way that AN/I cases are handled rather than a negative view of the AN/I type process.


On a scale of 1–5, how satisfied are you with the way reports are handled on AN/I?

1.47% did not select an option [?]


1 – Dissatisfied (24.63%)
2 – (19.40%)
3 – (29.10%)
4 – (21.64%)
5 – Very satisfied (5.22%)
Only 27% of respondents indicated they were satisfied with the way that AN/I cases are handled.

Have you avoided reporting one or more incidents to AN/I in the last 12 months, because you did not think it would be handled appropriately there?

2.21% did not select an option [?]


1 – No (40.30%)
2 – Yes, one or two times (26.87%)
3 – Yes, between three and ten times (17.16%)
4 – Yes, more than ten times (8.96%)
5 – Other (free text) (6.72%)
52.99% have specifically avoided making a report on ANI because they were afraid it would not be handled appropriately.
> If you did not select "no" above, why did you think those incidents would not be handled appropriately?
participants (n) = 62
response buckets[a] = 83

74 participants (54.41%) did not enter a response for this question

1 – Avoiding drama (8.06%)
2 – Complex issues (12.90%)
3 – Toxicity (12.90%)
4 – Civility issues / threats (6.45%)
5 – Biased participants (9.68%)
6 – Defensive cliques (19.35%)
7 – Admin confidence (3.23%)
8 – Certain users protected (4.84%)
9 – Boomerang effect (12.90%)
10 – Easier to ignore the problem (8.06%)
11 – Ineffective / inconsistent (8.06%)
12 – No chance of action (8.06%)
13 – Bad past experience (6.45%)
14 – Too difficult / too much scrutiny (3.23%)
15 – Better options (6.45%)
16 – Other / meta (3.23%)

One user wrote, "There is the boomerang factor. Who knows what I have in my history that people will comb through, so I put up with harassment or bullying or vandalism because the general rule is that boomerangs are allowed since there is no scope rule with ANI reports".

Another user mentioned bias specifically, "It depends on who shows up; bias comes into play, e.g. people take sides based on whether they personally agree with the actions of people, not if people's actions follow policies and guidelines".



Have you ever disagreed with an AN/I outcome, such as the wrong person being sanctioned?

1.47% did not select an option [?]


1 – Never (6.62%)
2 – Rarely (29.41%)
3 – Sometimes (46.32%)
4 – Frequently (16.18%)
More than six in ten participants reported "sometimes" or "frequently" disagreeing with the outcomes of cases at AN/I.

On a scale of 1–5, do you agree with the general process of how AN/I reports work? (e.g report, discussion, and then decision?)

2.21% did not select an option [?]


1 – Strongly disagree (9.02%)
2 – (20.30%)
3 – (19.55%)
4 – (38.35%)
5 – Strongly agree (12.78%)
More than 50% of users agree or strongly agree with the general process of how AN/I reports work.

Theme 2: The type of case matters

[edit]
For which types of problems does AN/I work well?
participants (n) = 98
response buckets[a] = 166

38 participants (27.94%) did not enter a response for this question

1 – Urgent (7.14%)
2 – Straightforward (44.9%)
3 – Short term problems (3.06%)
4 – Many eyes on problem (2.04%)
5 – Limited discussion (8.16%)
6 – Single problem editors (5.10%)
7 – No need for kindness (1.02%)
8 – Tech problems (6.12%)
9 – Bot problems (2.04%)
10 – Sockpuppetry (16.33%)
11 – Copyright violations (7.14%)
12 – Legal threats (4.08%)
13 – SPA, POV (5.10%)
14 – Rules other (2.04%)
15 – Misuse of admin tools (2.04%)
16 – Personal attacks (8.16%)
17 – User issues (7.14%)
18 – New editors problems (6.12%)
19 – Serious vandalism (19.39%)
20 – "Nothing" (4.08%)
21 – "Everything" (3.06%)
22 – Other (5.10%)

When asked "for which type of problems does AN/I work well," there were 98 write in responses. Responses were focused on specific kinds of problems, which we sorted into four major groups: the complexity of the problems, technical issues, rules, or problems involving editor conduct.

AN/I seems to work best for more 'obvious' or less complex problems like sock puppetry, "short term" problems (problems that can quickly or easily be resolved), copyright violations, and 'bot or automated script' problems. This seems to be reflected in the write-in answers, as well.

One user wrote, "AN/I works great for clear-cut rule violations, bot problems, etc. It does black-and-white very well."

Another described the issues AN/I handles well as "housekeeping and basic admin stuff, like IP vandalism/sockpuppetry, blatant trolling, etc."

Generally, the descriptions and suggestions were that AN/I handled cases best that were "objective and obvious cases" and "clear cut ones." Specifically, vandalism, bots, and sockpuppeting were mentioned frequently. In their responses, survey participants did not always include specific problems that AN/I is able to handle well; rather, they spoke about more general concepts. For example, lots of feedback mentioned 'straightforward cases' without specifying what makes a case straightforward.

Examples of answers that were labeled as 'straightforward cases': A user wrote in,"obvious instances of people breaking policies and guidelines."

A user wrote in, "relatively simple issues that just need one admin or don't really involve disputes; disputes where one editor is clearly the disruptive one and can be sanctioned."


For which types of problems does AN/I NOT work well?
participants (n) = 99
response buckets[a] = 186

37 participants (27.21%) did not enter a response for this question

1 – Conflicts with long history (21.21%)
2 – Complex conflicts (24.24%)
3 – Content conflicts (17.17%)
4 – Certain topics (4.04%)
5 – Unclear issues (11.11%)
6 – Conflicts better suited elsewhere (7.07%)
7 – Conflicts that attract attention (3.03%)
8 – Bot problems (2.02%)
9 – Admin conduct (4.04%)
10 – Bad faith reports/"gaming the system" (5.05%)
11 – Conflicts between factions (cabals) (13.13%)
12 – Conflicts with a certain type of editor (25.25%)
13 – Interpersonal disputes (21.21%)
14 – Threats (1.01%)
15 – Civility violations (18.18%)
16 – Reports from minorities, minority editors involved (3.03%)
17 – (Almost) all problems (7.07%)

This question had 99 write-in responses. Some of the responses have been grouped into multiple buckets since the answers fit multiple kinds of labels. The more complex, nuanced, complicated, or personal the issues, the more participants seemed to stress AN/I is not the right space to handle those problems. A complex problem may be something where the rules are ambiguous or contradictory, making solving a problem difficult, whereas a complicated problem could be a long running dispute between editors. Examples of these problems were described as cases that involved issues such as controversial topics, or issues involving civility problems and personal threats.

One user wrote in, "What AN/I doesn't do well is grey areas, long-term abuse, and taking action against "competence is required" editors whose problems are less clear cut."

Another user highlights this 'grey area' problem by saying, "Ambiguous issues, issues where the topic is ideologically divisive, or where one of the users is new and the other one is a 'old hat' with plenty of friends (rarely is the discussion unbiased in these cases)."

The more ambiguous and/or more investigative work required, the harder it is to solve. Longer term problems that require more back and forth were viewed by admins as harder to solve, and something that AN/I didn't solve well. One user suggests that longer term problems would be better solved on another board or space such as "AN or ArbCom."

A user wrote in, "Anything where looking at large amounts of evidence is needed, where the outcome isn't obvious or where one or more editors are long-term so have supporters and opposers."

Another user wrote, "Complex interpersonal disputes, content disputes that have been ongoing for long enough or involve enough editors to have turned into conduct problems, complaints related to "incivility", any complaint whose specific circumstances touch on broader wiki-political issues and which therefore encourages a lot of soapboxing and off-topic personal commentary from observers."

Ideas for improvements to AN/I

[edit]
If you could change one thing about AN/I, what would it be?
participants (n) = 110
response buckets[a] = 134

26 participants (19.12%) did not enter a response for this question

1 – Clerking and moderators (21.82%)
2 – Closing cases (4.55%)
3 – Boomerang (2.73%)
4 – Misc rules (0.91%)
5 – Fairness / Merit-based process (10%)
6 – Punish bogus reports (3.64%)
7 – Referring people to different processes (5.45%)
8 – Misc. policy suggestions (2.73%)
9 – Punish incivility (8.18%)
10 – Environment (5.45%)
11 – More civility in general (1.82%)
12 – Other technical solution (3.64%)
13 – Structured forms (5.45%)
14 – Subpages and length (4.55%)
15 – More structure in general (9.09%)
16 – Private reporting (1.82%)
17 – Generate data / metrics (0.91%)
18 – Misc reporting (2.73%)
19 – Separate or ban uninvolved editors / non-admins (10.91%)
20 – Punish derailers (5.45%)
21 – No change (2.73%)
22 – Get rid of it (3.64%)
23 – Not sure (2.73%)
24 – Unsorted (0.91%)
What are some other changes you would like to see in the AN/I reporting process?
participants (n) = 74
response buckets[a] = 103

62 participants (45.59%) did not enter a response for this question

1 – Clerking and moderators (14.86%)
2 – Closer adherence to policy (6.76%)
3 – Boomerang (5.41%)
4 – General rules (2.7%)
5 – Sanctions against abusers (5.41%)
6 – Fairness / Merit-based process (6.76%)
7 – Punish bogus reports (4.05%)
8 – Referring people to different processes (2.7%)
9 – Training (4.05%)
10 – Misc. policy suggestions (4.05%)
11 – Environment (6.76%)
12 – More civility in general (6.76%)
13 – Grouping related (4.05%)
14 – Other technical solution (2.7%)
15 – Misc filters / limits (4.05%)
16 – Structured forms (4.05%)
17 – Time limit / subpages (8.11%)
18 – More structure in general (10.81%)
19 – Generate data / metrics (2.7%)
20 – General reporting (10.81%)
21 – Separate or ban uninvolved editors / non-admins (14.86%)
22 – Negative feedback (2.7%)
23 – Unsorted (4.05%)

Theme 3: More moderators/clerks for AN/I discussions

[edit]

A reoccurring theme in the free text comments was for there to be more moderators or clerks to enforce the rules. One person said, "discussions need to be clerked to keep them from raising more problems than they solve." Another user said, "clerking is needed to keep discussions focused."

How often, in general, would you say the following statements apply to discussion on AN/I? — Discussion is focused and neutral.

2.94% did not select an option [?]


1 – Almost never (18.94%)
2 – Rarely (29.55%)
3 – Sometimes (33.33%)
4 – Often (15.91%)
5 – Almost always (2.27%)
Almost half of respondents said that discussions on AN/I are "almost never" or "rarely" focused and neutral. .

Other responses indicate a general need for more administrators to monitor AN/I. A user suggested for there to be "more of the admin corpus active on any given day. It's the same old faces time after time."

One survey participant said that "too often I've seen meticulously documented reports being dismissed as TL;DR or just not acted upon because apparently no one wants to take the time to read the diffs and make a judgment call. AN/I also has its regulars who seem to delight in the drama (and often foment it), and the mischief they create sometimes complicates a thread so much that the core issues are lost. I also am a little tired of seeing complainants (myself included) criticized for choosing to file an AN/I report rather than pursing some other avenue. So, sometimes even if the report has its intended effect, the process of getting there is fraught with unpleasantness. For volunteer editors, this may not be worth it."

Another person said "an ideal solution would address the thanklessness of both the Admin's and the involved editor's role. Find a way to motivate Admins to spend more time, not less, per case. Redistribute the workload load and review Admin decisions for signs that they are overworked and becoming burnt out." Other suggestions for increasing participation include, have a rotating "watch officer" to review inputs and disposition some of them."

Closing of AN/I cases The survey indicates dissatisfaction with the way that AN/I cases are currently closed.

Theme 4: Policy

[edit]

The survey finds that there are concerns around fairness of AN/I discussions that might be addressed with new policy. In particular, there were suggestions to make the discussions on AN/I fairer for new users. One respondent wants, "a greater commitment to fairness. Newcomers may not know all the ins and outs of Wikipedia but that doesn't automatically make them wrong in a dispute." Another comment suggests that the rule "Wikipedia:INVOLVED should be a rule for everybody at AN/I, not just admins. Otherwise 'popular' users often avoid heavy sanctions for issues that would get new editors banned."

There are mixed opinions among survey participants about the use of the BOOMERANG essay in AN/I discussions. As one user points out, "There is a tendency to issue "boomerangs" against the filer of a complaint -- mostly justified, but sometimes not so. Because of this, I try to make certain that the report is fully justified and of a serious-enough nature that it's worth the risk of an unjustified sanction being levied against me. I'd say in general, the AN/I community is overly fond of finding reasons for issuing boomerangs."

Additionally, the survey results show that some respondents want improved policies or enforcement of existing policy in order to positively change the tone and substance of the discussions on the AN/I during cases.

Other commenters want "restrictions on non-administrators participating in discussions, limiting them to a certain number of edits per month. They say that "this might attract admins to participate there more consistently."

Theme 5: More structure for reports to AN/I

[edit]

While there was not concurrence about a specific type of change, there was strong feedback suggesting the benefit of modifying the structure of reports to AN/I.

In your opinion, what changes should be made to how reports are made on AN/I?

Participants could select more than one answer


5.88% did not select an option [?]


1 – Use of structured reports (e.g. form-based submission) (59.06%)
2 – Private reporting (11.02%)
3 – Multiple options for reporting (e.g. public reporting and private reporting) (35.43%)
4 – It's fine the way it is (25.98%)
5 – Other (see next question) (31.50%)
Around a quarter of respondents thought that AN/I was fine the way it was, but almost 60% wanted some form of more structured reporting.

One participant points out, "How ANI is currently built is extremely conducive for agenda driven editors to watch the page all the time and continue drama and other "power maneuvers" against "other factions" I think having some fundamental changes in design could incentives people to be civil and/or look for peaceful resolution, rather than always try to escalate."

One respondent's suggestion is to "create an optional submission form that would (1) automatically generate links to mentioned users' contributions, (2) automatically notify those users, and (3) eliminate edit conflicts when initially filing a report." Other users wrote in suggestions like "Standardize reporting, to avoid walls of text", "Structured reporting (with opt-out allowed)" and "Use subpages for issues to avoid edit conflicts."

Theme 6: Other technical improvements

[edit]

While there is not agreement about specific ideas, there is feedback that technical solutions could improve the function of AN/I. Some suggestions include:

  • Tool for sorting/filtering posts
Respondents also highlighted issues with uninvolved participants on the noticeboard; some contributions from participants uninvolved with the cases were seen as unhelpful or distracting. Some free text survey comments suggest to approach this problem by developing methods to sort or filter comments by participant.
  • Private reporting system
Some respondents want to provide an opportunity for anonymous, or privacy-shielded reporting that protects personal information about gender and other personal information that might be used for retaliation.
  • Improved search feature
The ability to search current and old cases to locate related cases.
  • Twinkle or other gadgets to make reports and manage cases.
New or improved gadgets for use on Wikimedia projects.
  • Tool(s) to assist with finding and adding evidence to reports
Better tools to search for and add diffs to reports.

Conclusions

[edit]

Several comments by survey participants concisely summarize opinions about AN/I that were commonly stated in the survey.



The results of this survey, similar to some community discussions around improvements to AN/I, do not point to a single point of improvement. However, the findings do strongly point to several areas where contributors see opportunities for improvements. Some would involve technical solutions, such as structural changes like form-based submission. Some would need social and procedural changes, such as the suggestions around clerking and moderation.

This research was prepared as part of a larger project to give Wikimedia communities more data when making decisions about their policies, and the processes used to enforce them. Support and Safety and the Anti-Harassment Tools team are committed to providing resources for community-supported change, be that technical development, further research, or coordination support.

We welcome discussion on the results on the talk page, and will be following and participating as they develop. If you have ideas about how to further research processes like AN/I, we would be happy to discuss them.

Notes

[edit]
  1. ^ a b c d e Some responses were sorted into more than one "bucket", which means that the number of actual responses may be less than the total number of bucketed responses.
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy