How to run a hackathon that people actually finish

Great hackathons are designed backwards from the demo. Decide what a finished submission looks like, then work back through judging, mentoring and check-in so every hour has a purpose.

Scope the theme

A narrow theme produces better projects than an open brief. Publish the theme with the registration page so teams arrive with ideas.

Judging

Score on a short rubric that judges can hold in their head, and give every team the same two minutes.