At Xobni, we made some changes to the Yahoo! recipe for Hack Day. Here are our startup-optimized keys for a successful Hack Day:
- When: To minimize disruption to our roadmap, and allow the team to focus completely, we hold our Hack Days right after a release. We try to do at least two a year
- How Long: We start our Hack Days on Thursday evening at 5pm and present on Tuesday morning. So the total time consumed of work was 2.5 days (in the end, about one full day more than Yahoo!…and we spanned the weekend…which allowed the motivated to work four full days on their hacks)
- Focus: Unlike Yahoo!, we encourage our employees to focus on Xobni. The rules aren’t too much more specific. Some employees even turned in culture hacks, such as fake TV commercials for the product
- Presenting: We extended the time to present from 90 seconds to up to 3 minutes. At Yahoo! it was routine for people to get cut-off during their Hack preso. 3 minutes is way more than enough.
- Prizes: We made our prizes better. Rather than just fame, we added prizes for best hack to include things like iPods, iPhones, Kindles, etc. For second place, we do $100 Amazon gift certificates. You could consider going even more elaborate…but there is an issue with that. If the prizes are too good, the people that lose feel like they are really missing out, and rather than feel good about their hack, they feel jealous and disappointed.
- Patents: We video all the presentations and send the patent committee through them later looking for patent potential. In the last hack day, we added nine new patent ideas to our patent backlog. Each patent application pays $500 to the responsible contributor…another benefit to the employee for their hard work and creativity.
- Judges: Unlike Yahoo!, all our judges come from outside the company. As our employees all love startups. They want to be founders of their own startup some day, so I always include at least one VC as a Hack Day judge (some are investors in Xobni, others are not. We also look for great entrepreneurs (Nirav Tolia was a judge, Michael Arrington was a judge, Joshua Schachter was a judge, ). We invite hackers with great street cred, like the lead product manager for Mozilla’s add-in team. We have had members of Y!’s original Hack Day team, like Daniel Raffel or Leonard Lin. Lastly, we invite subject matter experts from UX, engineering and product. A great judge panel will be 3-4 people. They will need to commit 2 hours to participate. I don’t think we have ever had a judge who didn’t love participating.
At the time I wrote this post, the team was 18 people, and submitted 24 hacks in a hack day, which is 1.2 hacks per participating employee…an over 100x increase over Yahoo! About 20% of hacks make it into the product in one form or another within 6 months. Over half of the hacks greatly influence future development or changes. Some hacks have been transformative for the product or our business model.
In fact, in our current state, hacks are even more critical to the company. I credit our successful hack days as a significant contribution to giving our team the feeling that they can create something interesting or cool without permission and show it to us. About a third of our new products come from this type of process, no hack day required. It is just every day business at the company now.







