Joining a hackathon requires more paperwork than the application to the event itself. Some programs may or may not need their participants to prepare a presentation explaining, informing, or detailing their ideas turned into projects. But for people joining a hackathon for the first time, what segments should a submission presentation contain?
1. Problem of the Project
The first thing a presenter or a team should talk about is the problem they will try to solve—what systems or services they will use and the project's benefits to the industry and the society. Many programmers have developed various solutions to existing problems, but have not all have been implemented.
Therefore, the problem of the project should be a statement that states the issues needing a resolution and the plans on solving them. Treat the project similar to a science experiment in school requiring some answers. After writing the problem, aspiring hackathon participants should know if the project is worth it to solve or not.
2. Brief Introduction
The second segment of the presentation should be a brief introduction. Introduce the team, background knowledge of every member, their skills, and projects they've worked on are good enough to give them credibility and support from the judges. Participants should also provide an introduction to the project itself.
Giving an introduction of the project—whether it is a start-up or a new invention—gives the audience a feel of what the team will be doing. For example, a team could tell the audience that they will make a dating app that solves the issue of people's first date being a disappointment. Sometimes, a brief introduction is all it takes to help the judges decide on the importance of the project.
3. Project Beneficiaries
When writing the problem statement, project participants should also include the project’s beneficiaries. Presenting the project’s beneficiaries helps the audience understand the importance and the significance of solving the task.
Beneficiaries are people who will benefit from the project the most. For example, some of the beneficiaries of a dating app would be the gender that the app caters to. Or a team applying for an app that allows people to meet their neighbors could mention its beneficiaries as the people who live in an apartment building or gated community where they can't meet anyone.
A good presentation should not involve explaining the entire solution to the project. The whole solution would mean that the presentation is too long, and the judges will get bored or confused.
Instead, the team should summarize the project and what they have done so far. If the project is a start-up, the audience should know if it is taking off and a summary of the team's progress up to this point.
5. Expected Results
The last part of the presentation is the expected results of the project. The team should have a return of investment or a clear idea of the project's success. This part is critical to writing a winning project.
An example of the expected results would be to use a dating app to help people find love. What would the fund-raising plans be, and how would they change the dating app. The team could also use the presentation to explain how they will promote their dating app, whether through social media or advertising.
Before Joining a Hackathon…
Remember that it's not about what you're making or how it will look. Judging for a hackathon focuses on problem-solving, the project's beneficiaries, and expected results. The presentation is an essential part of the entire hackathon. The exhibition decides whether the team will advance to the next round, receive a prize, or simply be eliminated.
On Hackathon.com you can easily search to find the nearest hackathon near you. We have event listings for everyone, from aspiring developers, designers, programmers, managers, and industry experts - as well as those with no experience at all! Check out our event page today to register for a hackathon now!