DrupalCon, We Have a Problem

As a community that has experienced rapid growth in a very short time, we’ve very quickly gone from conferences that consisted of a couple dozen people getting together for a few beers to international events that attract thousands of people from around the world. As DrupalCons have grown, not only have their audiences become more diverse, but their reasons for attending have changed as well.

DrupalCon is no longer just a gathering for the core community, it’s also a place where new people come to learn more about Drupal from the best and brightest minds in the community. While these people aren’t necessarily as passionate about Drupal as the rest of us, they are nonetheless investing a lot of time and energy to attend DrupalCon, and when they end up in a session with a speaker who hasn’t spent enough time preparing the presentation, it reflects poorly not only on the speaker, but also on Drupal and the community as a whole.

For the last few DrupalCons, we’ve been asking attendees to not only fill out a survey rating their DrupalCon experience, but also provide ratings and comments on individual sessions. I’ve spent the last few weeks looking through the information we’ve collected, and the results confirm what many of us in the community have suspected for some time: while many DrupalCon sessions are great, there are also many sub-par sessions by speakers who are disorganized and unprepared. Here’s a few representative survey comments from the last couple of DrupalCon surveys:

"Get better speakers. Too many people did not plan their presentations, so I didn't get much out of it. Have them be more specific in advance about what they'll be covering."

"Many speakers seemed to have no public speaking experience at all. They rushed through presentations in a monotone, glossed over code when I wanted detailed examination of code, and generally just didn't explain themselves very well."

"I travelled from Singapore on my own cost. Some of the speakers adopted the attitude that since its open source they didn't need to prepare and present in an organized, focussed [sic] and clear fashion. That was a disappointment."

What’s even worse is that these kinds of comments are not just restricted to a few sessions; even some of the best public speakers in the Drupal community are getting dinged for insufficient preparation and disorganized presentations. This is clearly a widespread problem.

But I’m a Web Developer, not a Talk Show Host!

One easy way to solve this problem would simply be to only select presenters who are known to be good public speakers. But doing that would go against many of the values that Drupal and DrupalCon stand for; first and foremost that this is a community where anyone and everyone can participate. Futhermore, one of the things that sets DrupalCon apart from other technology conferences is the passion that our core community members have for sharing their knowledge with others, and many who of those who are widely recognized as some of the best and brightest in the community are not necessarily some of its best public speakers.

So we needed to find a solution that both encourages presenters who are already good speakers as well as provides support for those who are less-experienced or less-polished presenters who have knowledge and insights to share.

The Plan

At the beginning of this year, shortly after Chicago was formally selected as the venue for the North American DrupalCon in 2011, the organizing committee sat down to talk about how session selection and programming would be handled at DrupalCon Chicago. Our conversation was informed by numerous conversations we’d had with other people both in and out of the community, a frank analysis of what worked and didn’t work at past DrupalCons, and our experiences speaking at other large technology conferences.

Speaker co-chairs Matt Farina (mfer) and Greg Dunlap (heyrocker) then went back and created a “Programming Manifesto” that outlined the overall principles that would guide our process:

  • Being more transparent about the process and principles behind session selection and voting;
  • Providing better tools for attendees to evaluate in advance what sessions they should go to;
  • Choosing sessions by a publicly announced combination of curation and voting (i.e., not all sessions will be subject to public vote, which means that lesser-known speakers won't have to compete against the "big names" for votes);
  • Limiting the number of sessions that any single individual can participate in, so that they can focus on making sure their presentations are of the highest quality possible;
  • Taking into account attendee feedback and ratings from past DrupalCons when making speaker selections;
  • Making sure that less experienced or polished presenters receive mentorship and guidance earlier in the process, and encouraging them to team up with more experienced presenters for panel discussions
    Communicating better with attendees about which sessions are appropriate for different audiences (evaluators, developers, designers, etc.);
  • Doing our best to ensure that introductory sessions are well-polished and presented by people with a proven track record, as this is where we make our first impression to people new to the community
  • Recognizing that there are different expectations for sessions focused at existing Drupal community members than there are for sessions targeted at new or more casual attendees, and doing a better job of identifying which is which.

These principles, the session selection process, and additional information are explained in more detail in the Speaker FAQ that will be shared with all prospective speakers for DrupalCon Chicago. These principles have also informed everything from our venue plan to our marketing strategy for the conference: while there are many reasons to attend DrupalCon, we believe that quality content is one of the most important.

Making DrupalCon Both Bigger and Smaller

One piece of feedback that we’ve heard over and over again from recent DrupalCons is that the conferences have gotten “too big”, and that we’re losing the intimate feel that characterized earlier community gatherings. Given that Chicago may well draw more attendees than any previous DrupalCon, we’re keenly aware of this issue, and are working on ways to make sure that the the conference is fulfilling not just for a mass audience, but also for veteran community members.

One of the things that we’re working on right now is a special “Core Conversations” track where Drupal core contributors and community members can meet for more conversational sessions about the future of Drupal and its community, much as earlier DrupalCons where places where interested and engaged individuals could gather to share ideas and insights. Presentations in this track would be finalized much close to the date of the conference than those in the “traditional” session tracks.

In addition to these “Core Conversations”, DrupalCon Chicago will also feature its own exhibit hall Day Stage, which will be the venue for exclusive content such as lightning talks, Drupal author presentations, case studies, sponsor demonstrations, and other unique and entertaining programming that doesn’t fit neatly into the regular session schedule.

Being Prepared

One of the major common themes that we’ve seen in negative speaker comments from past DrupalCons is not that the speakers themselves were bad, it was that they were unprepared, or their presentations weren’t well organized.

We believe that this issue can be alleviated greatly with just a few simple steps. First, we will be finalizing the session schedule for DrupalCon Chicago much earlier than in past years; this not only helps out prospective attendees who would like to know what kind of sessions will be offered before they purchase their tickets, it also gives speakers more time to prepare their sessions.

Second, DrupalCon Chicago is committed to providing a high level of support for its speakers. Our track chairs will work with presenters in the months and weeks leading up to the conference to make sure their session preparations are on track and that the session content matches the description in the conference program. We will be available to answer any questions, provide any assistance, or connect speakers with other community members who can help out.

We’ll also have on-site resources for speakers to make sure that they have everything they need to give the best presentation possible. One of these will be the Green Room, a special speakers-only room that provides a place for presenters to go over their slides and make any final preparations before the start of their session. The Green Room will be stocked with refreshments and is located adjacent to the restrooms. We’ll be asking speakers to check into the Green Room a half-hour before their session starts to make sure they’re on-site, on-time, and have everything they need to hit the ground running.

Another way to ensure speakers can focus on being prepared is by making sure they’re not overwhelmed with having too many sessions to present. Limiting the number of regular sessions that speakers can participate in also has the advantage of enabling other, less well-known members of the community to have an opportunity to present at DrupalCon. Speakers who do want to do more will have the opportunity to participate in Core Conversations, the Day Stage, BoFs and more. Our goal is to provide more ways for people to participate in DrupalCon than ever before.

Where You Come In

These are just a few of the things that we’re doing to make sure that DrupalCon Chicago is a conference that works for everyone, regardless of whether they’ve been involved with Drupal since the beginning, or just found out about it last week. If you have ideas that you’d like to share with us, we encourage you to share them in the comments below or via the contact form on the DrupalCon Chicago website. While we won’t be able to take advantage of every good idea that comes along, we want to make sure that the community has a voice in the process to help make make Chicago the best DrupalCon yet!

Comments

rszrama’s picture

Great news, George. I look forward to seeing / experiencing the fruit of all this work in Chicago. : )

And I must confess... at first blush the title of your post made me think it was about improving the DrupalCon website process. Always thinking of programs made of code, not of people. : P

chx’s picture

I am mostly baffled by the impossibility to speak to people who range from someone who never even installed to Drupal before to my fellow core developers who can't go a day without drinking some of the Kool-Aid :)

Specifying a track to be "advanced" should be very clearly communicated: please do not attend if you are not one, you will discomfort the presenter by totally inappropriate questions and you won't understand much.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

Chris Sloan’s picture

Have speakers submit their presentation 2 weeks prior to the event, if they're not ready scratch their talk or have someone else in the community cover the topic; there are more than enough capable Drupalers now that we don't need 1 person doing 3+ sessions.

If you want to start to unify the message and have a more professional feel then you're going to have to require some changes. I've been to enough events now to see the "Drupal-Good-Ole-Boys-Club" and frankly some of those guys, while great Drupal minds, are horrible presenters but keep getting a chance to fail.

heather’s picture

OK... this is a rant here, but I enjoyed this post and it got me thinking!

My friend recently attended an industry conference (i shall give no further details). He was telling me about the presentations from really big companies, like Microsoft, Nintendo. The MS guy was apparently really good, but other presenters were horrible. Disney? Nintendo? Monotone, zippy animated words on slides, over use of jargon, "synergy". Attendees were bored.

Fact is, presentations require much preparation and the skills require a lot of practice. And those skills are quite rare. People who present well are those who practice their presentations 20x, they present it several times... they are interested in public speaking. Did you know Jen Lampton is a member of Toastmasters? It's no coincidence that she's so good at presenting and training.

But not everyone who presents at Drupal Con, and has something to share, is interested in that level of performance.

The difference between DrupalCon and my friend's work conference is passion. If you're passionate about the content, you can be forgiving on style. I think attendees are passionate at DrupalCon, and eager to learn.

I wonder if the problem is that we take a lecture style approach to coding presentations? Looking at slides of code is not going to stick in any one's heads. You can transfer big concepts and ideas, but walking someone through code, you're gonna lose 'em - well, I can't remember how many tweets I saw about complaints of slides of code. A few, maybe more.

There are alternatives. If something can be done hands-on, do it. You don't have to cover *everything* (what you cover isn't what people remember anyway). Break up the 45 minutes into a short demo, then have people download code, or try something out. Or break into groups, discussions, reporting back, etc. What's the "big idea", what's the message? Is there another way for people to experience it in addition to you talking about it?

We can re-think what these sessions are about, and how we conduct them. Days full of presentations are going to wash over people.

BoFs are pained as well. I've sat in BoFs where we spent 30 of 40 minutes introducing ourselves and didn't "get" anywhere. Open Space Technology is a great way to get people's ideas out, build a collaborative agenda and have meaningful conversations and outcomes. These are simple techniques.

I've had good success with these kinds of techniques. I'd be glad to have a BoF on "Open Space Technology" - like a BoF about BoFs. I suggested the same to Moshe at DC San Fran. The space at DC Copenhagen wasn't conducive- but maybe it would work in Chicago?

Steven_NC’s picture

Every organization with significant growth reaches this same situation. It is a natural, though painful step. As someone who frequently speaks at conferences (in another industry), I find that my presentation get better over time. Even the subject matter experts need constructive feedback. Too fast? Too basic? Too broad based?

Luckily, the Drupal Community has a method to help presenters and improve the DrupalCon experience - Drupalcamps.

To present at DrupalCon, one must have presented the subject at a Drupalcamp.

This gives the presenter at least one feedback cycle on their subject. Every presenter surely feels they could do better upon leaving the podium. It is very difficult to evaluate yourself until you have a live audience.

Many Drupalcamps have recorded sessions. This is a great way for speakers to self-critique. With the experience at a smaller venue, the presenters can make changes and add polish for the next. It is also a way for DrupalCon coordinators to evaluate proposed sessions.