Hackathons are time-bounded build environments where people come together around a problem, idea or opportunity and turn capability into a working response through rapid collaboration and experimentation.
A Hackathon deliberately shortens the distance between a question and a working response. The value is not only the final prototype; it is the learning created through collaboration, decisions, iteration and demonstration.
The challenge should give teams something worth exploring, building or demonstrating within the available time.
A fixed sprint creates focus and forces teams to decide what matters now, what can wait and what must be tested first.
A prototype, experiment, model, workflow, analysis, experience or other tangible response makes learning visible.
Teams learn to divide work, communicate assumptions, resolve disagreements and integrate contributions under pressure.
Teams explain what they built, what they learned, what evidence supports it and what they would do next.
Hackathons can be designed as one intensive session or a multi-day sprint. The architecture stays consistent: frame the opportunity, build quickly, test continuously and demonstrate clearly.
Clarify the problem, users, opportunity, constraints and definition of success.
Bring together complementary capabilities, roles and perspectives.
Generate possibilities, test assumptions and select a response worth building.
Move quickly from concept to prototype, model, workflow or working demonstration.
Gather feedback, inspect behaviour, challenge assumptions and refine the response.
Communicate the response, evidence, learning, limitations and next step.
A hackathon can be adapted to the learner, organisation, capability and problem. The timebox and build requirement remain central.
Learners apply newly developed skills to a defined problem with mentoring and a final demonstration.
Teams combine capabilities from different disciplines to explore a new product, service or operating idea.
Teams work on a real organisational problem and develop evidence-backed responses within a fixed window.
Technical teams prototype applications, data solutions, AI experiences, integrations or digital services.
Teams address a community or societal challenge while balancing feasibility, inclusion and measurable value.
Participants move from a question, insight or research finding toward an experiment, model or demonstrable application.
The strongest hackathons are not collections of identical skills. Teams are designed so different forms of capability can meet around one problem and produce a coherent response.
A team can combine technical, analytical, creative, business, domain and communication capability depending on the challenge.
The sprint should help teams practise the behaviours required to build together under real constraints.
A hackathon outcome should make both the response and the learning visible. Not every sprint needs a production-ready solution; it does need a credible demonstration of what was attempted and learned.
A demonstrable product, model, workflow, experience or technical proof of concept.
The key assumptions, alternatives and choices that shaped the build.
Tests, user feedback, analysis, experiments or observations that support the team's claims.
A concise explanation of the problem, response, value, limitations and next step.
What the team discovered about the problem, capability, collaboration and approach.
Hackathons sit alongside Labs, Challenges and Project Labs. They add a distinctive ingredient: an intense shared build window in which collaboration and speed become part of the learning experience.
Build concepts, methods and foundational capability.
Develop repeatable performance with feedback.
Apply capability under constraints and ambiguity.
Collaborate rapidly to build and demonstrate a response.
Develop a more sustained solution with deeper ownership.
Speed should not remove responsible practice. Hackathons should make authorship, data use, intellectual property, tool use, accessibility, safety and evaluation expectations clear.
Explore applied learning across the Academy, or work with Astraal to design a focused hackathon around a capability, business challenge or innovation opportunity.