 "So you think you can hack? Here’s a 5 step guide to winning at a hackathon")
In brief, a hackathon, held for a predetermined amount of time, involves tackling a certain problem set by the organisers. The solutions are usually app/tech-based but can be in the form of a device as well.
Here’s a short guide that will steer you on a path to victory.
1) Get your A-team together
A successful team composition, not too unlike a start-up, needs the following roles fulfilled:
- A designer to draw designs/mockups and make things look jazzy
- A coder to program the solution and make it snazzy
- A businessperson to pitch and excite the judges till they’re dizzy
2) Understand the problem and solution
While spending 55 minutes out of that figurative one hour is slightly too much for a hackathon, I strongly recommend spending a good portion of time fleshing out the problem statements and how your solution can address it – preferably with solid market research.
This phase is arguably the most important step.
3) Feedback, feedback, feedback
You should be actively getting feedback for your solution at various points. The last thing you want to make is something that people don’t need or something without enough use cases to be compelling enough.
4) Judge who judges the judging
Know who your judges are; understand what they look out for. That’ll help you craft your solution and pitch accordingly. Knowledge is half the battle won.
5) The pitch
A very common error? Pitching overly technical solutions to business judges, losing their attention in the process. Teams also spend too much time on the solution, and too little time preparing for the pitch. I recommend setting up a schedule so that you can review your solution, and adjust your pitch if needed.
This is an excerpt from Tech in Asia. You can read the full article here
