in Uncategorized

Programming Conferences

This morning on Twitter, a conversation flared up around IA Summit 2014, because they received over 400 submissions for 50 spots, which means many many people, even those whose sessions were reviewed highly, were rejected. (I was rejected as well, but I half-assed my proposal.)

FOR STARTERS, let me say nothing but praise and thanks to Aaron Irizarry, Johanna Kollmann, and Abby Covert, the IA Summit chairs. They are friends and colleagues, and I know they are working tirelessly to do the best for the IA and UX communities.

OK, back to the conversation at hand. Jared Spool raised his concerns that with so many submissions for so few spots, there’s a lot of “wasted effort.” I share that concern (though I recognize my lackadaisical effort was not wasted), because a lot of people, and thus good people, likely feel burned by the work they put into a submission, and would be less inclined to submit in later years. So while this year’s summit benefits from being able to draw from such contribution, how will later summits fare?

Professional associations have it kind of tough. When I was at Adaptive Path, I programmed MX and UX Week events, all based on what I wanted to see (and suggestions from colleagues). Professional associations have a responsibility to their membership, and tend towards the “call for papers/proposals” process. The benefit of this is that you can get interesting new voices and ideas, and you give the membership a voice it might not otherwise have. The drawback is that your beholden to submissions, and it can make it hard to craft a compelling event.

Which events are better, invited/curated or submitted? They both can work, though, given that I’ve curated, I lean towards that style. I like it when there’s an editorial point of view that connects the presentations.

However, I’ve had transformative experiences at the IA Summit, and as a conference organizer, always sought out rising stars there. There’s a randomness/unexpectedness that often delivers crap, but can yield amazing stuff.

The IA Summit faces a challenge in terms of not discouraging great submissions because potential contributors feel the effort isn’t worth the likely rejection. One solution is to raise the bar on what it takes to submit, to weed out those (like me, this time around) who are half-assing it, and cluttering things up. Another might be to more aggressively ‘track’ submissions into categories, to make sure there’s a good spread of topics (and make clear to folks that we don’t need yet another submission on agile/lean UX).

Separately, I heard complaints about panels. There are always complaints about panels. Done wrong, panels are a lazy way to fill a conference slot. And many panels suck, because it’s simply 4-5 short presentations. However, I still have vivid memories of one of the IA Summit’s best sessions, a panel in 2003 on “Wayfinding and Navigation in digital spaces” which was legitimately mind-expanding. So, don’t count panels out. Just structure them so they’re stimulating.