Hackathon / Ideathon
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
An innovation format in which participants work under a hard deadline on a stated theme, usually in cross-functional teams, and present results at the end. Hackathons emphasize building a demonstrable artifact, while ideathons emphasize generating and pitching concepts. The key qualification is the time box: the deadline is deliberately too short for perfection, which forces prioritization, rapid decisions, and building rather than planning. Outputs are normally prototypes rather than finished products.
SCAFFOLDING EFFECT
Reduce cognitive load
- Deadline forcing: use a short fixed window to force decisions that would otherwise stall. - Skill mixing: combine engineering, design, and domain expertise so solutions borrow across fields. - Demo filter: judge results by what can be shown working, not by how the plan reads.
Anchor fast decisions
Under a hard deadline the cost of deliberation rises relative to the cost of action, so teams shift from discussing to building. Focused intensity also raises the likelihood of flow, and flow increases output per hour. Cross-functional teams add recombination, since each member brings a different repertoire. The compressed window therefore yields a disproportionate amount of tested output from the same people.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Hackathonverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS