Scoring categories

 1. Connection to Youth Wellbeing
  • Does the idea solve any of the current problems?
  • How well the idea is related to youth wellbeing?
  • Does the idea offer a disruptively innovative product/service?
  • How innovative is the idea for the youth wellbeing industry?
  • Is there a need for a product/service like this?
 2. Idea Validation (understanding of customers and their needs)
  • Has the team chosen their specific target audience?
  • Did the team build a prototype (paper or powerpoint is ok)?
  • Did the team mention any other parties they may cooperate with?
  • Did the team get out and talk to customers?
  • Did the team modify their solutions according to feedback?
  • Is this idea scalable (can be taken across borders/industry verticals?)
3. Team Dynamics
  • Did all team members take active participation in developing the idea?
  • How equal did the team share responsibilities?
  • Did the team members asked for advice/guidance during the hackathon?
  • How likely it is that the team will continue working together if given such opportunity?
Suggestions on how its done

+ Assign roles in the team: project manager(s), designer(s), programmer(s)
+ Be people centric: talk to the people you’re trying to help. Write down who they are: users, partners etc
+ Build a prototype. You can draw, do arts and crafts (askarrella for us Finns!), anything that people can look at and perhaps play with. Also, hot tip: Pop Appis great for prototyping mobile apps rrrreeeally quickly!
+ Pitch: its really important that other people can understand what your project is about, so practice on how to present your work!
+ Lastly the coding bit!
Yes, it is awesome if you manage to code your solution, or parts of it, IF it requires coding or software that is!
You can do really well over the weekend with zero coding, if you concentrate on prototyping and other areas.
Do not obsess about coding (it is only a small part of one scoring segment!)

Always design, prototype and test your prototype first!