Organising a hackathon means setting up an intensive, time-bounded creative sprint where teams work on a concrete problem in a short window. The format originally comes from the technology and software world, but it has since reached much further. Marketing teams, HR departments, healthcare organisations and even governments use hackathons as a tool for innovation, team development and problem-solving.
The core of a hackathon is simple. You give people a challenge, put them in mixed teams and give them limited time (typically 8 to 48 hours). After that you let them work towards a presentable solution. The time pressure isn't an accident, it's the engine. Perfection isn't the goal, but progress is.
A hackathon works well when you want to generate ideas quickly around a specific question, when you want to break down silos by getting people from different departments to work together, when you want to give young talent a stage, or when you want to make a culture of innovation visible and tangible.
It works less well in three situations: when there are no real questions, when the outcomes lead nowhere, or when participation feels mandatory.
