JLS City – Inside Scoop

Hackathon

A hackathon is a time-bound event where participants collaborate to innovate or build proofs of concept and MVP for a specific pre-defined problem.

Also known as hack days, hack fests, or code fests.


JLS Membership Platform Hackathon Banner

Description


A hackathon is a high pace, high-energy participatory event in an informal ambiance. A hackathon usually lasts anything from one to three consecutive days.

It provides a time and space for people to collaborate and innovate on a given topic. People split up into self-organizing teams and work on turning their ideas into concepts, prototypes, or Minimum Viable Products (MVP).

Each team demonstrates its solution at the end of the event. A panel of expert judges evaluates the solutions, and the winning team receives a reward. A prize can range from a letter of recognition to considerable monetary prices.

The term ‘hackathon’ combines the words ‘hack’ and ‘marathon.’ Although the term was first used in connection with programming and many hackathons still involve coding, hackathons are not limited to software development.


Benefits

  • Fast ideation and prototyping
  • Creative problem solving
  • High pace collaboration and innovation
  • A way to explore and test new solutions beyond established processes and bureaucracy
  • Enhance creativity beyond the hackathon event
  • Seek innovative ways and advancements in products or services
  • Build/strengthen the community involved
  • Provide learning opportunities for participants
  • Generate momentum around creativity and innovation

Event Length

Hackathons can last anything from one to seven days. The 24- or 48-hour format is the most common one, including the weekend.

The key to the right length of the hackathon is to make it long enough so that actual ideas and prototypes can be developed while keeping the event short enough to attract the target audience.

  • 24-hour hackathons are appealing to younger professionals, but less so to professionals with families
  • Longer hackathons are harder to organize and are more costly, but participants have more time to produce robust ideas and prototypes
  • External) Hackathons are typically held over a weekend to prevent people from missing work/school

Size & Participants

Hackathons work for any number of participants. They typically range between 30 to 1,000 participants depending on the format, target audience, and topic.

The participants are the secret sauce. Without them, a hackathon wouldn’t be possible.

  • Choose the target audience based on the theme/topic of the hackathon.
  • Involve people who are excited about being part of the experience.
  • The teams will benefit from diversity of thought.
  • Hackathon teams are always self-organizing. They decide how they want to approach the challenge and manage their time.
  • The teams can either form before or at the hackathon.
  • The ideal size for a hackathon team is between 4 to 7 people.

Format

  • Online
  • In-person
  • Hybrid of online & in-person
  • External
  • Internal
  • Hybrid of external & internal

Theme

Hackathons have a theme or domain, often specified by a sub-theme or specific challenge statement. For example, e.X.Hack (Employee Experience Hackathon) is the theme, and redesigning the pre- and onboarding experience for new hires can be the more focused challenge statement.

A theme should get participants excited about the hackathon. People want to build stuff that is exciting, that matters, that gets used, and that gets noticed. Try testing your theme against that. If it holds up, run some rapid testing with a few potential participants before committing to a theme.

Here are some examples:

  • Policy focused: Develop ideas for creative work arrangements after COVID
  • Business model focused: Develop a business model to make learning initiatives self-sustaining
  • Communication focused: Create communication hub to support Agile transformation journey
  • Data jams: Analyze HR data and produce insights around diversity, equity, and inclusion
  • Employee focused: Design the career pathing model of the future
  • Marketing focused: Create a playbook for impactful storytelling by HR professionals
  • Software focused: Build an informative app for an engaging pre- and onboarding experience
  • Software focused: Build a marketplace for learning and knowledge sharing

In addition to an inspiring theme, a hackathon needs a well-defined problem statement, as well as some guiding questions and additional resources (if applicable). It provides focus to the teams and ensures they are working on the right problems and guarantees the solutions are designed with the right end-users in mind.

It is important to point out that it is challenging to solve highly complex problems in the span of a hackathon. The hackathon is usually just one step in a longer redesign or innovation process. However, the hackathon is a very powerful instrument for rapid ideation and prototyping. Many ideas and projects generated during a hackathon find a way to incorporate themselves into the business over time.


Budget

Even though the money spend on hackathons is well invested, they are not cheap to host.

Against expectations, larger-size events tend to have higher average per-person costs due to higher expenditures for travel costs, security, facilities, promotional efforts, and the need for an event/production company.

Here are some reference budgets for in-person hackathons:

  • 30 participants: US$ 2,000 – US$ 5,000
  • 50 participants: US$ 5,000 – US$ 12,000
  • 200 participants: US$ 20,000 – US$ 40,000
  • 500 participants: US$ 50,000 – US$ 100,000
  • 1,000 participants: US$ 200,000 – US$ 250,000

It is important to make a budget for your hackathon. Here are some typical high-level spending categories to consider:

  • Venue and security
  • Staffing (facilitators, volunteers, judges)
  • Catering & celebration
  • Promotion, signage, and branding
  • Swag & Prizes
  • Miscellaneous – from nametags and lanyards to extension cords and banners
  • Event/Production Company
  • Speakers
  • Travel & Expenses
  • Emergency fund


Resources

Resources


Basic Package

Hackathon Prizes

Hackathon | Ideas for Gifts & Prizes

Hackathon Timeline

Hackathon | Timeline


Plus Package

Checklist Hackathon e1626176472761

Hackathon | Checklist

Hackathon Rules

Hackathon | Hackathon Rules

Hackathon Schedule e1626176269791

Hackathon | Schedule

Hackathon Code of Conduct

Hackathon | Code of Conduct

Hackathon Voting

Hackathon | Judging/Voting Card

Checklist Hackathon e1626176472761

Hackathon | Checklist

Hackathon Schedule e1626176269791

Hackathon | Schedule

Hackathon Rules

Hackathon | Hackathon Rules

Hackathon Code of Conduct

Hackathon | Code of Conduct

Hackathon Voting

Hackathon | Judging/Voting Card


Pro Package

Hackathon Budget

Hackathon | Budget

Hackathon Problem Statement

Hackathon | Theme & Purpose

Hackathon Metrics

Hackathon | Metrics

Hackathon Budget

Hackathon | Budget

Hackathon Problem Statement

Hackathon | Theme & Purpose

Hackathon Metrics

Hackathon | Metrics


Premium Package

Hackathon Backlog

Hackathon | Backlog

JLS Membership Platform Hackathon Playbook

Hackathon | Playbook (Template)

Hackathon Slides

Hackathon | Slides (Template)

Hackathon Budget

Hackathon | Budget (Template)

Hackathon Metrics

Hackathon | Metrics (Template)

Hackathon Backlog

Hackathon | Backlog

JLS Membership Platform Hackathon Playbook

Hackathon | Playbook (Template)

Hackathon Slides

Hackathon | Slides (Template)

Hackathon Budget

Hackathon | Budget (Template)

Hackathon Metrics

Hackathon | Metrics (Template)