Step 9 - How to Develop a Hackathon Program?
In this chapter, we will provide a comprehensive guide to developing a successful hackathon program. We'll walk through pre-hackathon activities, activities during the hackathon, and post-hackathon follow-ups. We will also guide you on how to frame learning goals in the context of a hackathon.
9.1 Pre-hackathon Activities
A hackathon doesn't start on the day of the event, but rather, in the weeks and months leading up to it. The pre-hackathon phase is critical for setting the stage and getting the participants ready. Here are a few key activities that you might want to consider:
Communicate the Importance and Benefits of a Hackathon: Not all students might be familiar with the concept of a hackathon. It is essential to convey the benefits of participating in a hackathon, how it could enhance their learning, and the unique opportunities it presents. Use the communication toolkit to ensure students receive proper instructions and information before the event.
Pre-lectures: Pre-lectures focusing on the hackathon's theme can be conducted to increase participants' awareness of the problem they'll be trying to solve.
Team Formation: This could either be left to the students or be a facilitated process. Having a balanced mix of skills within a team can be crucial for the hackathon's success.
9.2 Activities During the Hackathon
The core of the hackathon lies in the activities that unfold during the event. This is when the participants roll up their sleeves and start collaborating intensely on their projects. The event can be divided into three phases: the research phase, ideation phase, and prototyping phase.
Research Phase: In this stage, teams delve deeper into the problem they're trying to solve. They conduct thorough research to understand all aspects of the problem, its current solutions, and potential areas for innovation. Activities can include brainstorming, expert interviews, or user surveys.
Ideation Phase: With a good grasp of the problem, teams transition into brainstorming solutions. The goal is to generate as many ideas as possible, no matter how unconventional. Techniques like mind mapping, sketching, or role play can be employed to stimulate creative thinking.
Prototyping Phase: Once a potential solution has been chosen, teams develop a prototype. This could be a physical model, a digital representation, or a sketch. The key is to make the idea tangible and ready for testing and refinement.
9.3 Post-hackathon Activities
After the intense work of the hackathon, it's important to reflect on the event and celebrate the participants' hard work. The post-hackathon phase could include an exhibition where the public can view the prototyped solutions, listen to the pitches, and speak to the teams. Teams could also be encouraged to refine and further develop their prototypes.
9.4 How to Develop the Hackathon Program?
The structure of your hackathon will largely be determined during meetings with your hackathon project team. While the foundational framework for a hackathon is often design thinking, the structure can be more flexible for experienced participants. Here are a few factors to consider while developing your hackathon program:
Innovation Process Activities: Facilitators should guide participants through the innovation process in a manner that's appropriate for their level of experience. Novice participants might benefit from a tightly structured process, while those with more experience can have a bit more freedom.
Knowledge Transfer & Inspiration Content Activities: Alongside the core innovation process, facilitators can set up breakout sessions, workshops, or inspirational talks to deepen the participants' understanding of the problem at hand.
Learning Goals: The learning goals of the hackathon should align with the theme of the event and the subjects being taught to the students. Use the Hackathon Scoping Canvas to assist in this process.
9.5 Example Hackathon Programs
Here are examples of what a hackathon program might look like. Please note that these are just examples and your actual program might differ based on your specific needs and constraints.
Example 1-day in-person hackathon program:
Morning: Introduction and team formation
Mid-morning: Research Phase
Afternoon: Ideation Phase
Late Afternoon: Prototyping Phase
Evening: Presentations and Awards
Example 2-day in-person hackathon program:
Day 1:
Morning: Introduction and team formation
Afternoon: Research Phase
Evening: Ideation Phase
Day 2:
Morning: Prototyping Phase
Afternoon: Refinement and Practice Pitch
Evening: Final Presentation and Awards
Example 3-day in-person hackathon program:
Day 1:
Morning: Introduction, team formation, and problem definition
Afternoon: Empathize and scoping, research phase
Evening: Initial ideation
Day 2:
Morning: Deep-dive ideation and initial prototyping
Afternoon: Testing prototype and iterative development
Evening: Team reviews and feedback
Day 3:
Morning: Iterative development
Afternoon: Pitch development and practice
Evening: Final presentations, judging, and awards
Example 1-day hybrid hackathon program:
Morning: Virtual kickoff and team formation
Mid-morning: Online collaborative research phase
Afternoon: Ideation phase via digital brainstorming tools
Late Afternoon: Prototyping phase using online resources, remote collaborative tools
Evening: Presentations and judging via a video conference platform
Example 2-day hybrid hackathon program:
Day 1:
Morning: Virtual kickoff and team formation
Afternoon: Online collaborative research phase
Evening: Ideation phase via digital brainstorming tools
Day 2:
Morning: Prototyping phase using online resources, remote collaborative tools
Afternoon: Refinement and Practice Pitch
Evening: Final presentations, judging via a video conference platform, and awards
Example 3-day hybrid hackathon program:
Day 1:
Morning: Virtual kickoff, team formation, and problem definition
Afternoon: Empathize and scoping, research phase
Evening: Initial ideation using digital brainstorming tools
Day 2:
Morning: Deep-dive ideation and initial prototyping via online resources
Afternoon: Testing prototype and iterative development
Evening: Team reviews and feedback
Day 3:
Morning: Iterative development
Afternoon: Pitch development and practice
Evening: Final presentations, judging via a video conference platform, and awards
Note that a hybrid hackathon program allows for both the virtual and physical presence of participants. It opens up the possibility for teams to collaborate remotely and use digital tools to their advantage, increasing the accessibility and reach of your event.
In the end, the key to a successful hackathon program is to be flexible and adaptable. Tailor your program to the needs of your participants and the objectives of your hackathon. Remember that a hackathon is a dynamic event, and it's okay to make adjustments as needed.
Last updated