How to Organize a Tech Conference
A collection of obvious and not-so-obvious details to consider when organizing a technology conference
Join the DZone community and get the full member experience.Join For Free
running a conference is hard work, and lots of things need to come together in just the right way to make it a great experience for everyone. this blog post is a collection of the most important things i’ve seen conference organizers get wrong (with the best intentions). it’s not comprehensive, but i hope it will help point out “low-hanging fruit” for interested people. hopefully you’ll be able to avoid some of the mistakes as a result.
know your audiences
i organized my first tech conference in 2008 and i didn’t do a great job. i focused almost exclusively on the experience of the attendees, and i didn’t understand the broader picture. fortunately others helped and it wasn’t a disaster. i learned a lot from them.
there are several audiences at a conference, not a single one.
- attendees typically say they come for great content, fun, networking, and inspiration.
- speakers usually speak for their own interests, a company’s, or altruistically.
- vendors or sponsors usually want to attract relevant potential buyers.
- organizers often have an interest in bringing the attendees and sponsors together. it might be a company that makes a business from running conferences, as with o’reilly; or it could be a group of people interested in promoting a community or technology, as with gophercon and the go language.
it seems obvious to state these things, but so often conference organizers ignore the needs of one of the audiences. don’t forget, too, that there are others such as the local community (e.g. the restaurants and hotels nearby).
a well-balanced conference is a conscious choice to mix the interests and needs of all of the audiences as much as possible.
food and drink
good food and drink (coffee, alcoholic beverages) at a conference is extremely important. without these, the conference gets destroyed and reconvened several times a day. people have to leave and try to find some food, wait in lines, walk around in the rain, get lost, come back late and miss the talks they wanted to see (thus disrupting the talks when they enter late)…
feed your attendees unless you’re right in the middle of a food paradise. you’ll reap the rewards and so will they. get sponsors to help and it’ll be a virtuous circle.
what you feed them is also very important. i’m gluten sensitive and i can’t tell you how many times i’ve walked down a buffet line, only to see literally nothing i can eat. the menu is things like bread, pasta, sandwiches, couscous salad and pizza. not kidding—gluten (and high carbs/starches) in every single dish. and what about people with common allergies such as nuts? salads with nuts in them, or cheese sprinkled instead of being in a separate dish… these things aren’t hard to fix. it’s easy to accommodate most peoples’ needs. just ask for help from someone whose diet isn’t like yours; find a gluten-sensitive vegetarian for example. there are lots of them.
planning in advance
many conferences don’t plan far enough in advance. not planning and announcing things leads to a lot of problems. you have to consider your audiences, again:
- sponsors are committing to other events and their calendars are filling up.
- speakers are too!
- all of the attendees, sponsors, and speakers are not only committing to other things, but may have challenges getting coverage for family needs (babysitter help while they’re away), booking travel at reasonable rates, and the like.
if you wait longer than other shows to open and announce your call for proposals, in particular, you won’t get proposals because other shows will already have accepted the speakers you want. this typically means at least 6 months, often 8 months. back out the schedule and see where you need to plan; it varies depending on the type of event, but you want a good amount of time to sell tickets (and if there’s any travel involved you need to do that much earlier), a chunk of time for going through various ticket pricing increases such as early-bird and discount; time for a committee and community to promote the agenda you’ve chosen; time for the committee to choose the speakers and talks; time for the talks to be submitted; time for the word to get out—again, you need at least 6 months as a bare minimum for most events.
i’ve had to miss a lot of great conferences because the organizers didn’t plan and announce far enough in advance.
the cfp is particularly important. it needs to be announced and publicized repeatedly. it’s a big effort. it also needs to be highly visible on the conference website. i’ve seen conferences with cfps inadvertently accessible only from links in emails and tweets, not directly linked from the website. the website needs to promote whatever’s stage-appropriate as time passes: the cfp, registration, and then the schedule/agenda.
many conferences i know don’t do a good enough job asking last year’s speakers to speak again at future events. i’ve gotten emails asking me why i didn’t propose talks for a show where i was a speaker in previous years, implying that i’d shunned the conference, when the reality is the conference ignored me . i heard nothing about the conference or cfp until the accusatory email. this should not be hard; use mailchimp or similar to just create a simple email list.
a very important part of announcement and promotion is to use a guaranteed delivery format such as email, not a maybe-you-notice-it social media channel. i have known conferences that rely on twitter. they didn’t realize that a significant part of their audience was not watching their twitter account. they assumed their speakers, in particular, were watching them intently—when the reality is the speakers were leading lives doing other things. i’ve gotten blank stares at times when i remarked on this being the reason i missed things. email is key. twitter is auxiliary. again, build email lists in mailchimp and keep records in spreadsheets, don’t wing it or do it ad-hoc. otherwise you will miss important things and important people, and the result will be hurt feelings and burned bridges.
if you can, announce the next year’s date and venue during each show. many people and companies really do need to plan a full year in advance.
speaker selection, acceptance, and announcement
you need to treat speakers respectfully. if you haven’t been in their shoes, it is easy to mess this up badly. here is a sample of the ways conferences have inadvertently treated me badly as a speaker:
- burdensome processes that ask me to jump through hoops
- taking too long to make a decision
- failing to confirm acceptance or rejection with me
- publishing and promoting my talk before getting my acceptance
- accepting my talk publicly, e.g. on twitter, instead of privately
the worst speaker management sin an organizer can commit, in my opinion, is promoting me as a speaker without asking me first. i’ve had this happen several times when i had already made conflicting plans because the conference didn’t plan and announce early enough. then it looks like i am the jerk for backing out. not cool.
by the way, the choice of whether to pay speakers (or just reimburse them) is highly dependent on many factors, so i don’t think any universal policy is appropriate for me to recommend.
i am a big fan of single-track conferences. examples are monitorama and gophercon. the temptation to cram more content in by multi-tracking is strong and i understand the pressures. organizers who resist this end up with the highest quality conferences i’ve ever participated in.
i understand that big trade shows are a different matter and i’ve organized those too. that’s fine, those are necessary. but if you want to respect speakers and attendees and really achieve a goal of community building and education, single-track is the way to do it. there is a way to work sponsorship into this, by the way, although naturally such a conference is less focused on sponsors. monitorama does a great job of this.
diversity and safety
have a mission statement. everything changes when you do. it doesn’t need to be public. just know why you’re doing what you’re doing.
you must have and enforce a code of conduct. don’t invent one, just copy one from a conference that does it well and offers theirs for reuse. if you don’t know what i’m talking about you really need to do more research on this yourself. it’s beyond the scope of this post.
beyond this, having a diverse committee will produce a much better conference. you’ll avoid all kinds of problems that come from monocultures (such as a gluten-only menu). these problems are easily avoided; it’s a really simple thing to just get some diversity onto the committee.
a mission statement and a diverse committee should take care of all the other things you will care about for your specific event (such as outreach to and inclusion of a diverse audience and roster of speakers).
give sponsors what they pay for
sponsors/vendors/exhibitors do not want to ruin your conference, they want to improve it. if you have not been one, you might not understand their needs, and again you might make simple mistakes that are literally the difference between them getting their money’s worth or you losing next year’s sponsorship goodwill. here are some simple mistakes i’ve seen that wreck things for sponsors:
- failing to print name and affiliation (company) in large type on badges. sponsors at a booth are very busy and they want to save their staff’s time as well as treat the booth visitors well. the name and company need to be visible from a few paces away. you’d be surprised how many people come to a conference with the express purpose of cruising the expo hall and trying to prey on the sponsors (e.g. trying to sell them cloud hosting). this gets in the way of what the sponsors are there for. name badges solve a lot of this: you can ask people to move along so you can spend time with the right people.
- failing to print a qr or other scannable code on a badge for sponsors to efficiently take a record that follow up is needed. this is not evil. it’s time efficiency. people who have no interest in being scanned will not present their badges for scanning. sponsors who are savvy are only scanning badges when there’s a good conversation that results in a follow-up request anyway.
- not including sponsors in the show. a classic mistake is holding a reception or open bar outside of the booth area. shows that lay out the booth area so that lunch, coffee, and reception traffic flows through it are doing everyone a favor. many attendees also want to browse the exhibit hall but can’t if they have conflicting needs (i need to go get my coffee and get back to another session, i can’t make time to go out of my way for the expo!)
- interfering with conversations in the booth area. no loud music in the expo hall! if you have music or a dj, keep it background . sponsors don’t want to have to lean into people’s faces and yell to be heard. at a recent conference i was literally wiping spit from my face as people at the booth asked me to demonstrate vividcortex, and repeated requests to turn it down were not respected over the course of several days. this one’s a personal peeve for me, as people who know me can attest.
conferences organized by people who’ve been exhibitors are usually easy to tell from those that are just organized by people who’ve spoken/attended. if sponsors and exhibit areas are afterthoughts it’s a waste of time and money for sponsors. again, including a diversity of viewpoints on a committee helps avoid simple mistakes like this.
to give you a sense of how important this is, i do reference checks on every single conference we decide to sponsor at vividcortex. i will look at last year’s event and see who sponsored, then call or email them and ask if they had a good experience. i also regularly give feedback to other companies, so i’m not the only one who does this. a lot of conferences that get rave reviews from attendees (best tech conference i’ve seen in years!) are a waste of time for sponsors.
good advice is to think of how to put talks on one side, an expo hall in the middle, and food and drink either intermingled with or on the other side of the expo hall. it usually can be done. few things are more frustrating to a sponsor than flying across an ocean, setting up a booth, and sitting at the booth alone for the evening reception/party while all the drinking and talking is happening two rooms over.
depending on the type of conference, it might be appropriate to help publicize the sponsor’s participation. this can be as simple as tweeting about the sponsor (or sponsored talks), inclusion in newsletters, press releases, all the way up to dedicated publicity campaigns. it can definitely be overdone, however. one cloud event is unlike anything i’ve ever seen. they are obviously hiring armies of social media spam accounts, because there have been thousands of tweets like the following (redacted to avoid naming names):
that’s definitely not the way to do it.
be nice to the organizers
organizing a conference is a stressful job. there are so many potholes you can step in. some have serious consequences, such as using paypal to accept payment and having all your funds frozen. that kind of thing can destroy an event (or even an organizer’s personal finances). and a lot of stuff has to be done by the seat of your pants or at the last minute, unless you’re a pro and have it down to a set of checklists.
as such, if you’re a sponsor, attendee, or speaker, please try to be nice to the organizers. they’re doing their best. it’s much harder than you think it is to run a conference. (it’s also way more expensive.)
lots of other things
there are tons of other things that can go wrong.
- bad wifi
- bad a/v
- trouble with vendors, unions, and logistics
- and so on
however, these are largely things that most conference organizers are aware of, in my experience. they may do a good job or not, but they’re not ignorant of it. in this post i’ve tried to focus on things that conferences seem to get wrong repeatedly because they’re non-obvious mistakes.
feedback is welcome!
Published at DZone with permission of B Jones, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.