Tips for Unconference newbies

This post was renamed from ‘Tips for LocalGovCamp newbies‘ in April 2012, to make it more easily findable

I’m delighted to be going to LocalGovCamp on Saturday; my second event of that title and one of many unconferences I’ve attended in recent years. I hope to see you there.

Coral Musgrove asked me, on Twitter, for advice for unconference newbies.

I’ve come up with the following, which apply equally to any unconference:

  • Don’t expect to be able to go to every session. Sessions are run in parallel, and though a few may be repeated, most aren’t. So if you want to go to two that are happening at the same time, buddy up with someone with the same desire, and agree to go to one each then share your learning. Also…
  • Follow the event’s tag/ hashtag (e.g. #LocalGovCamp) on Twitter, , on SlideShare and on Delicious [Update: Delicious became awful when it relaunched, I now use Pinboard]. (The same applies if you don’t have a ticket for the event — better luck next time!) The sessions you couldn’t attend (and those you did) will most likely be blogged about, by the presenter or attendees. Which leads to…
  • Be prepared to blog about the event yourself, in the following day or two and…
  • If you can, tweet about the event while it happens, and at the same time…
  • Ask questions. Unconference sessions are conversations, not lectures. And if you can…
  • Speak about your own experiences and knowledge, chip in, and share what you have. Unconferences (unlike most traditional conferences) are for sharing.
  • Evangelise about the event when you get back to work…
  • Get your colleagues, and bosses, to read the most relevant blog posts.
  • Find about similar events near to you. If there are none…
  • Think about running your own unconference, or a smaller event, or even a social media surgery. Others will help you!

But most of all have fun! You’re probably attending the unconference in your own time; and it’s a social event as much as it is about work.

Please add any other tips in the comments, below.

14 thoughts on “Tips for Unconference newbies

  1. Carl Haggerty

    Excellent advice.

    I’d also add, try and include your twitter alias on your badge or sticker, this will help people connect with you and know who you are…

    Now bring on the curry…

    Reply
    1. sue waller

      really looking forward the event but i’m a newbie (@kpsol), does anyone know the dresscode? I’m not usually paranoid about things like this but i don’t want to be standing out for the wrong reasons! i’ll come in a suit but would be nicer to be smart casual since i’m on the 6.05am train from Liverpool! just trying to strike the balance between professionalism and comfort!

      Reply
      1. Andy Mabbett Post author

        Hi Sue,

        For clarity, you’re taking about UKGovCamp. Like most unconferences, it’s pretty relaxed; smart casual or jeans will be fine. More importantly, being an unconference, attendees will be more interested in what people have to say, than what they’re wearing; and nobody should be judged.

        Reply
  2. Pingback: Links of the week – summer blogs « ivry twr

  3. James Cattell

    Just tweeted: –

    Interesting chat @londonhackspace last night. I pitched @pigsonthewing’s #unconference tips.

    I mentioned some other advice, which I think is right: –
    People in a session, are the right people to be there (correct?)
    If a sessions not your bag, baby, then vote with your feet
    Sales pitches are ok, but please keep them short & sweet
    Respect each other, e.g. let your colleagues finish speaking
    Facilitate, don’t dictate
    Agree to disagree

    Reply
  4. Pingback: An Unconference For Techy Commsy Churchy Stuff | Jon's Blog

  5. Pingback: Hyper WM the Third is here… | HyperlocalWM

  6. Pingback: Tips for Unconference newbies (by Andy Mabbett, aka @pigsonthewing) « Health Camp West Midlands

  7. Pingback: First time at an Unconference? | UKGovcamp

  8. Pingback: About VCSSCamp Nine

Leave a Reply

Your email address will not be published. Required fields are marked *


e.g. 0000-0002-7299-680X