Hackathon Agenda Template
Hackathons reliably produce energy and demos, and then the corpus-familiar silence: no follow-through. This template keeps the build magic and fixes the two structural gaps: problems worth solving, and a real path for winners after the demo.
Hackathon Agenda Template
Who it is for: Internal or public hackathons, 30 to 1,000 people, one to three days. Typical duration: 2 days.
The full agenda, block by block
Click any block to see why it is there and which of the eight evidence pillars it feeds.
Problems with owners beat themes; the choice is the first act of commitment.
Deliberate team assembly beats friend clusters for both output and ties.
The core: uninterrupted making with help findable.
Light structure keeps 40 teams from silently stalling.
One user test doubles the realism of every demo that follows.
Demos are the celebration; the criteria keep them honest.
This block is why this hackathon will not be like the others.
The afterlife of the work is public and dated.
What the strongest agendas do differently.
Three moves, pulled from the pillars that separate the top 5% of scored agendas from everyone else.
Source problems from owners who commit to piloting winners before the event starts.
Add one real user test before demos; it transforms judging and learning.
End with continuation contracts, not just prizes: sponsor, pilot, date.
Real agendas to study.
The highest-scoring public agendas we found in this category, scored by the same Gathering Effectiveness Score rubric.
A number worth citing.
The corpus average is 21.8 of 100; follow-through averages 5.8.
Questions about this template.
Why do most hackathon projects die?+
No continuation structure. The corpus-wide follow-through average of 5.8 of 100 is the hackathon story in one number.
Internal or public?+
The template works for both; internal ones need the continuation contract even more because the day job returns Monday.