Day by Day

We don’t have a cash prize for the winner but that is not a problem. The winner will get bragging rights and the glory that comes with being named the winner. What does make winners is winning ideas, winning group dynamics and a product that satisfies you (and the judges).

These criteria are a mix of the four criteria I’ve been using (clinical accuracy and appropriateness, software quality, consumer need met appropriately, commercial potential) and the criteria used for NHS Hack Days.

Must have criteria

• The solution must be practical and concrete and address a problem of self-care for long term health issues.
• The solution must be clinically appropriate and accurate (using the Flinders care criteria).
• Consumer needs should be met, so talk to people with long term health issues and hear their point of view as part of your solution.
• The group must produce something that works. In other words, it must be more than a set of screengrabs of what the product could be. It must be usable software. Buggy is acceptable, but it must work.
• It was done over the weekend of the hackathon. Be clear in your presentation on Sunday that (1) your group’s idea emerged at the hackathon or (2) it’s been a work in progress and the group pushed it to the next step over the weekend. It’ll be the next step for option 2 that will be judged.

Good to have criteria

• What real, practical, immediate benefit is there for people to use your solution?
• Have you included some humour to soften the experience of using your solution?
• Do you like it?
• How difficult is the problem you’re addressing? In other words, is it a complex, difficult problem to solve or have you chosen something really easy? This will help judge the difference between a workable but not flash solution to a difficult problem and a flash and sophisticated solution to an easy problem.
• If you want to make a big change with your solution, it may be wise to create small do-able solutions to components of the problem you’re solving. Indicate this to the judges in your presentation.

Things to think about

• In the spirit of Ubuntu be open about what you’re doing and always acknowledge your sources. Ubuntu is about being human, about doing things together for the greater good.
• Acknowledge your inspiration.
• The group’s work should be clearly a response to a problem.
• Avoid creating a solution that’s looking for its problem.
• Clearly outline the problem you’re attempting to solve so that the judges can see the connection between the problem and its solution
• What you’ve been working on for commercialisation for the last six months will not be considered for judging, i.e. it is disqualified.
• It’s not going to be practical if your solution flies in the face of established government policy.

I’m looking forward to seeing how creative, innovative and collaborative you and your group members can be during the hackathon! It’s going to be great!