Inspiration

During a hackathon, organisers are swamped with ensuring smooth running of events. It becomes tricky to ensure hacker teams have a great hacking experience, especially for newer hackers.

Often, organisers only find out about poor experiences and areas to improve – through surveys post-hack. If only they were able to support teams that needed the most help and guidance during a hack. Additionally, hacker teams struggle to understand how their project is going, how well they are communicating, and having fun at a hackathon through events.

Two important problem statements arise:

  1. How can we empower organisers to understand how each team is going during a hackathon and not only after?
  2. How can we incentivise better project, communication and participation outcomes for teams during a hackathon?

What it does

TeamTree is a reflective visualisation of a hacker team.

Starting off as a sapling and growing in complexity and beauty as the team develops aspects of their project, communication, and participation. Each aspect results in a tree branch growing.

During a hackathon:

  1. Organisers are able to see a real-time forest growing an intuitive visualisation of how teams are going. Thus, easily identifying and then provide guidance to teams that are struggling in some aspect.

  2. Hackers are incentivised:

  • Better Project Outcomes: GitHub based – Through more frequent GitHub commits, using multiple languages/frameworks/tools, and learn proper development practices.
  • Deeper Communication: Discord based – to chat more frequently and use more positive language and collaboration.
  • Broader Participation: Google Forms based – checking into hackathon events and sponsor showcases results in a more fun hackathon experience.

After the hackathon, hacker teams are able to flex their TeamTree through a web XR model.

Built With

  • figma
Share this project:

Updates