Monday, April 26, 2010

5 Tips for Submitting a DevLearn 2010 Session Proposal

The DEADLINE for submitting a proposal for DevLearn10 is this Friday.  Late submissions are a huge bummer.  Some times the late proposals are AWESOME, but because they were late there is no place left on program to put them.  So don't be THAT guy/gal!

Basic Submission tips:
1) Be clear and convincing.  1 or 2 sentences just doesn't cut it.  Give me the details!  There is a reason why the form is designed the way it is.  Short and unclear is just as bad as long and boring.  Sell me.  Tell me why you (your project) ROCK!

2) Titles should be clear AND creative.  But most importantly no more than 8 words.  If you can't tell us what the gist is in 8 words or less, then you should rethink the topic.  The rest is handled in #1 (see above)

3) Co-presenters need a reason to be there (and yes, co-presenters pay to attend).  Tell me why.  A good example of a pairing is having both the project manager and the technical developer.

There is a lot more too it, but I hope that helps a little.  I'm hoping our past presenters will add some tips in the comments below...wink, wink ;-)

Advanced Submission tips:

1) Record a YouTube video so I can see you and hear about the session topic you are proposing.  Once you post it to YouTube then just past the link into one of the description fields on the submission form.

2) Post your slides to - Even if the presentation is not completely designed, go ahead and use the same tool to propose as you would to present.

Its not rocket surgery! Put yourself in my shoes.  Write a proposal that YOU would want to read and make sure the content is something YOU would want to attend.

Hey veteran DevLearn speakers!  Comment your favorite tips about presenting at DevLearn.  Thanks!  Without y'all we couldn't make DevLearn happen.  You ROCK!

mLearnCon - Mobile Learning Conference and Expo- June - San Diego, CA DevLearn 2010 Conference and Expo - November - San Francisco, CA
Post a Comment