Meanwhile, as everyone is broken down into little teams, very few people actually meet others; the worst case scenario of this is a lot of times people come with a few of their friends, and literally meet no one.
I thereby find myself going to events like this and purposely not joining a team and not entering the a-thon, and instead watching like a hawk waiting for the few moments when someone is taking a break (I then meet them).
On the other side, I've seen events like this work well: in specific, the 360|iDev game hack-a-thon is nearly perfect. As it is part of a larger conference, there are lots of chances to meet people, and in fact many people don't participate at all (as there is no real expectation to); of those who remain, they are clearly building "something fun", so the idea of "would this actually work" is irrelevant.
* Chronicling the products that were created.
* Having a forum where there is discussion on the MVPs created, to validate it against real market and see if it can be developed into a product.
* A place where the MVP creators can try to find initial customers / beta testers.
Individual networking does not required any post event hand holding, but thats hardly enough to help the MVP to take shape into a full blown product.Once the intensity of building is over, that's when the real networking begins.
- give a chance for everyone to network with each other
- put people in situations where teamwork is needed
- put focus on creativity and make things fun. FUN is the focus here.
- learning is still the goal here but not in a stressful/lack of sleep environment.