- The seattle tech sector lives. There are few open get-togethers in Seattle for tech sector folks, despite the size of the industry here. It was telling how easy it was to get 150 people to sign up for this event, and it’s embarassing that no one had done it before (Kudos to Andru). A few people mentioned idea day, which I haven’t been to yet. Thanks to all the organizers and volunteers.
- High quality sessions. There wasn’t enough time: I missed good sessions. The mix was good: less tech-centric than the last FOO. I threw myself in the middle of things, and got involved in 3 sessions, but that meant I didn’t go to many others. Ario, Joe and I did one on leading software teams (we met through the event wiki), I did a solo on why smart people defend bad ideas and ran a UI critique session with Mr. Richard Stoakley Thanks to windowssecrets.com , teachtown.com and others for letting us critique their sites in front of a crowd.
- Show and tell of ideas . Everyone had something to show or talk about, and the informal vibe made it easy to share. I spent a half hour chatting with Andy Edmonds about browser design and software instrumentation. Learned about the Firefox Attention trust effort from him as well. I saw live demos of gada.be, Ruby on Rails, a choose your own adventure DVD and two good sessions on information overload and web annotations by Ario. Given the number of sessions it was easy to bail on anything that bored me.
- Left with a mental buzz. I heard so many different ideas and passionate people that my head spun for the next 24 hrs. It’s easy to forget how stimulating it is to meet new people who are passionate about what they’re doing.
- Wireless didn’t work. I felt bad for the folks who talked for 10 mintues at the start of the day for how they set up the wireless system (and how cool it was). After a few hours of everyone failing to get it to work, those guys were hard to find: it wasn’t their fault, as the building had less bandwith than they were told. It turned out ok: I was glad people had more reasons to close their laptops and talk to each other.
- Little incentive to stay overnight. The Sunday morning schedule was weak and there was a no alcohol rule: two strikes against staying. The building was huge which also hurt the stay overnight factor. Many folks I met left by 1am (myself included). I came prepared to stay over, but I couldn’t make a good argument for it.
- Some first time event mistakes . I used to run training events and I’m familiar with how hard it is to get it right. On the whole they did well. My notes: many had never been to a self-organizing event before and had no idea how to prepare or what to expect (Lots of “I would have brought X” or “I could have talked about Y”), the directions were confusing (even at the complex itself: there were no signs outside) , there was no phone number for people who got lost and the website didn’t help people hook up before the event (Something FOO did a good job of with photos of everyone up on the site and at the event itself).
- Post event value opportunities being missed. There was talk of capturing as many sessions as possible, but I have no way of knowing if that happened. The Seattlemind website and wiki hasn’t been updated since Friday. Everyone’s understandably exhausted come Sunday, but there’s time now to collect slides from all presenters, roll together lists of podcasts, etc. If nothing else it makes it easier for folks to prepare for Seattle Mindcamp 2.0 .
Suggestions to future Foo/Bar/Mind camp organizers:
- Have a “First time at camp?” FAQ . Make it easy for folks to understand exactly how to prepare and how different it is from regular confererences. Don’t make up the FAQ: ask people who just went to their first one what they were confused about and what they wish they’d known before they’d arrived (Don’t codle them with detals but get them over the hump). I’d write it if someone would use it.
- Encourage pre-event connections. Name tags are not as good as faces. When people sign up, ask for a URL for a photo and include it. Also, many sessions listed on the wiki didn’t happen: why? not sure. There was plenty of room late Sat and Sun morning. There was just no supported way to tell those people before they event I was interested in their topic. The wiki/website made it hard to dig up e-mail or contact info for other people.
- Have a single primary pre-event news and update feed. In the days before the event it was hard to find details on updates and changes. There was the seattlemind website blog, personal blogs of organizers, the main wiki page, the session_ideas page, and various other child wiki pages. Instead, make it easy to track news, requests and updates in one place to fuel the self-organizing process. This same primary feed should be the way to get post event news (podcasts, slides, etc.) as well.