Handling harassment incidents swiftly and safely

This article was written by me and originally published on the Ada Initiative’s website. It is republished here according to the terms of its Creative Commons licence.

As anti-harassment policies become more widespread at open technology and culture events, different ways of handling harassment incidents are emerging. We advocate a swift process in which final decisions are made by a small group of empowered decision makers, whose focus is on the safety of the people attending the event.

Open technology and culture communities, which often make decisions in a very public way, can be tempted to also have a very public and very legalistic harassment handling process, a judicial model, but we advocate against this. It prioritises other values, such as transparency and due process, over that of safety. Alternatively, because many members of such communities find ostracism very hurtful and frightening, sometimes they develop a caretaker model, where they give harassers lots of second chances and lots of social coaching, and focus on the potential for a harasser to redeem themselves and re-join the community.

But neither of these models prioritise safety from harassment.

Consider an alternative model: harassment in the workplace. In a well-organised workplace that ensured your freedom from harassment — a situation which we know is also all too rare, but which we can aspire to, especially since our events are workplaces for many of us — an empowered decision maker such as your manager or an HR representative would make a decision based on your report that harassment had occurred and other relevant information as judged by them, and act as required order to keep your workplace safe for you.

A well-organised workplace would not appoint itself your harasser’s anti-harassment coach, have harassment reports heard by a jury of your peers, publish the details of your report widely, have an appeals process several levels deep, or offer fired staff members the opportunity to have their firing reviewed by management after some time has passed.

Like in a well-organised workplace, we advocate a management model of handling harassment complaints to make events safer: reasonably quick and final decisions made by a small group of empowered decision makers, together with communication not aimed at transparency for its own sake, but at giving people the information they need to keep themselves safe.

The management model of harassment handling is that:

  1. you have a public harassment policy that clearly states that harassment is unacceptable, and gives examples of unacceptable behaviour
  2. you have a clear reporting avenue publicised with the policy
  3. you have an empowered decision maker, or a small group of decision makers, who will act on reports
  4. reports of harassment are conveyed to those decision makers when reported
  5. they consider those reports, gather any additional information they need to make a decision — which could include conduct in other venues and other information that a very legalistic model might not allow — and they decide what action would make the event safer
  6. they communicate with people who need to know the outcome (eg, with the harasser if they need to change their behaviour, avoid any people or places, or leave the event; volunteers or security if they need to enforce any boundaries)
  7. they provide enough information to the victim of the harassment, and when needed to other attendees, to let them make well-informed decisions about their own safety

Further reading

Creative Commons License
Handling harassment incidents swiftly and safely
by the Ada Initiative is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Based on a work at https://adainitiative.org/2014/07/23/handling-harassment-incidents-swiftly-and-safely/.

Are your lulz low quality? Valerie Aurora is here to help

This article originally appeared on Geek Feminism.

Warning for mention of sexual assault, and extensive discussion of harassment.

In May, my GF co-blogger and Ada Initiative co-founder Valerie Aurora posted Handy tips for my Internet harassers on her blog. They included:

Threatening my job: Unfortunately, I am my own boss. Try emailing one of the Ada Initiative sponsors? Although they might take that as a sign that the Ada Initiative is doing important work and make another donation. Hmmmm. Maybe create a Yelp page for my file systems consulting business and leave bad reviews? Endorse me for CSS on LinkedIn?

Rape and death threats: Run spell check! There’s nothing more jarring than reading an otherwise creative and well-written death threat and then seeing “decapetate.” Also, chain-saws are so last year. Remember, Gmail won’t display images by default. P.S. I happen to know one of the members of Nirvana and your bright idea has already been done.

Why did she do such a thing, and what resulted? Geek Feminism obtained an exclusive tell-all interview.

Q. Have you received any harassment as a result of this post? Was its quality indeed improved?

Sadly, no. Part of the problem is that my friends loved it — I’ve never had so much positive feedback on a post — but they didn’t want to share it with other people online. I like to joke that it’s the ultimate in dark social since people only talk about it offline using vibrations in the air called “sound.” I think that my friends are more afraid of me being harassed than I am.

Q. The post is pretty out there! Why did you put this post up? What point are you trying to make?

“Self-doxxing” myself (thanks, Kate Losse for the term) was inspired in part by how incompetent and bad the online harassment that I’ve received has been. Most people doing online harassment are just trying to impress other online harassers, at the same time that what they are doing is, frankly, totally unimpressive. The reality is, anyone can spend $25 and get another person’s home address and a bunch of other personal information, but we act like it is some kind of amazing act of computer hacking. By showing how bad people are at online harassing, I’m hoping to remove some of the motivation for people to do the harassment, or at least make them spend more time on it before they get the reward of “so cool, bro!”

I was also inspired by Krystal Ball , who ran for U.S. congress in 2010. When her political opponents tried to slut-shame her into quitting her political campaign over “sexy photos” of herself that they published, she turned around and shamed THEM — both her opponent and the media outlets that published the photos. It was glorious, and it hit home for me: if we let the existence of sexy photo of a woman prevent her from serving in political office, then I and every woman born after 1990 were out of luck. Women’s representation in political office would go down.

Q. Should other people do this?

For most people, no, I wouldn’t recommend it. It was okay for me for a lot of reasons: I already went public about sexual abuse in my family, I’m white, I’m my own boss, I don’t have children or a partner, I have skills that are in high demand, I have lots of friends and a huge support network — my emotional, physical, and economic safety is pretty good. Most women have a lot more to lose.

However, I think it is a very good exercise to think about worst cases like this: what if the thing I am most afraid of other people finding out got published all over the Internet? Because a lot of times, that thing actually doesn’t reflect on you – the shame is on the person who did the original act or publicized a private matter. It can be healing to plan what you might do, even if you don’t actually go public with it yourself.

Q. Why won’t you accept my endorsement for CSS on LinkedIn? I taught you everything you know, dammit.

I’d hate to embarrass you by letting anyone else know that you are the source of my mangled <div>’s! [Ed: good point, well made.]

Q. When are you monetising this? How can investors contact you? How big is your Series A and at what valuation?

Actually, that is a great idea. Instead of vetting a political candidate and saying yes or no, you investigate them and then publish everything that might be a problem in a funny blog post.

Or better yet, here is my favorite idea: If I ever run for political office, I’m going to scan in all my embarrassing naked photos, then watermark them with the email addresses of various journalists. Then email them anonymously to said journalists. Then when the photos get published (it’s “news,” someone else would have, etc.), I can expose the specific person who decided that slut-shaming a candidate was “news” and put the shame where it belongs. Sexism-shaming as a service, SSaaS. I’m accepting funding now.

Code of Conduct timeline and postmortem

This article originally appeared on Geek Feminism.

Last week, Geek Feminism announced we’ve adopted a Code of Conduct.

As Annalee said in that announcement, this comes long after adoption of codes in other communities, especially events:

You’ve been promoting Codes of Conduct for years. Why didn’t you adopt one of your own sooner?

We dropped the ball in a big way here. We’ve known for at least two years that we needed a Code of Conduct internally. We’re sorry for the inexcusable delay.

We thought it would be useful to other communities to discuss how this happened.

Timeline

May 2008: Skud founded the Geek Feminism wiki, two and a half years before anti-harassment policies and codes of conduct began to be promoted by geek feminists.

August 2009: Skud founded the Geek Feminism blog, more than one year before anti-harassment policies and codes of conduct began to be promoted by geek feminists. At the time of launch. the blog had a strong comment policy which remains in essentially the same form (albeit expanded since). We weren’t the first by a long way to have such a policy (in fact it was based fairly closely on that of Hoyden About Town) but this was at the time unusual among the technical blogs and forums that many of the original bloggers frequented.

November 2010: Warning for assault Nóirín Plunkett was assaulted at ApacheCon. Within the month, Valerie Aurora had released a draft anti-harassment policy for events and finalised it for events to adopt. This is the policy that is now maintained on the wiki.

I have not found any discussion of Geek Feminism adopting such a policy internally at this time, which isn’t surprising considering it was envisaged as being for in-person events.

Early 2011: there were person-to-person complaints within the Geek Feminism community that an individual within it is harassing people when Geek Feminism contributors meet up in person (as sometimes happens at conferences we attend and similar).

January 2012: AdaCamp Melbourne (the first event I know of run by Geek Feminism community members that occurred after the development of the event anti-harassment policy) has an anti-harassment policy.

July 2012: Blogger Nice Girl reported harassment at OSCON by attendees identifying as geek feminists and using terminology from our wiki. (We do not know the identities of these people.) In August, Skud wrote on the blog:

We are taking a few different steps to address the specific concerns raised. One is that we are reviewing our wiki pages to make sure that we have information on slut-shaming and that it is appropriately cross-linked with articles about sexualised environments at geek events to help reinforce/educate people that criticising an individual woman’s choice of clothing is very different from criticising (for instance) a business that uses booth babes as a marketing device.

The second thing is that we are setting up a process so that people can contact us if they experience harassment by someone associated with GF. This is a work in progress, especially since GF is (as mentioned) a loose affiliation with no official membership, and because we may be asked to deal with harassment that occurs outside our own spaces. However, if someone is harassing another person under GF’s name or in a way associated with GF, then we want to provide a private way for people to contact us, and respond appropriately.

On the same day, Skud wrote the first version of the wiki’s Slut shaming page.

At around this time, Skud founded Growstuff, reducing her available volunteer time; her participation in the blog and other Geek Feminism activities dropped drastically over the next few months.

July/August 2012: Emails about the harassment by a Geek Feminism member discussed earlier began to circulate among Geek Feminism bloggers, presumably with our awareness of internal harassment risks heightened by the public and private discussions of Nice Girl’s reports. More than one person reported feeling unsafe and no longer recommending our backchannels as safe spaces. Skud first became aware of these reports at this time.

Given the seriousness of a known harasser operating in a community central to anti-harassment policy promotion, it didn’t seem appropriate to wait for a policy and response group as mooted by Skud to be in place and instead Valerie Aurora spearheaded a letter asking this person to leave the community, which was signed by several others including myself. The person left our community.

After this, I cannot find any further internal discussion of an anti-harassment policy for approximately another year.

April 2013: Recognising her lack of availability for volunteering due to work commitments, Skud formally announced she was stepping down as a Geek Feminism administrator. There was a discussion about handing over various technical responsibilities but not (that I can find) about the anti-harassment status.

July 2013: I sent an email to the blogger backchannel reminding them that an anti-harassment policy is still to be developed. There was a short and inconclusive discussion.

October 2013: Annalee produced an early draft policy document with many unresolved questions, particularly who the policy was intended to apply to, and how reports would be resolved. Comments on the document were made by several community members.

November 2013: Rick Scott began to formalise existing editorial practice on the wiki in the Editorial guidelines page, which was revised over a few months by a small group of wiki editors. It is intended more to communicate norms to newcomers and onlookers than to protect wiki editors from each other.

January 2014: Discussion had died down on Annalee’s draft. I sent an email with some open questions but no one including myself follows up before May.

May 2014: Annalee produced a new draft anti-harassment policy and circulated it for discussion. Skud, Tim, Valerie and myself all commented and edited substantially. Annalee asked for consensus on adopting it, Valerie suggests she JFDI, and I ended up proposing a timeline through to late June for circulating it more widely, giving people time to familiarise themselves, appointing the Anti-Abuse team, and then making the document public.

June 2014: The Anti-Abuse Team was appointed after an internal feedback process. Annalee announced our Code of Conduct publicly. I made our policy made available for reuse and promoted adoption by other communities.

Post mortem

Things we did right

Skud established best practices (particularly the comment policy) at the time our community was founded.

When it became clear that harassment in our community was a periodic problem, we acknowledged publicly that we had not put best practices into place (a anti-harassment policy) and began discussing one suitable to our community.

We returned to the issue periodically without further external prompting or known (to me) incidents of harassment and eventually got a policy in place. In the process, we hope we have developed a new best-practice policy for communities to use so that others do not have to go through this process.

Our new policy has a pretty sophisticated description of various types of harassment, based on a wide variety of personal experiences and reports of harassment received by those of us who do anti-harassment action or advising in other communities. It is better adapted for a long-lived community than the event policy is, by, eg, considering incidents of harassment in the past and in other communities. It has a more explicitly feminist stance in, eg, stating that it centres the concerns of marginalised people, and that tone-policing will not be regarded as harassment.

Things we did wrong

Various individual members of the community were slow to recognise harassment in our community based on first-hand reports from victims.

We were very slow at responding to the known need for a policy, especially for a group which was among the leaders in advocating that in-person events adopt policies. Even on the most generous reading of this timeline, there was explicit discussion of an internal anti-harassment policy in August 2012, at the time Skud discussed Nice Girl’s harassment, meaning that nearly two years passed between us explicitly committing to it existing and it being put in place. We seem to have been caught in a common problem here: we had no active need for the policy (that I know of personally), and so we did not push ahead with it.

Less central members of our community report that they wondered why we didn’t have a code of conduct, but did not feel empowered to ask about it.

Where to from here?

It is far better to have clear documentation concerning safety in particular, and common problems in general, before they are needed. We hope our reusable policy gets adopted by other communities or assists them in drafting their own, to avoid some of the slowness involved in starting from scratch.

Skud reviewed our community structure and documentation in the lead-up to her Open Source Bridge talk and found various inadequacies. She and Annalee have each raised the issue of reviewing our community’s processes,. We would need to look at questions such as:

  • are we following best practices in anti-harassment, anti-abuse and establishing safer spaces?
  • is our group unusually reliant on certain individuals and if so (it usually is so in any community), how can we share knowledge and resources so that there are less single points of failure?
  • is our documentation sufficient for a newcomer to the community?

Does anyone have pointers to similar review processes in other groups? That would be really handy.

Skud suggests that in addition, with important projects like a code of conduct, a relatively structureless group like ours explicitly appoint people to the project, so that they feel empowered to act on it. We particularly need to be alert to Warnock’s dilemma (does silence signify consent, ignorance, lack of understanding, lack of interest or contempt?) in discussing changes to our community. We also need to be alert to hidden hierarchies, to, eg, the sense that nothing can go ahead without approval from, say, Skud as founder or myself as the most frequent poster.

Annalee suggests that we need to improve our institutional memory with documentation like that above, together with internal private documentation where it is impossible to make things public. This helps identify when things were done for a very good reason, versus having emerged essentially by accident, versus never having been done at all by anyone. We also need to clarify (probably continuously) about whether we are a JFDI community, or whether projects must have people appointed to them, or other.

Acknowledgements

Thanks to Annalee, Maco, Skud, Valerie and one of the linkspammers for their review of this post. Except where explicitly attributed, all opinions herein should be taken to be mine, informed by discussion with others in Geek Feminism but not necessarily co-signed by them.

Is harassment in your community unwelcome? Adopt a Community Anti-Harassment Policy!

This article originally appeared on Geek Feminism.

Last week, the Geek Feminism community announced that we’ve adopted a code of conduct in our community. Our code begins:

The Geek Feminism (GF) community is dedicated to providing a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of participants in any form.

This code of conduct applies to all Geek Feminism sponsored spaces, including our blog, mailing lists, and wiki, as well as any other spaces that Geek Feminism hosts, both online and off. Anyone who violates this code of conduct may be sanctioned or expelled from these spaces at the discretion of the Geek Feminism Anti-Abuse Team.

We took quite a long time to do this, after two harassment incidents associated with the Geek Feminism community (albeit, one probably not by people who are actually active in our spaces and who therefore can’t be excluded from them). We’d love it if others learned from our example and adopted a policy within their own communities. To that end, as of today, our Community Anti-Harassment Policy is available for re-use under Creative Commons Zero/public domain and we are beginning to develop associated resources, just as we have done over the past few years for the Conference anti-harassment policy

Here’s what you need:

  1. a policy (remember, ours is available for re-use, either as is, or in a modified form)
  2. a contact point where harassment reports can be received
  3. a group of responders who receive reports and have the power to act on them up to and including excluding harassers from your community

If your community does not have an obvious way to create a group of responders, start discussing how you can create one. In many communities, there is likely to be an existing volunteerocracy at the very least. Can these people reach consensus that your community should be safer from harassment, and that they are unwilling to work with harassers? Simply announcing to people that they must cease a behaviour, or they must leave the community, is in fact very effective as long as there is basic consensus around community norms. For online groups technical structures can help, but social structures are in fact the root of anti-harassment. You don’t need ops or admin power or the crown of the ancient rulers to enforce anti-harassment policies in your community, you need consistent anti-harassment responses by people with social power.

If you don’t know that your community has concensus on being anti-harassment. as a start you can declare your own personal anti-harassment stance, and publicly call for your community to adopt a anti-harassment policy, and a structure that enables the response team to exclude people from the community.

As Geek Feminism shows, activist groups or groups that have advocated for anti-harassment are not safe from internal harassment and still need a policy. And groups with no known harassment incidents are also not safe; it’s quite likely that people in your community have experienced harassment they felt unable to identify or report. Take steps to ensure harassing behaviour becomes known, and that it is known to be unacceptable.

One specific model we encourage you to avoid is the Our community is amazing! So wonderful! We rock! PS no harassment model in which you spend a lot of time affirming your community’s goodness and make a general statement about anti-harassment in passing. We discourage putting this in your anti-harassment policy for these reasons:

  1. you probably do not know the extent of harassment in your community without a policy and a reporting mechanism, and may not rock as much as you think
  2. stating that you are “anti-harassment” without saying what harassment means to you doesn’t give your existing community and potential new members the information they need to find out if their safety needs are a close enough match for your community’s norms

Stating your community’s great work or exemplary behaviour can be really useful for establishing social norms and letting people understand what joining your community means. They form a good basis for specific policies. But don’t make such statements in your anti-harassment policy, make them in a separate document listing your community’s values and goals. And it may be best to say that you aspire or intend to create an amazing space, rather than that you have definitely attained that goal. Statements that you are definitely no questions amazing may be used to silence people with critical feedback and in the end reduce your amazingness.

We also discourage private anti-harassment policies (shared only within a community or within its leadership), for reasons outlined by the Ada Initiative [disclaimer: I co-founded the Ada Initiative].

Do you already have a community anti-harassment policy, or have we convinced you to adopt one? List your community on the Community anti-harassment adoption page! And thank you.

Harassment report at your conference: what do you do???

This article was written by me and originally published on the Ada Initiative’s website. It is republished here according to the terms of its Creative Commons licence.

The Ada Initiative’s anti-harassment work and other anti-harassment initiatives have resulted in many conferences adopting anti-harassment policies.

The Ada Initiative are not enforcers of individual conferences’ policies: this is the responsibility of conference staff, and conferences do not usually inform us of reports, nor do we expect them to. Harassment within a community is that community’s responsibility. However, in some cases when Ada Initiative staff have attended a conference, we have been asked to advise conference staff on responses. We’ve learned several useful techniques for making sure that the conference follows through quickly on its commitment to anti-harassment. We’ve drawn our experiences together into a wiki page: Responding to harassment reports.

Our first tip is, of course, to have a policy. Harassment incidents at geek conferences — including open technology and culture conferences — are widespread. If harassment is reported at your conference and you do not have a policy, it is difficult to reach consensus among conference staff that harassment is not welcome, let alone that you should respond to it, or about how you should respond. The result is that people who are worried about harassment, or who have experienced it at your event or other events, will not feel or be safe at your event. Your policy should be in place before your conference. The Ada Initiative and Geek Feminism volunteers have prepared substantial resources on how to put a policy in place.

You should also pre-prepare some emergency contacts, for incidents that you can’t handle. Conference volunteers and staff are rarely able to solely respond to and properly help with physical safety threats, illness or people in crisis. We suggest preparing a handout with contacts for emergency services, venue security, local medical and mental health facilities and crisis hotlines for mental illness, sexual assault, and physical violence. Make this info available in your conference materials so that attendees do not have to come to you, but have copies to hand in case they do.

Having a staff member whose key responsibility is to assist attendees in difficulty (rather than routine conference chores) can assist in a fast response, see the Duty officer wiki page.

Unfortunately, having a policy does not mean harassment won’t occur at your event. Once an incident is reported, you need to respond rapidly to reports. As the wiki page discusses in more detail you should:

  1. get a written report where possible, or have the staff member who received it write down what they were told
  2. have a staff member collate these reports in case of multiple incidents of harassment by one person, so that you can respond to the pattern rather than one instance
  3. have a staff member discuss the incident with the alleged harasser
  4. convene a meeting as soon as reasonably practical to decide on a response
  5. decide on a response and communicate it to the complainant and the harasser as soon as possible
  6. provide the harasser with an avenue of appeal if one is available but insist that they abide by any sanctions in the meantime
  7. communicate the incident and response briefly to the community, either attending the conference or reading your blog etc, to allow them to see that the policy is enforced
  8. remind the attendees and community where the policy is found and invite them to review it

We welcome additional improvements to our detailed guide on how to respond to harassment reports. If you would like to discuss the suggestions, please do so on the wiki’s talk page.

Creative Commons License
Harassment report at your conference: what do you do???
by the Ada Initiative is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Based on a work at https://adainitiative.org/2012/10/04/harassment-report-at-your-conference-what-do-you-do/.

On feeling less safe

This article originally appeared on Geek Feminism.

Over at Hoyden About Town, Wildly Parenthetical considers Tackling Misogyny: Procedures or Social Sanctions?:

But more interesting has been the discussion about formal and informal mechanisms for dealing with sexual harassment. There are lots of reasons that formal mechanisms don’t work for lots of people… So we have the suggestion of informal “shunning’. Some have, with more and less hyperbole, suggested that without the formality of systems of justice and the “certainty’ they’re meant to bring, individuals could wind up excluded on heresay; this is the “OMG WITCHHUNT!’ objection. And others have pointed out that social sanctions are applied to all kinds of behaviours that are disapproved of in our society, and why should this particular behaviour be any different? I am pretty much with the latter group, although I understand those who think that we should be putting our energies towards fixing the formal systems rather than developing shun-lists…

I left a comment that I want to re-post here, since it captures neatly a lot of my more negative feelings about discussions around anti-harassment policies and such, which a lot of people in the geek community consider informal since geeks themselves will enforce them.

My response (very slightly edited here) was as follows:

I am a fan of social sanctions in an ideal world. There tend to be two problems with introducing it in practice:

  1. Some people at either the level of instinct or the level of rational analysis find it almost impossible to distinguish from bullying (see the Geek Social Fallacies, especially #1) and refuse to participate or actively attempt to defend the person sanctioned or decide to sanction the sanctioners, causing a lot of internal community conflict.
  2. It often turns out (at least in communities that I’m a part of) that not as many people are opposed to sexual harassment as one might hope. So a substantial fraction of participants oppose social sanctions or vow to not enforce them because it turns out they like sexual harassment just fine.

Option 2 is always a really distressing conversation to have in a community you felt safe in; you seldom feel safe after it turns out that a loud minority feel that sexual harassment is the effective/normal/desirable (at least, but not exclusively) heterosexual mating strategy.

How is everyone else feeling about the geek community after whatever their latest local round of feminist discussion was? I’m far from entirely negative, but there are definitely whole new places I don’t feel safe from harassment and indeed assault now.