Once you have defined the key problem the participants of your Hackathon set out to solve you have to start thinking about the size. If it is too small, your event might lack participants with capabilities and ideas that are key to solve the problem. If the Hackathon becomes to big, complexity increases, good ideas might not be heard and costs surge. However, what might the right size be?

In general the sizing is dependant on two variables. The scale of the problem on one hand, and the available resources on the other. Let’s first have a look at the scale of your problem that should be solved by the Hackathon participants.

  1. Narrow Problem: You have defined a very specific area in which the innovation can happen and provided a clear scope of the solution. E.g. in FinTech there are multiple events happening, focusing specifically on innovating the insurance branch of certain companies. Narrow problem events require usually a smaller number of participants with highly specialised knowledge in the area. A good mix of outside and inside experts will be sufficient to achieve the level of innovation expected. Concrete, we would speak about 50-250 participants
  2. Mid-scope Problems: When tackling problems that impact a region or broader industry you will need a wider audience participating in your Hackathon. An example would be the MedHack at the Johns Hopkins University, showing a focus on a the health sector but not on a specific region. A Hackathon of this scale will require multiple experts from several disciplines as well as outsiders to spark new ideas. Concrete, from 200-1000 participants should be participating
  3. Broad Problem: If the problem is not clearer defined in sector or region it is considered broad. Tackling global issues such as global warming or Human rights would be in this category. A good example is Hack the North in Canada with no concrete definition but more of a general theme. Experts from all possible areas are required to exchange to be able to tackle these problems. A Hackathon of this magnitude could span anywhere from 500-10’000 people or more.

Of course, all depends on the resources available. Not every institution can run a Hackathon with 10’000 participants. This implies that it might be necessary to narrow the problem to a solvable scope.

Whatever the size is, make sure to have a divers and interdisciplinary crowd participating, but also a structure in place to capture innovation as it happens to ensure the best possible outcome.

Thank you for reading. As always I am looking forward to your feedback and questions. Until soon, cheers.

image

One thought on “Sizing your Hackathon

Leave a comment