Guide
What is a hackathon for companies and when is it worth it.
A short, jargon-free guide for People and Innovation leaders who are thinking about running one.
What is a hackathon
A hackathon is an intensive event where several teams work, within a limited time, to solve a specific challenge. The word combines “hack” and “marathon”. It was born in the software world, but today it is used for any kind of problem: a process that does not work, a new product, customer experience or attracting talent.
In a corporate hackathon, the company itself sets the challenge. The teams analyse it, propose solutions and test them with a prototype before the event ends. Finally, they present their proposal to the company.
Types of corporate hackathon
- Internal. The company’s own staff take part. It activates an innovation culture, but teams tend to look at the problem with the same old eyes and leave their work during the event.
- With external talent. People from outside take part, for example university and vocational students. They bring a fresh perspective, and the company gets to know talent before hiring.
- Mixed. It combines company staff and external talent in the same teams.
At Delta we work with teams of young talent and mentors, so your team does not have to leave their work.
What you get
- A prototype (MVP) that can be tested, not just a presentation.
- Several tested solutions in a short time, before investing in one.
- A better-defined challenge, even if none of the solutions goes ahead.
- Contact with young talent who have already worked on a real problem at your company.
When it is worth it (and when it is not)
It is worth it if you have a specific challenge that has been sitting in a drawer, you want to explore several solutions quickly before investing, or you want to connect with young talent in your area.
It is not the right tool if nobody at the company will follow up on the result, if you need a finished, production-ready product (a hackathon gives you a validated starting point, not the final version) or if you are only looking for an image campaign with no real challenge behind it.
How to prepare a good challenge
- Specific. “Reduce waiting times at reception” works better than “improve the customer experience”.
- With a person in charge inside the company, who answers questions and collects the result.
- With just enough information. What is needed to understand the problem, without sensitive data.
- With a success criterion. Knowing in advance what would make the result useful to you.
You do not need to have it figured out before calling us: defining the challenge with you is the first step of our process.
What a hackathon with Delta looks like
Before, we define the challenge with you in one session. For 24 hours, teams of young talent work on it, guided by mentors. Afterwards, we hold a closing session with your team and hand over the MVP, a detailed report and the talent’s contacts.
Frequently asked questions
How long does a hackathon last?
Some last a few hours and others several days. Ours last 24 hours: enough time to reach a prototype and short enough to keep the energy up.
Do you need to know how to code to take part?
No. Teams mix engineering, design and business profiles, and the prototype can be a mock-up, a process or a service, not only software.
How is it different from a design thinking workshop?
A workshop usually ends with ideas. A hackathon ends with a prototype and a presentation to the company, within a fixed time.
How much does it cost to run a hackathon?
It depends on the challenge and the size of the event. Tell us about your challenge and we will prepare a proposal.