What I’ve learned from Objectify A Male Tech Writer Day – and why I’m calling it off

The real mission has to be making everyone feel welcome, period.

"Objectify A Man in Tech Day" has become much bigger than I expected since I first wrote about it. At first I was excited, but now I see the scale of the discussion and coverage is creating a number of valid risks - and as a result, I'd like to call off the event.

The widely-covered event started out as a lark that emerged when I got fed up with experiencing - and seeing other women writers and presenters in gaming and tech - fielding irrelevant compliments on their appearance when people referenced their work.

I hoped the result of what we began calling "#Objectify day" would catalyse discussions about the way we use language and how seemingly-innocuous "compliments" are belittling and distracting. A lot of people liked this idea, understood the intention and found it fun.

My goal was that humor and empathy could help people open constructive dialog about sexism. And for a while it seemed like it could work! But there were also a lot of problems with my approach that came to light thanks to the feedback of some trusted friends and colleagues, and I take their concerns extremely seriously.

The dialogue's been great, but the end result - a day of circulating a hashtag on Twitter - runs the risk of catching fire with people who miss the point. #Objectify is not about celebrating objectification or about making people feel uncomfortable, but I'm increasingly worried that point will be lost and that harm can be done.

My friends and I have done our best to put clear information about our goals out there, but the sad fact is we can't expect everyone to read up or treat one another with respect. And there are some problematic risks even assuming everyone does "get it": We liked people comparing #Objectify to the Hawkeye Initiative but that also means we must consider similar criticisms, and the very real risk that our event would solicit homophobia, transphobia, ableism and other prejudices.

Though we wanted to call out gendered language, focusing on men in this way makes some dangerous assumptions about gender norms and sexuality:

For one thing, the event as it stands currently ignores the fact that gay men, trans men, men of color and any other man outside the "straight white guy privilege" zone are already victims of objectification. "Objectify a man" risks using harmful language toward people who may be vulnerable.

For another, some people feel that an environment of men tossing cute comments at each other ends up reducing women's sexual agency to a joke, since the compliments won't actually have the same effect on their intended recipients. But it's worse if the compliments do affect someone negatively -- is potentially triggering men who have body issues a victory for anyone?

We also need to consider people who live outside of the specific gender binary our society enforces: There are trans women, genderqueer and non-conforming people struggling every day not to be misgendered, and people living quietly with gender issues they may not share in the open. If these people end up caught in the crossfire of our event it doesn't matter whatsoever how well-intentioned we are: We risk actually traumatizing them.

I hoped discussions of gender norms would be one of the positive outcomes of #Objectify, and that attention to the issue would make it all worth some inevitable hostility. But for some people who may be exposed to the wrong kinds of language on the planned day, misunderstanding can be actually harmful, and that is absolutely not a risk I want to take.

"Starting dialogue" this way isn't worth potentially triggering others, putting them at risk or making them feel unsafe. I feel naive that I failed to fully consider the potential ramifications and want to apologize to anyone that was made uncomfortable or who felt threatened by my choice to approach an issue in this way.

There are a few good things, here: it's been an incredible learning experience, and I am still proud of the respectful attention my colleagues, friends and readership have given to issues of objectification and of making women feel welcome in tech. I've had positive conversations that would have been impossible even a year ago. That it took off in a larger way than I ever could have expected shows on some level that people care about change, and that makes me glad.

But the real mission is making everyone feel welcome, period. What I wanted to encourage through humor was caring, empathy and a willingness to listen and educate - now I've been asked to change course, and by calling a halt to #Objectify I hope I'm modeling those same qualities myself.

When people tell you they are hurting, are afraid or feel excluded, you don't get obsessed with your own sense of righteousness, you listen That's what this has always been about.

If you've been paying attention, I hope you continue thinking about the words you use to describe other people and their work. Please continue aiming to listen to and care for everyone who needs your help to feel respected, safe and welcome in tech -- or anywhere.

If you understood and appreciated our intention we thank you for your support, but we ask that if you've written about Objectify to please remove your post, or at least modify it to reflect our reasons for reconsidering this event.

Thanks for your compassion.

Leigh Alexander, gaming and social media culture journalist, is Gamasutra editor-at-large, columnist at Edge, Kotaku and Vice Creators Project, and contributor to Boing Boing,Thought Catalog and numerous others. This post first appeared at her blog, Sexy Videogameland.

There'll be no more objectification. Look at this lovely picture of a baby giraffe instead. Photograph: Getty Images
Getty
Show Hide image

Is Google Maps discriminating against people with disabilities?

Its walking routes are not access-friendly.

“I ended up having to be pushed through a main road in London, which was really scary.” Three weeks ago, Mary Bradley went to London to visit her daughter Belinda, who is just finishing her first year at university there. Her other daughter joined them on the trip.

But what was supposed to be an enjoyable weekend with her two children turned into a frustrating ordeal. The apps they were using to find their way around kept sending them on routes that are not wheelchair-friendly, leading to time-consuming and sometimes frightening consequences.

Bradley has been using a wheelchair – when having to go longer distances without a vehicle – for over a year, due to a 45-degree curve in her spine, severe joint facet deterioration in her back, and other conditions.

She lives in Weston-super-Mare in Somerset, and has made the trip up to London to visit her daughter a handful of times. Each visit, they use Google Maps and the transport app Citymapper to find their way around, as neither of them know London particularly well.


Belinda and Mary Bradley. Photo: Belinda Bradley

“It was just horrible,” says Bradley of her most recent trip to the capital. “We’re following the maps, and we go along, then find we are faced with a footbridge, and realise there was no way I was going to get over it, so we had to go back the way we’d come. At one point, we were faced with a strip of narrow pavement the wheelchair couldn’t go down. That was something we found all weekend.”

While Google Maps did highlight accessible Tube stations, they found that once they had alighted to do the rest of the journey to their destination on foot, “it took us three times as long, because the route that it takes us just wasn’t passable”.

They ended up having to try different routes “having no real idea of where were going”.

“It meant that it took so much longer, the girls ended up having to push me for longer, I got more and more embarrassed and frustrated and upset about the whole thing,” Bradley tells me.

At one point, her daughters had to take her down a main road. “Being pushed on a road, especially in London, is scary,” she says. “It was scary for me, it was scary for the girls.”

When they returned home, Belinda, who is a 19-year-old Writing and Theatre student at the University of Roehampton, was so furious at the situation that she started a petition for Google Maps to include wheelchair-friendly routes. It hit over 100,000 signatures in a fortnight. At the time of writing, it has 110,601 petitioners.


Belinda's petition.

Belinda was surprised that Google Maps didn’t have accessible routes. “I know Google Maps so well, [Google]’s such a big company, it has the satellite pictures and everything,” she says. “So I was really surprised because there’s loads of disabled people who must have such an issue.”

The aim of her petition is for Google Maps to generate routes that people using wheelchairs, crutches, walking sticks, or pushing prams will be able to use. “It just says that they’re a little bit ignorant,” is Belinda’s view of the service’s omission. “To me, just to ignore any issues that big needs to be solved; it needs to be addressed almost immediately.”

But she also wants to raise awareness to “make life better in general” for people with disabilities using navigation apps.

Belinda has not received a response from Google or Citymapper, but I understand that Google is aware of the petition and the issue it raises. Google declined to comment and I have contacted Citymapper but have not received a response.

Google Maps does provide information about how accessible its locations are, and also allows users to fill in accessibility features themselves via an amenities checklist for places that are missing that information. But it doesn’t provide accessible walking routes.

“There’s no reason that they couldn’t take it that bit further and include wheelchair accessible routes,” says Matt McCann, the founder of Access Earth, an online service and app that aims to be the Google Maps for people with disabilities. “When I first started Access Earth, I always thought this is something Google should be doing, and I was always surprised they haven’t done it. And that’s the next logical step.”

McCann began crowdsourcing information for Access Earth in 2013, when he booked a hotel in London that was supposed to be wheelchair-friendly – but turned out not to be accessible for his rollator, which he uses due to having cerebral palsy.

Based in Dublin, McCann says Google Maps has often sent him on pedestrian routes down cobbled streets, which are unsuitable for his rollator. “That’s another level of detail; to know whether the footpaths are pedestrian-friendly, but also if they’re wheelchair-friendly as well in terms of the surface,” he notes. “And that was the main problem that I had in my experience [of using walking routes].”

Access Earth, which includes bespoke accessibility information for locations around the world, aims to introduce accessible routes once the project has received enough funding. “The goal is to encompass all aspects of a route and trip,” he says. Other services such as Wheelmap and Euan's Guide also crowdsource information to provide access-friendly maps.

So how long will it take for more established tech companies like Google to clear the obstacles stopping Mary Bradley and millions like her using everyday services to get around?

“You can use them for public transport, to drive, you can use them if you’re an able-bodied person on foot,” she says. “But there are loads of us who are completely excluded now.”

Sign Belinda Bradley’s “Create Wheelchair Friendly Routes on Google Maps" here.

Anoosh Chakelian is senior writer at the New Statesman.