Organisation notes

Berlin guidelines

So Hack&Tell is a format which seems to adapt a bit to the regional flavor but there are some core values that should not be changed. Here's how I run it:

  1. Present a hack and the tech behind it, not pitch your startup. (If your new startup does something cool please DEMO the sweet stuff and talk about the tech behind it.)

  2. DEMO & explain, don't do a PowerPoint show. (I usually limit the slides to 1).

  3. Make the event hacker friendly. Feel free to cut off any suits trying to hijack your event with business or hiring talk.

  4. To make the event more useful I created the flea market session 10min before the pizza break. People can come to the microphone and talk 2 sentences about a new job, request project help or announce an event. This is a good basis for the conversations in the break.

  5. If you decide to let the event be sponsored (pizza, drinks etc) make sure the sponsor knows what to expect. I tell them in the face that they get their logo on the announcement and 3min intro at the beginning and that's it. I always try to get a different sponsor each time to keep the brand Hack and Tell independent.

  6. Announce the event early and encourage friends to swing by and present it.

  7. Recently we introduced the concept of "Hack of the months" which is voted by the audience at the end of the event. It encourages hackers to compete more and let more people stay until the end.

New York City guidelines

Hack and Tell NYC is pretty simple and it works well. Here are some major points:

  1. We don't have a permanent home, so we give up 2 minutes for pizza/food and space. This is the only time ever that recruiting can be mentioned, though we've found that many times our sponsors don't say anything about hiring to keep with the spirit. It's sort of implied in NYC.

  2. 5 minutes/ 5 minutes. Demo followed by discussion. We use http://hackandtell.org/timer -- a quick little lighting talk timer that claps at the end and stick by it. Don't let people go over -- even in mid thought.

  3. We discourage slides, but sometimes the "hacks" aren't finished or aren't very demoable. In the case that the hack isn't finished, the presenter should be seeking guidance or some sort of help.

  4. Braindump. In solidarity with another dying meetup that some of us liked to attempt, we now try to get one person to talk about some concept, or present a paper, or some sort of story. We call this a braindump. Slides are OK, 5/5 rule still applies--very fun.

  5. Absolutely no startup pitches. We do two things. We seek presenters ahead of time, check them out and ask clarifying questions. Sometimes people get past us, which sucks. No work related projects. The whole idea from the get go was to be proud of side projects to encourage more people to do so. Countless people come up to me afterwards and say, "I need to find time for some side projects." It's very gratifying in that way.

  6. We usually pick 8 or 9 projects. It gets to be too much after that.

  7. Do yourself a favor and use Meetup (or something like it). I'm not saying this because I used to work there. I'm saying it because it Meetup makes it trivial to do a lot of the things that would be annoying and very time consuming to do otherwise.

  8. Be friendly and inviting to newbies and those just learning, but it's OK to hassle recruiters and people who don't belong. Hackers come first.

I tried to do this thing a while ago where I interviewed people who run successful tech groups. The results are here: http://congregating.us -- might be helpful if you're new to the organizational side of things