Improving Speaker Diversity
Last month at Devoxx I was in a session discussing what we can do to encourage more diversity in our speakers (specifically, although not limited to, increasing the number of women speakers).
I’m going to outline the things I remember being discussed, although as usual we did not find the answer to the problem, only identify some issues and explore some options.
This is a very chaotic blog post, because if I don’t post it now I’ll never post it, and it’s better if my thoughts are scrawled down and posted than if this all goes to die in my drafts folder.
Firstly, what stops people from stepping up to speak?
I don’t have anything to say
This is the very first thing any developer says when you ask them why they haven’t thought about presenting at conferences or user
groups. Turns out, you always have something to say. For example, our most popular sessions at the Sevilla JUG and MUG are “Introduction
to…”. You hear from plenty of experts who have travelled the whole road to some pinnacle of excellence,
but what many developers need is simply someone a couple of steps ahead of them to lead them forwards.
You always know more than someone, you don’t need to know everything, and you don’t need to know more than everyone
Why should I be role model?
So many women feel this, and I’m completely sympathetic to this view point: I’m a woman developer, getting along, happy in my job,
happy being a programmer, why the hell should I have to stand up and present and blog and be a role model for other women? Men don’t have
to do that. Men can just be developers.
In addition, there’s the fear that if you do stand up, become a role model, that somehow people will think you’re representing all women developers. You’ll be worried because you can only represent who you are, what you do, you can’t represent a whole gender in a single presentation or a single interview. And the pressure! What if I mess up? What if I say something my gender does not agree with? What if I say something that causes my whole gender to be judged?
Totally understandable fears. Totally true that many people will ask you to be the woman developer, to answer for all women. Well, that’s why I’m asking more women to stand up, to be role models - if we all step up, it will no longer just be me, and you, and that other one over there. There’ll be more of us, more differing voices, we’ll stand out less. But we have to stand up first. And in the meantime it’s us and our points of view they’re listening to. Wouldn’t you rather voice your opinion than have someone else speak on your behalf? Especially when very few people really can represent you, who you are and what you want.
What if I can’t answer the questions?
You’ll be surprised at what you do know, so people who present run into this less than you’d think, even if you’re just beginning,
but just in case here are some tips:
- Repeat the question, paraphrasing. Firstly, this ensures you’ve actually heard the question correctly. Secondly, it allows the whole audience to hear it, and thirdly, but most importantly, it buys you time to think.
- Be honest - say you don’t know, and move on. If you know somewhere that might have the answer, point the person to that resource. But a technical audience actually values the answer “I don’t know” more than you think. Especially the person who asked the question, it makes them feel really smart!
- If you don’t know, but you think the audience might know, throw it back to them. Either to the person who asked the question, if that feels appropriate (especially if this is one of those “look how smart I am” questions), or to the audience as a whole. In conferences in particular, there’s a good chance someone there knows the answer.
- If you’re genuinely terrified of all questions, say at the start of the presentation that you won’t take questions in the talk. Offer an alternative, like via Twitter or e-mail, if you can.
What can conference organisers do?
Specifically invite the people you want presenting
Don’t just wait for them to submit. If you want more women, more diversity, invite them. And invite them early…
Secure your women presenters early.
Recognise that there are relatively few women presenters on “the circuit”, and understand that everyone wants them to speak at their
conference. This rare breed, the female technical presenter, gets booked up well in advance. They’re probably as in-demand as your
keynote speakers, and can probably devote less time to appearing at conferences than those who have made it to keynote-standard (I’m
making a sweeping generalisation that your techy women have day-jobs as developers and your keynote speakers are either professional
presenters or at least can argue presenting as a critical part of their job).
So, you have a limited resource (experienced women presenters) that’s in high demand. You need to reach out directly to them, invite them, and secure them well in advance of your conference. Many big conferences, for example JavaOne and QCon, will invite speakers six months in advance. If you give women speakers a month’s notice before your conference or event, they simply are not going to have the space in their schedule at that late notice.
Showcase your diversity on your website
If you haven’t already heard of microaggressions,
go and read what that means before you get any further. There’s a very simple thing you
need to do with your website, whether you’ve opened for CFP or you’re trying to get attendees to register - make sure the photos on your
website show the type of diversity you want to encourage. Only yesterday I was looking at the website of a big conference,
who I know for a fact are working really hard to ensure diversity, not just with gender but race, age,
and where possible in less physically obvious dimensions. The conference is many months off, so the only photo they have on the website
is a background photo of the exhibition hall from some previous year, crammed full of attendees - white, male attendees,
as far as it’s possible to tell. It’s extremely subtle. You might not even notice, as the photo is behind the headers and text of the
site. But I noticed. And you can be sure the subconscious of every person who went to the website to either submit a proposal for a
talk, or is considering asking their employer to pay for the registration, also noticed. The conscious mind might be able to shrug it
off. But the subconscious of a non-white and/or non-male person notices and plants the subtle seed
of “this conference is not for me”.
So, conference and event organisers - if you want more women applying to speak at your conference, show more women on your website. If you want a more diverse audience, show more diverse faces. If you’ve invited your women presenters early and secured them early, show their photos on the site - this sends a strong message to other women that their talk proposals will be taken seriously.
Run warm up nights to try out new speakers
I know conference organisers get lots of submissions, and I know it’s hard to tell which are going to be good speakers,
especially if they’re new speakers or don’t have a video. If you’re genuine about improving the diversity of your speakers,
run free nights to a) promote your conference and b) try out new speakers. Probably a good idea to have a new speaker and a known
speaker to attract the crowd and give newbies a chance.
Don’t be so damn picky
- New speakers need to be encouraged. Find a way to see their content without just discarding an unknown name.
- Existing speakers might not have the luxury of creating new content. Many conferences want genuine practitioners, not just evangelists, but those people have day jobs and can’t be creating a new talk just for your conference.
Leave space for new speakers
…and don’t just have 7 slots for a pro speaker
Look at your swag
Not just guys t-shirts. One conference gave out cupcakes for example. But it doesn’t just have to be handbags and high-heeled shoes,
just take a quick look and see if your swag is generally useful for techies, or if it leans towards men only. Men only swag (men’s
t-shirts, bottle openers, subtle things like that) subliminally says “you don’t belong here” to the women.
Give feedback
You can’t tell every individual why they were rejected, but you could look at all the rejected submissions and give broad indications of
the type of CFPs that didn’t make it. Maybe write a blog post explaining which sorts of talks didn’t make it and why. This will help
speakers create content that better fits your conference.
Be specific about what you’re looking for
If you have tracks you’re finding content for, put them on the website/CFP, so people know what the topics are. If you have an
idea that you want 30% beginner material and 30% very advanced, make that clear too. Especially if you want only beginner or only
advanced. People will submit more appropriate talks.
Have a beginner’s track
…not just for the speakers, for the content too. Beginner speakers may be more comfortable presenting “Introduction to…” talks.
Having a beginners track, whether it’s for content or speakers, will make newbies feel more included.
What other things can we try?
User groups can grow talent
- Practice writing CFPs
- Help each other
- Presentation skills
- Lightning talks, book club, different meetup styles (like fishbowl)
- Run an open conference to encourage new speakers
Women’s user groups are instrumental
So here’s something interesting. I’m sceptical of all-women user groups as I feel it separates us from the communities we should be
contributing to. But women’s user groups can help us to integrate better. For example, Duchess France helped and encouraged its members
to submit talks to Devoxx, gave feedback on CFPs before they were submitted, and provided a safe place for the women to practice
presenting beforehand. I think this is exactly the sort of thing women’s user groups could be fantastic for.
Advice for budding speakers
- Just Do It
- The more you do it, the more comfortable you’ll be
- If you’re a speaker, it can make you feel less of an impostor at a conference - you’re not just a woman developer, you’re a speaker!
- Everyone’s afraid, it’s not just you
- Every developer wants to learn
- The audience is on your side
- Start Small (user groups)
- Be technical. But you don’t have to be super smart
- Bootstrapping is hard - you haven’t presented so you can’t get into conferences. Again, user groups can help with this.
- Pair. Ask a more experienced presenter if you can co-present with them.
- Ask for mentors
- Ask for feedback
- “I don’t know” is perfectly acceptable.
I appreciate there is so much more I could have covered, and many topics deserve more depth. But this is the brain dump from the Devoxx session, and maybe one day things will be expanded into their own topics.