Last week in sexism

Last week wasn’t all bad, but it was exhausting. Despite the many good things that happened, it was one of the harder weeks I’ve had in a while, and it was hard specifically because I’m a woman.

The most obviously inappropriate thing that happened to me last week was that someone left a love-note on my desk. It was short, fitting in the small, square space on the top of my post-it pad, and unsigned, aside from the XOXO at the bottom. The pen used to write it was left lying casually across the top, a generic ballpoint, translucent blue on bright, matte, neon blue.

I haven’t been able to touch the pen. I just stare at it and feel my stomach turn a little bit. I don’t quite know what I feel. Someone came into my office, which I lock religiously, and left me this weird note. It’s so strange, it hardly seems like it was meant for me. It’s probably nothing. Probably harmless. Maybe a joke, or a prank even. Though I haven’t found the humor yet. I don’t feel unsafe, exactly—until I really stop and think about it, and wonder if I should.

Still, in some ways, it’s easy to deal with. There’s a process. Everyone I work with has been exceptionally supportive through the weirdness, and we’re having all the conversations with the folks who manage our building that we’re supposed to be having. I am both lucky and privileged in this respect—lucky to have thoughtful and kind colleagues, who want to create a comfortable, safe work environment for everyone, and privileged, as a well-off, white, straight, cisgender woman, to have the confidence that my concerns and fears will be taken seriously.

The other things that happened last week were more insidious, and for many reasons, are much harder to talk about. The stories that every woman I know can tell. The casual comments that draw attention to the fact that you’re the only woman in the room. The discomforting conversation with a man who either doesn’t realize, or doesn’t care, that his enthusiasm and persistence reads as aggression and feels inappropriate. The moment you realize your arms are crossed over your chest and your back is against the wall, that your body is radiating “I don’t want to be here,” and yet, seems to be doing so in a language no one around you can read. That was my week.

I am, again, both lucky and incredibly privileged that this was an atypical week for me. Still, I find that these moments tend to bleed into one another. They call back memories that have that same sour taste and heavy feel. My high-school classmates who were certain that the only girls who got A’s in physics were the ones who wore short skirts. The federal employee who saw my “Summer Intern” badge and, upon hearing where I went to college, asked if I was getting my “MRS degree.” The men who hollered at me as I walked down the street toward them, and then hollered some more about my ass as I walked away. The guy I looked up to professionally, who tried to get me to come back to his hotel room during a conference. The time my picture ended up in an article that called women ignorant, apathetic, and lazy for having the temerity to use FourSquare.

None of these were big, life changing events, just as nothing that happened last week was a big, life changing event. They were just moments in time, and some were relatively small ones at that. Still, they are all connected in my mind—strung together in a slow, steady drumbeat of sexism and yes, misogyny, that seems to stretch backward and forward in time.

It is not weather, but climate. There are bright, shining, beautiful days, and I am privileged to have more of them than most. But the overarching trend of the region, the region of being a woman in most industries, in most countries in the world, is still heavy and grey.

My story, these moments, they are not unique. I have never shared them with another woman and not heard similar stories in response. Still, it feels like a risk to write this, to add my voice to the chorus of women who have shared their own stories before. Because of course, the perverse irony is that often, to share your experience with sexism and misogyny is to make yourself a target for more sexism and misogyny. Yet, I know of no other way to silence the drumbeat than to produce an equally steady beat of our own, to counter the weight of the air by sharing these moments and affirming that they are real, they are happening. They are happening to women you love, and women you hate, and women you never even think about. But none of us deserve them.

It’s not enough, but perhaps it is a start—perhaps by shining light on these moments, we can eventually change this climate, and create a future with weeks full of brighter days instead.


This post originally appeared on The Pastry Box Project.

Let’s talk about comments

If you’re reading this, I’m willing to bet you’ve heard, or said, "Don’t read the comments!” at one time or another. I know I have. It’s usually accompanied by an eye-roll and a heavy sigh, the implication clear: of course you shouldn’t read the comments, surely you know better than to expect anything good to come from this morass of the web now, in twenty-fourteen.

That’s actually how I first began to question the belief that comments were just a sad pit of internet despair. Few things raise my hackles, or my skepticism, like the argument that we should be embarrassed or ashamed for believing things could be better than they are. It’s cynical, dismissive, and downright disdainful of a way that many people use the web.

I’ve written before that at their best, comments are a form of community. Given what I do for a living, I’m naturally loathe to see online communities start disappearing from the web. Some argue that comments are superfluous in the age of social media; now that everyone can have a Twitter or Facebook profile, even their own blog, for free, the comment section is hardly the only place dialogue occurs. While that’s certainly true, it glosses right over the fact that someone might have valid reasons for not wanting to maintain a presence on those platforms, or hell, might want to have a conversation about a particular topic without inviting all of their Twitter followers and Facebook friends into the mix.

More than that, at a time when Google, Facebook, Twitter, and seemingly every other website, is trying to predict our needs and interests, tailoring the web to what they think we’ll like, comments and community offer a refreshing opportunity for serendipity—the unexpected encounter that opens our eyes to a new perspective or idea. The realization that we have more in common than we thought.

Is that idealistic? Sure. But that doesn’t mean it doesn’t happen either. When we act like every comment section out there is as bad as what we see on YouTube, we’re dismissing a very real way that a lot of people have chosen to participate on the web, and we’re reinforcing this notion that comments are just inherently bad—that the content and the people who create it are adding nothing to the web, even taking away from it.

A little while back, Frank Chimero shared a talk he gave at the School of Visual Art’s Thesis Festival. If you haven’t read it yet, you should. In the talk, he shares some examples of how Yellowstone National Park has dealt with the unpredictable nature of, you know, wildlife, over the years: when wolves were attacking cattle, they got shot; when bears were eating sandwiches (and destroying cars in the process), they started a “bear management” program, to help people learn how to enjoy the park without tempting or endangering the bears. Here’s Chimero:

“I’m sharing this weird parable about Yellowstone, because it describes both sides of how to approach problems. Some designers want to shoot the wolves, others want to manage the bears. One is trying to make an antidote, the other invests in a process to keep things open and adaptable.”

Most of what I see these days is people “killing the wolves”—getting rid of comments sections wholesale. Somehow, simply having a place for people to leave comments has not guaranteed that our comment sections will become a place for rich discussion and community—who’d have thought?

Having an interesting, worthwhile, and dare I say, engaging, comment section takes work. It is work to read through all the comments a site receives and decide what should or should not be published. It is work to bring together all the necessary people and get them to agree on what the guidelines will be, and who will enforce them. It is work to remind everyone of those conversations when people test those boundaries and are disappointed to find them enforced.

Obviously, not everyone is up for that, or interested in creating community in that particular way. The lovely folks here at The Pastry Box aren’t, and that’s perfectly fine. Somehow though, the fact that comment sections aren’t miraculously cultivated web-gardens, when we don’t do the work to keep them that way, has turned into this belief that they’re just inherently awful pockets of the web.

Here’s the thing though: comments sections don’t have to be terrible. Folks like Jennifer and her fellow bloggers at Captain Awkward, authors like Ta-Nehisi Coates, and the team over at Code Switch. These people write about difficult, challenging topics. They write about race, about relationships, about politics and feminism and whether or not it’s moral to watch NFL games anymore. These are not mundane topics—they’re lightening rods, third-rails of the web.

But you know what? The comments are pretty fascinating. I often learn something new from reading through them, and usually have a hard time pulling myself away. They’re fascinating because people put in the work: because they set boundaries, and then enforce them. Here’s Code Switch reflecting on their first year of conversations about race and culture on the web. It clearly hasn’t been easy, but they’ve found it to be a valuable experience, worthy of the obvious effort they’re putting into it, because they’re creating a place for discussion that might not exist otherwise.

Part of that boundary-enforcing means being willing to step in and remove comments that steer the discussion, intentionally or not, off the topic at hand. Many of us who work on the web have bought in to, on some level, the geek social fallacy that “ostracizers are evil,” and are loathe to play that role, even when it comes to web comments. We’re left with a sort of all-or-nothing approach: either we keep all the comments, except those so blatantly violating our guidelines that they can’t be ignored, or we throw out comments altogether, unwilling to play bad cop on our own sites. The middle-ground, being willing to prune our comment sections, is hard work, too. Matt Thompson, at Code Switch, outlines this for their readers:

“So if we delete your comment, it’s not necessarily because we think the comment is bad or wrong, or because we want to suppress your point of view. Most often, it’s because the comment doesn’t get at the topic we’re aiming to discuss at that moment, in this space. We are trying to curate a discussion that is intelligent, unique, and novel a discussion that moves us and that may require removing comments we think are not directly contributing to the focus of the conversation at that time.”

There’s another layer of work that goes into making these comment sections better than the rest: instead of ignoring the comments, or holding them in obvious disdain, these authors actually read and respond to them. People participate, in part, because they’re able to build a relationship with a writer they like and respect. Knowing that someone like Coates may read what you’ve written, and will probably call you out if you’re being a jerk, is a pretty good incentive for people to not just follow the guidelines, but actually share thoughtful contributions.

Seeing comments sections like these, it’s clear to me that there are ways for us to manage the bears, instead of shooting the wolves: we can create guidelines for our comments sections, we can enforce those, and we can engage with our commenters, encouraging them to participate in a way that benefits the community as a whole.

I have a hunch that the recent Open News-New York Times-Washington Post collaboration will provide some very interesting tools to facilitate this, though I suspect they have their sights set on a whole host of issues beyond comments as well. Still, at a time when so many sites are giving up on comments, and so many in our own community view them with contempt, it’s exciting to see smart people invested in improving this part of the web.

Not every site needs to be a community, and community can grow in a myriad of ways, but at its core the web is about connecting people and ideas. In a web that feels like it’s becoming more siloed and restricted, let’s try to keep things open and adaptable. Let’s manage the bears instead of killing off one of our methods for creating community, just because it’s been neglected or poorly executed in the past.


This piece originally appeared on The Pastry Box Project

Just ask

I’ve always loved this song, “Joan of Arc,” by the now defunct Actionslacks. It’s a cute little pop song about possibly unrequited love (do we listen to pop music because were miserable, or are we miserable because we listen to pop music?), and it’s got this seemingly obvious line: “The answer’s ‘no’ until you ask.”

When I first heard that, as a high school student, I was like: whoa. Probably because the two possible reactions I was capable of in high school were: "whoa" and rolling my eyes.

Still: “the answers ‘no’ until you ask.” And it’s true, right? One of my mottos as a community manager is: just ask. It’s easy to make assumptions about what the people who are using our websites will or won’t want, what they’ll use, how they’ll react to change. If you’re reading this, you know that you are not your typical user. But how often do we act on that?

A few years ago, I was asked to organize the first in-person meetup for GHDonline, where I work as an online community manager. We’d never hosted an official event for our members to meet one another in person before. As a community for health care professionals working around the world to share and discuss best practices, many of our members aren’t local, and we assumed they’d be too busy, or uninterested in meeting people outside their particular specialty areas.

We also worried that hosting an event in Boston, when so many members live and work internationally, would be seen as insensitive or tone-deaf to the reality of their day to day lives and obligations.

So, when we announced the event, we acknowledged that and asked folks to let us know if they'd be interested attending something similar in their region. The results were surprising: 50 or 60 people wrote in to say they wanted to attend a meetup in their community, and a number of people offered to help host or organize events in the future.

As I was reviewing these responses, I realized I didn’t recognize many of the people writing in. In a community of several thousand, I don’t know every member’s name, but I tend to remember the people who contribute regularly. I started to search our site, and realized that about half of the people who responded had never posted or publicly engaged in our communities before. Still, when asked if they’d meet other members face-to-face, many of them raised their hands.

We would never have known this if we hadn’t asked—wouldn’t have held the first meetup here in Boston, or organized another event that year in Delhi. We also wouldn’t have known that folks with a seemingly tenuous connection to our community actually identified with it quite strongly.

I’ve seen countless examples of this during my years as a community manager, but I’m still surprised by how often we, as an industry, skip this step.

Uncertain if someone will want to participate in your event? Ask.
Not sure how members will respond to a new feature? Ask.
Wondering what will happen if you change your terms of service? Ask.
Worried a new business model might go over poorly? Ask.

Ask ask ask. The worst that can happen is someone says no. Or they tell you they think your idea is a bad one, before you push it out to the world. Basically, the worst thing that happens is you hear something you didn’t want to hear. Which, well, welcome to the internet, I guess?

You’re going to hear things you don’t want to hear no matter what, so better to ask now than be surprised later.

Some of you are probably thinking, “But Steve Jobs! Henry Ford!” Which, sure, I guess. That faster horse line is a good one. Think of it like Pascal’s wager, but for making websites: maybe you are the second coming of one of those men, but if you’re not, wouldn’t it be nice to know what your users think before they start screaming it at you on Twitter?

There are, of course, a few caveats to this mantra:

Caveat the first: Do not ask people for feedback if you’re just looking for a rubber stamp on something. If you can’t, or won’t, make changes to a site, feature, product, whatever, it’s a waste of everyone’s time to ask someone what they think.

Try not to find yourself in this position. Ask before it’s too late not to.

Caveat the second: Ask people you trust to tell you the truth, and who can bring some perspective to the table that you don’t have.

Caveat the third: Sometimes, what you need to ask is: “What can l do for you?”

One of the few things I’ve found to be universally true in my time working on the web is that people on the internet will never cease to surprise you. Sometimes that’s a good thing. So remember, the answer’s no until you ask. The answers may surprise you.


This post originally appeared on The Pastry Box Project.