The key to organizing a hackathon is to start with “Why?”
Sinek explains how the Wright brothers, young farmers who never finished high school, became the first to build a machine that could fly, although their main rival for that claim had financial support from the U.S. War Department and was beloved by the New York Times. Why did the Wright brothers succeed? They possessed the deepest certainty that if they could make an aircraft that could leave the ground and fly through the air, the world would be changed forever.
The lesson: If hackathon attendees don’t understand why they are there, it will be tough for them to stay emotionally and rationally connected to the objective.
Here are a few other things to keep in mind when organizing a hackathon:
Build a community from the ground up
In our experience with Poderomedia, Hackathons and Hacks/Hackers Chile, holding a hackathon without also coming together for meetups, lectures, brainstorming, and so on is tricky. Meetings like this let you know who you are dealing with before you decide to hold a hackathon. Starting at the beginning and building community from the ground up may take longer, but qualitatively the result is greater, especially when you seek to promote an innovation ecosystem that will disrupt media in the long term. Anyone can run 100 meters. It’s the marathons that matter.
Set clear rules
Setting up a hackathon is like designing a game. You must establish a concrete mission and clear rules. Here are some examples from recent hackathons:
"Story and Algorithm": a hack day organized by Mozilla Open News last year. It focused on "new ways in which the data allow us to tell convincing stories.”
Hackathon of creating visualizations using D3.js: a session organized by Hacks/Hackers Buenos Aires in April, which proposed to "make news apps on D3.js that allow journalists, programmers, designers and organizations to interact with the library to solve data visualization problems.”
- Radiothon: a hackathon held by Hacks/Hackers Chile in May 2013 to help independent and community radio stations use lo-fi technology and put together a collective online radio network in one afternoon.
Follow the rule of three
Just as a stool needs three legs for stability, a hackathon needs three people: a journalist, a programmer, a designer or front-end developer. If you have a journalist, you have someone who asks questions in the public interest and seeks data for the programmer and designer. By having a programmer, you make sure you build or reuse the technology in the end. If you can have a designer or front-end developer in the group, he or she makes sure the project has a decent interface and stays focused on usability.
As in sex, before, during and after are equally important
The problem with the majority of hackathons is a failure to monitor and follow up post-hackathon. People are excited to come together and build something, but the majority of hackathons stop short of the “after.” But it’s what happens after the hackathon that can often be most valuable.
Tools like Hackdash.org (born at a hackathon) help attendees believe in the project and track it once the event concludes.
Having allies willing to use, finance and publicize the best products arising from the hackathon also encourages participants to complete their projects beyond the test phase trial. This also helps community members take the hackathon seriously and not just see it as a sandbox for adults.
Other hackathon resources
Miguel Paz is a Chilean journalist and founder and CEO of Poderopedia, a data journalism website that highlights links among Chile’s business and political elites. Read about his Knight Fellowship here.
Photo by Miguel Paz, taken at the Hacks Hackers Chile Radiothon.
This post was translated from Spanish into English and edited by Jennifer Dorroh.