« Talks, Trips, and More | Main| Racism... Unfortunately Alive and Well »

Lotusphere: Sessions, Selections, Rejections, and Responses...

QuickImage   
Category  
Bookmark : del.icio.us  Technorati  Digg This  Add To Furl  Add To YahooMyWeb  Add To Reddit  Add To NewsVine 

I was planning on posting on a couple of other things today, but based on recent events, I felt it more important to post this instead.

I have been extremely fortunate to be involved with Lotusphere since 1996; I started as an attendee, expanded as a shirt co-creator (C.U.L.T. shirt), I then became a speaker, and I reached my favorite involvement of all, as a track consultant and manager for the Best Practices track. Along the way I watched the Best Practices track grow from an "experiment" to one of the most popular tracks at Lotusphere, each and every year. A side affect of being a very popular track is that it gets more and more submissions each and every year, while the session count has remained stable at around 30 or so sessions each year.

This year was no different; in fact the Best Practices track set another record for submissions - there were over 300 sessions submitted to the Best Practices track alone! There were more Best Practices track submissions than App Dev OR Infrastructure - tracks that have many more session slots than Best Practices. This means that we were able to only select one session for every TEN submissions.

As I have explained in the past, our selection process for the Best Practices track is intended to keep the content fresh and interesting. Sometimes this means new presenters, sometimes it means bringing back presenters who have exhibited a dedication to providing new and interesting materials each year.

I know I speak for the entire content team when I say that we LOVE the passion and dedication the Lotus community has shown for Lotusphere. This is true even moreso for Mac and me, in our roles as the two people responsible for the Best Practices track - the track that is "for the community, by the community". And because of this dedication and passion, I can understand that some people who weren't chosen would be upset, and would want to vent. Hell, when I wasn't chosen in the "early days" I know I was really disappointed and depressed. But now that I've been "on the other side", I understand how hard it is to actually put together a track. Let me explain.

In those 300-plus sessions we received, I can honestly say that about HALF of those sessions were worthy of being selected. The problem is that, as I explained earlier, Mac and I have only 30 session slots, give or take, for presenting a good representation of these excellent 150-or-so session submissions. That means that we are unable to choose about 120 sessions that are otherwise exceptional. And let me tell you, it was HARD for us to make these decisions.

So, I'd like to ask for your understanding in how we've put the Best Practices track together. I can assure you that every session was carefully reviewed, and we have done the best we could in creating this track for you, the Lotus community.

If, however, you still would like to discuss this, please feel free to contact me. Mac is out on maternity (ok "daddy") leave, so I will have to speak for both of us in his stead. You can drop me an email (rock AT teamstudio DOT com), or ping me on IM. I would be happy to discuss this with you.

Take care, and I can't wait to see all of you at Lotusphere 2009!

Rock

Comments

1 - I know I had some items in BP track among others, perhaps some don't belong in BP but then the limited scope of choices makes it hard where to put something.
Like admin items, really doesn't belong in BP per se, but there is no better place.

Any thoughts on this for next year?

2 - I do not envy any of you track managers the difficult job of parsing through what must be a huge pile of great options. Maybe one of these days the BP track will expand (Downtown Disney, anyone? We could take over the Irish Pub...think about it...)

See you in Orlando!

-Rob

3 - My submission { Link } was rejected, but I am not upset. I realize that there are many better submissions and more experience speakers.
I will make another attempt next year. Hope to see you in Orlando, Rocky!

4 - Rocky: If you don't want to/can't answer, I will understand. I was just wondering how much help the BP IdeaSpace on IdeaJam was for your selection process. Did it help to see community involvement? Is it a worthy endeavor? Would you do it again?

Thanks.

5 - Thanks, Karl. And thanks for submitting.

See you at Lotusphere! Emoticon

Rock

6 - I don't even want to think of the Herculean chore the track managers had to undertake... so Rocky - better you than me, bro!

I haven't paid too much attention to the community today, but are you getting many "sour grapes" postings, comments, IMs, et al?

If so, sorry to hear that - as that's not very much like our community...

7 - @Gregg (5) - IdeaJam was a great additional datapoint for us to consider when making our choices. We did consult it on occasion during the deliberation process, as an additional data point. So, yes, I think it was a good idea; and yes, I think we should use it again.

@Keith (6) - I do understand your comment about "limited scope of choices makes it hard where to put something" - but I want to make it clear that you can submit to any track; and quite often a handful of non-IBM speakers are chosen for the other tracks. So, if your session just fits better into another track rather than BP, then you should put it there.

If you want to submit to another track, here are some suggestions. Now, this is from MY OWN personal observations; I cannot speak for any other track team member. From what I've seen, the sessions that are chosen most for other tracks fill some gap that would otherwise go unfilled in those tracks. For instance, I know that some "foundation-level" LotusScript sessions have been selected for the App Dev track, because there aren't many LotusScript-type IBMers that come to Lotusphere. So, think of that narrow gap between a Jumpstart session and some advanced session or some BP session, and you are thinking in the right way.

As for Admin sessions... I'm kinda shocked that you would say that about Admin sessions. Of course admin Best Practices sessions exist! The last few years we have added more and more Admin sessions to the Best Practices track because of their popularity! In fact, the last couple of years there has been about a 50-50 division between App Dev and Admin (not counting the other, miscellaneous sessions we add in there). So, this means two things: 1) we are definitely showcasing the Admin content, and 2) the competition for Admin content is as strong, if not stronger than, the App Dev content.

I hope this helps - not only you, but anyone else who is reading this.

Cheers!

Rock

8 - Rock, thanks for input and it's not that there are no Admin sessions, just that it would be nice if there was a track solely for admin sessions if what I would like to see.
That is not taking away anything from the View's Admin annuals but most people get to one event, Lotusphere, so it should do more. Just my 2 cents.
Or if there were defined tracks by product, Quickr, Sametime and Connections could easily fill an entire track.
I would be interested if there is a % break down by admins, devs, execs, others, misc. of attendees to understand the decisions better.

9 - Rock - I don't envy those who have to make the track selections either!! And I want to say thanks to all and that I'm honored to be presenting in the BP track this year! Here's to another great year!!

Meet Rocky

Rock - February 2010
Rocky Oliver
If you see me at a conference, please stop me and say hi!

Calendar

Search

Categories

Proudly Employed By

Wofkflow Studios

Thawte Notary

Thawte Web of Trust Notary

LOTUS GEEK gear

Social Networking


Add to Technorati Favorites

View Rocky Oliver's profile on LinkedIn

Rocky  Oliver

LotusGeek Blog Roll

Why display a blog roll when Planet Lotus does it so much better?

Dilbert

Buy my book!

Blog Buttons

Atheist - Unitarian - Humanist

Poker Players Alliance