Steven's Knowledge
Self-Driven

Hackathon

Dedicated time to work on projects you're passionate about

Core Idea

A Hackathon is the concentrated version of innovation time. Over 1-2 days, members can freely form teams and work on any project they want. No restrictions, no approvals — just present the results at the end.

How to Implement

Format

  • Frequency: Once per quarter or semi-annually
  • Duration: 1-2 days (consecutive workdays)
  • Participation: Free team formation, solo participation is also fine
  • Theme: Can set a broad direction (e.g., "Improve User Experience") or be completely open

Process

  1. Proposal phase: One week before the Hackathon, everyone submits ideas and votes
  2. Team formation: Form teams freely based on ideas
  3. Development phase: 1-2 days of focused development
  4. Demo phase: Each team presents for 5-10 minutes
  5. Voting and wrap-up: Everyone votes to select the best project

Converting Results

  • Good projects can be converted into official product features or internal tools
  • Even without conversion, the experience and relationships built are valuable
  • Document Hackathon results to inspire future participation

Tips

  • Don't schedule other work during the Hackathon
  • The focus is on creativity and teamwork, not overtime sprints
  • Provide food and a good environment so everyone enjoys the process
  • Don't let the Hackathon become a competition to showcase individual ability — the focus is team collaboration and innovation

On this page