Go to content

Why hackathons are always great – and sometimes right!

Hackathons are bursts of energy. Intensive, time-limited events where people with diverse skills and disciplines come together to brainstorm, collaborate, and engage in rapid prototyping to build solutions to specific challenges. It’s a space for creativity and problem-solving, often producing early-stage ideas or solutions in just a few days.
Hackathons are a great way to test ideas, meet people, and gain exposure to an industry. Even if you don’t win, the connections and learnings can be invaluable. That’s what happened to us – you never know who you’ll meet or what opportunities will come out of it.
… in conversation with Mathias Mølgaard, CEO & Co-founder Storyhunt. Read the full interview here.
An often-overlooked strength of hackathons is how they break away from typical project structures. In a regular office, projects often get bogged down by hierarchies, approval processes, strategy meetings, and budget checks. But there’s no room for bureaucracy in a hackathon! You don’t have to be a senior executive to propose or push an idea forward. In a hackathon, every idea has a chance — if it makes sense to the rest of the team.
Another superpower of hackathons is their adaptability, fitting seamlessly into diverse settings from universities to more corporate spaces. The key is aligning the format with your goals and the participants you want to engage.
The starting point of this chapter is the Solution Searching phase of XNTC – a phase primarily centered around hackathons and the hope that out of these hackathons would come solutions to the cross-Nordic problems already identified by the tourism industry.
In this chapter, we’ll look at why hackathons can be great—and why they’re not always the right fit. You’ll find practical tips on when to use hackathons, how to run one, and why the work shouldn’t stop after the final pitch. Through three very different examples, we’ll explore how hackathons can produce golden ideas, promising concepts waiting to hatch, or bursts of energy that spark excitement but don’t always lead to a big solution.

QUICK OVERVIEW: XNTC Search for Solutions & Hackathons

A quick overview of the XNTC activities as part of the solution search, based on the challenges identified in the problem mapping:
  • 2 Hackathons in Denmark and Iceland, branded as “Solution Camps” and carried out in partnership with a Danish University and the Iceland tourism and startup ecosystems respectively.
  • Through a Cross-Nordic Mapping of Tourism Startups, XNTC uncovered approximately 400 tourism and tourism-related startups across the region, categorising them to highlight emerging trends and opportunities (see Chapter
  • Open Calls for Solutions: Based on the challenges identified, XNTC launched open calls for solutions within three overall themes: 1) Planet preservation, 2) Co-creating a year-round industry, and 3) sustainable business models for tourism SMEs.
  • XNTC conducted 3 Intensive Design Sprints to dive deeper into the outcomes of the two hackathons, and a stronger focus on the problem area of digitalisation.

WHEN, AND WHEN NOT, TO DO A HACKATHON

Hackathons are an incredible tool when used intentionally. Done right, they can spark fresh ideas, solve real problems, and energise participants. But their chaotic energy and time-limited nature mean they’re not right for every situation. For example, without clear goals and a plan for what comes next, the impact of a hackathon can fade as quickly as it started —leaving little behind but a LinkedIn post to mark the occasion.
So, when should you go all-in on a hackathon? And when is it better to hold off?
Here’s a guide to help you decide:
Hack or Hype? Are you taking part or organising a hackathon to solve problems, or because hackathons make good LinkedIn posts? 

When to Do a Hackathon…

When you have a well-defined challenge that can be accessed quickly:
Hackathons are great for solving problems that can quickly be accessed and lend themselves to quick brainstorming, prototyping, and rough drafts, like building Minimum Viable Products (MVPs) or testing concepts.
When it’s time to pressure-test emerging technologies:
Hackathons provide a fast-paced environment for experimenting with cutting-edge tools or technologies (like AI, blockchain, or IoT). Participants can uncover practical use cases or unexpected limitations that wouldn’t surface in controlled settings.
When you want to introduce new tools or platforms:
Hackathons are a great way to showcase APIs, technologies, or frameworks, helping participants learn through hands-on experimentation.
When you want to safely explore "What If?" scenarios:
Hackathons provide a safe space to test wild ideas or tackle "what if" scenarios without the risk or commitment of full-scale development.
When employees or teams need an energy boost:
A hackathon can re-energise teams stuck in a slump and ignite enthusiasm to tackle wicked challenges.
When you need to shift organisational mindsets:
Hackathons can challenge traditional ways of working, encourage teams to think outside of rigid structures, embrace experimentation, and become more comfortable with ambiguity.
When you want to build a sense of community and collaboration:
Hackathons are excellent for fostering connections across teams, departments, or industries. And across diverse skill sets.
When you want to attract unconventional participants:
Bring fresh perspectives into your industry by inviting participants with varied skill sets and backgrounds perhaps not otherwise exposed or attracted to your industry.
When you want to attract new talent:
Use hackathons to spot emerging talent and creative thinkers who can bring new ideas to your organisation or industry.
When you’re looking to pilot new ways of working:
Use a hackathon to introduce your organisation to fast-paced, agile approaches that may not be part of its usual workflow.
When you want to highlight a specific problem:
Hackathons can draw attention to underexplored challenges and inspire innovative approaches to tackle them, or simply inspire more people to care.
When kickstarting a long-term project:
Hackathons can lay the groundwork for larger initiatives, providing an initial framework or set of ideas to build on later.

When Not to Do a Hackathon…

When the problem requires deep research or expertise:
Hackathons aren’t ideal for tackling highly technical or research-heavy challenges that need extended timelines and specialized resources.
When the challenge doesn’t inspire creativity:
Hackathons thrive on excitement and creative energy. If the challenge is overly technical, mundane, or procedural, it may fail to engage participants, resulting in low-quality outputs.
When there’s no plan / no appetite for post-hackathon follow-up:
If you don’t have a plan, appetite, bandwidth, buy-in or resources to follow-up on the ideas generated, running a hackathon risks wasting both time and goodwill.
When you can’t engage the right participants:
A hackathon needs diversity in skills, perspectives, and expertise. Without this mix, teams may struggle to generate new thinking and innovative solutions.
When resources or time are stretched thin:
Hosting a hackathon during high-stress periods (e.g., end-of-quarter deadlines or student exam periods) can hurt participation and engagement.
When mentors aren’t well-prepared or lack relevant expertise:
Uninformed or uninterested hackathon mentors can frustrate participants, derail discussions, or provide unhelpful advice, reducing the overall quality of the event and ideas.
When there’s no clear incentive to participate:
If participants don’t see personal or professional value in taking part—whether through prizes, networking, or learning opportunities—they might not engage fully or even show up.
When your problem is too vague or broad:
Ambiguity can kill a hackathon. Challenges like "fix sustainability" or "digitise tourism" are too broad and lead to scattered ideas that are hard to execute, and likely not very relevant.
When your problem requires immediate solutions:
Hackathons are great for sparking ideas, but not for emergencies. If you need a solution that can be implemented right away, the iterative and experimental nature of hackathons might not be the right fit.
When it’s just for fun:
While hackathons can be fun, hosting one without a meaningful objective risks being seen as a gimmick and people involved may leave feeling their time was wasted.

When to Do a Hackathon: Lessons from XNTC

The experience from the XNTC programme highlighted the unique strengths of hackathons: the two hackathons created a buzz of energy, drew attention to important challenges of the tourism industry and the XNTC programme, and engaged a wide range of participants from diverse backgrounds, but also partners, co-hosts, mentors and judges. The XNTC experiences emphasised that hackathons are a fantastic way to spark creativity, bring new perspectives to the table, and foster collaboration across disciplines. In the X-Nordic Travel Contest, they played a vital role in energising the programme and encouraging innovative thinking.
The experiences of XNTC showed that outcomes from hackathons can vary a lot – by design, and by coincidence. In the case of XNTC, the smaller, more targeted hackathon with one very specific challenge and with professionals of diverse skill sets produced more directly programme and industry relevant and actionable solutions.
While a hackathon might deliver a "golden egg," it takes careful nurturing and ongoing effort to mature these ideas into meaningful outcomes. Ultimately, whether big or small, the success of a hackathon depends on having clear goals, thoughtful planning, and a roadmap for what happens after the final pitch.

YOUR 9 STEP GUIDE TO DESIGN A HACKATHON

As someone who has done more than 200 hackathons around the world, as organiser, mentor, facilitator, Lasse Chor of Happy 42, and part of the XNTC consortia, shares his steps to design a great hackathon:
  1. Prep and Plan

    • Define your purpose: Are you designing a hackathon for innovation, problem solving, piloting new tech, community building …? Choose a clear, focused theme and avoid overly broad ones like “sustainability”.
    • Set the duration: Will your hackathon be 24 hours, 48 hours, or longer? Don’t forget to plan appealing perks like prizes, interesting mentors, cool data sources to keep participants motivated.
  2. Know Your Hackers

    • Decide who you’re targeting: Students – perhaps of specific specialties? Developers? Designers? Entrepreneurs? Or a mix? Make sure your theme is relevant and appealing to them.
    • Set clear eligibility criteria: Outline any required skills (e.g., programming knowledge) to manage expectations.
    • Consider asking for short bios: Ask participants to share their skill sets, backgrounds and interests to help with team formation and mentor pairing.
  3. Engage Mentors and Stakeholders

    • Recruit experienced mentors: They bring valuable expertise to guide teams, keep them on track, and refine ideas. They may also represent industry stakeholders to bridge from hackathon to the real-world application.
    • Partner with industry stakeholders: They ensure the challenges are relevant and can help build connections post-hackathon.
  4. Nail the Logistics

    • Book a suitable venue: Ensure power, Wi-Fi, seating, and rest areas are ready.
    • Get the tech setup right: Charging stations, projectors, and reliable internet are a must.
    • Detail the schedule: Ahead of the hackathon, make sure participants, speakers, experts, judges, mentors all have a detailed schedule with check-ins, work time, pitch times, and judging. Ensure all team members know their roles.
  5. Spread the Word

    • Create branding that stands out: Consider creating a logo, or a noticeable color scheme, or theme that makes your hackathon stand out.
    • Promote widely: Use social media, emails, and partnerships to attract participants. Build a smooth and simple registration portal to make sign-ups easy.
  6. Find a Great Facilitator

    • Choose an experienced hackathon organiser: They will manage the schedule, and when the schedule changes, they will be able to adapt and make sure participants don’t experience any disruptions of change.
    • High energy is key: The facilitator should keep the crowd engaged and maintain momentum.
    • Communication is critical: The facilitator will ensure participants know what’s happening at all times - without adding to the natural (and fun) chaos of a hackathon.
  7. Hackathon Day(s)

    • Stick to your schedule: Make check-ins, workshops, and pitch times clear.
    • Keep the energy up: Announce progress updates and circulate mentors for support and guidance.
    • Less talk, more action: Get people going, help them move forward: It’s about progress, not perfection!
    • Stay adaptable: Things often don’t go as planned, but your job is to make sure participants don’t notice the hiccups.
    • Don’t slack on snacks: Keep participants energised with food, coffee, and plenty of snacks!
  8. Judging and Awards

    • Brief your judges: Make sure they know the judging criteria to ensure relevance in final selection to your initial purpose.
    • Celebrate the effort: Don’t forget a lively awards ceremony and prizes to recognise achievements and motivate participants.
  9. Wrap Up: What Comes Next?

    • Identify the “Move On’ers”: Support teams (not just winners) who want to continue developing their ideas.
    • Share the highlights: Document wins, lessons learned, and key moments to share with stakeholders and mentors.
    • Stay connected: Be sure to thank participants and partners and provide updates on the hackathon’s impact and legacy.
  1. Prep and Plan

    • Define your purpose: Are you designing a hackathon for innovation, problem solving, piloting new tech, community building …? Choose a clear, focused theme and avoid overly broad ones like “sustainability”.
    • Set the duration: Will your hackathon be 24 hours, 48 hours, or longer? Don’t forget to plan appealing perks like prizes, interesting mentors, cool data sources to keep participants motivated.
  2. Know Your Hackers

    • Decide who you’re targeting: Students – perhaps of specific specialties? Developers? Designers? Entrepreneurs? Or a mix? Make sure your theme is relevant and appealing to them.
    • Set clear eligibility criteria: Outline any required skills (e.g., programming knowledge) to manage expectations.
    • Consider asking for short bios: Ask participants to share their skill sets, backgrounds and interests to help with team formation and mentor pairing.
  3. Engage Mentors and Stakeholders

    • Recruit experienced mentors: They bring valuable expertise to guide teams, keep them on track, and refine ideas. They may also represent industry stakeholders to bridge from hackathon to the real-world application.
    • Partner with industry stakeholders: They ensure the challenges are relevant and can help build connections post-hackathon.
  4. Nail the Logistics

    • Book a suitable venue: Ensure power, Wi-Fi, seating, and rest areas are ready.
    • Get the tech setup right: Charging stations, projectors, and reliable internet are a must.
    • Detail the schedule: Ahead of the hackathon, make sure participants, speakers, experts, judges, mentors all have a detailed schedule with check-ins, work time, pitch times, and judging. Ensure all team members know their roles.
  5. Spread the Word

    • Create branding that stands out: Consider creating a logo, or a noticeable color scheme, or theme that makes your hackathon stand out.
    • Promote widely: Use social media, emails, and partnerships to attract participants. Build a smooth and simple registration portal to make sign-ups easy.
  6. Find a Great Facilitator

    • Choose an experienced hackathon organiser: They will manage the schedule, and when the schedule changes, they will be able to adapt and make sure participants don’t experience any disruptions of change.
    • High energy is key: The facilitator should keep the crowd engaged and maintain momentum.
    • Communication is critical: The facilitator will ensure participants know what’s happening at all times - without adding to the natural (and fun) chaos of a hackathon.
  7. Hackathon Day(s)

    • Stick to your schedule: Make check-ins, workshops, and pitch times clear.
    • Keep the energy up: Announce progress updates and circulate mentors for support and guidance.
    • Less talk, more action: Get people going, help them move forward: It’s about progress, not perfection!
    • Stay adaptable: Things often don’t go as planned, but your job is to make sure participants don’t notice the hiccups.
    • Don’t slack on snacks: Keep participants energised with food, coffee, and plenty of snacks!
  8. Judging and Awards

    • Brief your judges: Make sure they know the judging criteria to ensure relevance in final selection to your initial purpose.
    • Celebrate the effort: Don’t forget a lively awards ceremony and prizes to recognise achievements and motivate participants.
  9. Wrap Up: What Comes Next?

    • Identify the “Move On’ers”: Support teams (not just winners) who want to continue developing their ideas.
    • Share the highlights: Document wins, lessons learned, and key moments to share with stakeholders and mentors.
    • Stay connected: Be sure to thank participants and partners and provide updates on the hackathon’s impact and legacy.

GREAT TOOLS FOR YOUR HACKATHON SUCCESS

Whether you’re organising your first hackathon or diving in as a participant, these productivity boosters, development essentials, and free, open-source tools will help you collaborate, create, and deliver your best hacks.

HackMIT Hackathon Tools (https://code.hackmit.org/)

A brilliant list of great open-source tools for hackathon coordinators and attendees.

ngrok (https://ngrok.com/)

A reverse tunnel. Run a server locally in any language and give it a public domain. Good for testing and demoing.

Notion (https://www.notion.com/)

Notion is an all-in-one productivity tool that combines note-taking, task management, databases, and collaboration features to streamline personal and team workflows.

Midjourney (https://www.midjourney.com/­home)

High-quality, creative images from text prompts, great for rapid prototyping, visual storytelling, and creating design assets to enhance project presentations.

Vagrant (https://www.vagrantup.com/)

Create and configure lightweight, reproducible, and portable development environments. Don't mess up your dev box by installing all kinds of stuff that might conflict with your existing dev setup. Instead use dev environments like Vagrant or Docker.

Homebrew (mac) (https://brew.sh/)

Homebrew is the missing package manager for OSX. It installs the stuff you need that Apple didn't install.

Origami (mac) (https://origami.design/)

Origami is a free tool for prototyping. It allows designers to rapidly build and share interactive interfaces.

Google Drive

Use Google Drive as a communication and organisational tool to keep the team on the same page. Don't bother emailing or dropboxing.

Pitcherific (https://pitcherific.com/)

Pitcherific helps in preparing and rehearsing pitches, so you don't have to be all shaky on stage.

Canva (https://www.canva.com/)

Canva is a free-to-use online graphic design tool. Use it to create social media posts for your hackathon, prepare pitches, posters, videos, logos and more.
See many more tools on: https://nyhackathons.com/­tools/

A TALE OF TWO (VERY DIFFERENT) XNTC HACKATHONS

We have already heard that one superpower of hackathons is their adaptable character – they can take many shapes and forms. And it so happens that the two hackathons of the XNTC programme played out in strikingly different ways: One focused on student exploration, the other on targeted business outcomes. Here’s what we learned from both…

XNTC Hackathon #1: Student Creativity in Action

XNTC joined forces with Aarhus University and the Municipality of Syddjurs to host a hackathon for over 160 students and industry stakeholders. The purpose was to harness student creativity and fresh thinking, applied to tourism industry challenges.
Students received challenges that among others related to challenges of tourism & hospitality in relation to hyper-local food sourcing and production, and related to seasonal challenges of accommodation, especially in relation to generating a sustainable business and steady workforce.
Students worked in multidisciplinary teams to develop ideas to address the challenges, and the final concept included everything from branding campaigns to new concepts for visitor experiences, co-operative models for sustainable food practices, and more.
Key Lessons Learned for XNTC: The hackathon showcased the energy and creativity that student-led innovation can bring to tourism challenges. At the same time, while the ideas were compelling, many of them remained highly localised, limiting their scalability across the Nordic region—an essential focus for XNTC.
In XNTC, a key lesson was to define even more clearly scalability objectives and criteria to underline the cross-Nordic relevance and priority of this programme’s purpose.
Why It Worked: This hackathon successfully bridged the gap between university and industry, engaging students in meaningful problem-solving and bringing fresh energy to tourism industry challenges. While the solutions may not have had immediate cross-Nordic applicability, the event demonstrated the value of broad collaboration and the potential for hackathons to surface new ideas and expose students to tourism as an appealing field of innovation and future work.

XNTC Hackathon #2:  Business Hacks for Real-World Impact

XNTC partnered with Iceland Tourism Cluster and KLAK – Icelandic Startups to host a hackathon in Reykjavik, bringing together approx. 20 participants with expertise spanning AI and tech, hospitality and tourism, design, and environment.
The hackathon was kick-started by Iceland’s Minister of the Ministry of Higher Education, Science and Innovation, underlining the potential of hackathons to really put a topic on the broader agenda and generate both awareness and attention.
For this hackathon, participants were asked to adopt AI and smart technologies to solve challenges relating to sustainable business models, as well as work force & seasonality.
The winning team, Snotra, developed an AI-driven SaaS platform designed to simplify and streamline sustainability reporting for tourism businesses. Their solution directly addressed the EU’s Corporate Sustainability Reporting Directive, offering a practical way for businesses to meet regulatory requirements.
Key Lessons Learned for XNTC: Including Artificial Intelligence and smart technologies as part of the hackathon theme and challenge likely attracted a different audience and contributed to the diverse skill sets represented in the hackathon. It introduced tourism as a playing field to test new technology. There was also a prize announced beforehand, which may have further supported professionals in investing their sparetime and weekend in participating.
After the hackathon, the process was also very well defined. The winning idea was focused on a follow-up design sprint to further refine the idea, focused on customer development, user interviews, competitor analysis and product idea adjustments. This was further support with input and perspectives from Nordic Standard for Sustainability Reporting (NSRS) and potential customers.
Why It Worked: The themes of this hackathon – tourism, sustainability, AI & smart tech – combined with the promise of a prize, attracted participants with a diverse and interesting mix of skills and expertise. The follow-up sprint ensured the idea wasn’t left to stagnate but was pushed forward with guidance from industry standards and customer insights.
See more about the further testing with the winning idea, Snotra, in Chapter 5.
Show up. Just go. Even if you don’t think you have anything to contribute, you never know what might happen. The first time I attended a hackathon, I simply showed up, and it turned out my knowledge aligned perfectly with the solution we developed. When I went to the XNTC hackathon I told my wife I wasn’t sure why I was going!
– in conversation with Vicente Carro, hackathon winner, Snotra. Read the full interview here.
Photo: Faarehyrden v-Darewhan Amin

IDEAS THAT LAST: A HACKATHON SUCCESS STORY

In conversation with Mathias Mølgaard, CEO & Co-founder of Storyhunt
Not all hackathon stories end when the event does. Some ideas take root and grow into real-world success stories. The journey of Storyhunt began in 2018 when two students at the IT University of Copenhagen joined a hackathon, organised by Wonderful Copenhagen, armed with a vague idea and an eagerness to explore its potential.
Their idea evolved into Storyhunt, a self-guided audio app designed to help travelers discover hidden gems, learn about local life, and dive into the historical parts of a destination — all at their own pace (see more https://www.storyhunt.io/en).
While not part of the XNTC hackathons, we have included the Storyhunt journey to illustrate how hackathons can indeed develop ideas with lasting potential and become viable businesses. This case highlights the kind of long-term impact a hackathon can support when opportunity, connections and follow-through come together.
We spoke with Mathias Mølgaard, CEO and Co-founder, to explore their path from hackathon concept to thriving business.
What inspired you to take part in a hackathon?
We had an idea for a product and saw the hackathon as a good chance to test it out. The panel of judges included some influential people, like representatives from Copenhagen Municipality, which we knew might end up being interesting and important for us. It was good exposure to engage with decision-makers directly. We also wanted to find another team member.
So, you already had an established idea when you joined the hackathon?
We started with a vague idea: A gamified experience for locals to unlock stories around the city. We weren’t sure about the business model, but since we both have a technical background, we began building to see if we could apply this technology to the tourism sector.
The hackathon was tourism-focused, and our product morphed into spreading tourism flows of people. While that wasn’t our initial goal, we realised our product idea could actually fit this context well. It was a fun challenge, even though we didn’t know much about the tourism industry at the time.
How did the hackathon shape your journey in the tourism industry?
First things first, we learned there were far more stakeholders involved than we initially anticipated! The political elements like distributing travelers across the city as I mentioned before. We didn’t realise how much of a priority this was for the municipality. At the end of the hackathon, every team had to present their idea.
Despite coming in third place, someone from the Copenhagen Municipality recognised the potential of our idea and suggested a way to align it with their goals, such as using digital technologies to create engaging experiences that nudge travelers towards less-visited areas of the city. This became part of shaping our product development, like incorporating routes instead of just a collection of stories on a map.
What was it like collaborating with the Municipality?
It was super helpful! They had a deep understanding of travel behaviour, which we lacked. It was a symbiotic relationship in this sense – we brought the technology, and they contributed with insights about travelers. 
What were the biggest challenges in transitioning from a hackathon to an actual startup?
It was a quite a gradual process. We were still attending IT University every day, so we had the advantage of student grants (SU), and an environment filled with like-minded people. I actually think universities are really good environments for this, like a kind of startup incubator. 
Our first customer was Copenhagen Municipality – a contact we made from attending the hackathon, as I previously mentioned. And then followed the destination organisations (DMOs). So, once we finished our studies, we could go full-time. A big moment was when the municipality created a promotional video trailer for us. It showcased our app and the walking tours, which gave us something really valuable to present to other destinations. That video was an important resource for growing our business.
What makes a hackathon successful?
The host needs to have a clear goal, but saying that, it should also be vague enough to allow participants to interpret it creatively. Go crazy for 48 hours, leave room for personal ideas…
The panel of judges included some influential people, like representatives from Copenhagen Municipality, which we knew might end up being interesting and important for us. It was good exposure to engage with decisionmakers directly.
Mathias Mølgaard, CEO & Co-founder of Storyhunt
How has it been working with the tourism industry?
The tourism industry is quite old-school. Many organisations barely use AI, even though there’s so much potential to optimise their operations. There’s resistance to change, partly because the average age in these organisations is high and change management can be challenging. 
My impression is that younger people in the industry often see the potential of AI, but struggle to convince their seniors. It can be frustrating to push for innovation in an industry that prefers doing things the way they’ve always been done.
What advice would you give to someone considering joining a hackathon?
Hackathons are a great way to test ideas, meet people, and gain exposure to an industry. Even if you don’t win, the connections and learnings can be invaluable. That’s what happened to us – you never know who you’ll meet or what opportunities will come out of it. 

SO, ARE HACKATHONS THE RIGHT TOOL?

As the XNTC experience and Storyhunt’s journey show, hackathons can bring together the right mix of energy, fresh perspectives, and opportunities for real feedback.
Hackathons can be a challenging fit for time-limited innovation processes that require solutions ready to hit the ground running. Their open, fast-paced, and often messy nature tends to produce early-stage concepts that still need significant refinement before they’re ready for real-world testing. Additionally, the teams formed around these ideas are often newly assembled and may require time to solidify and collaborate effectively. Without a strong framework for post-hackathon development, even promising ideas can stagnate.
Before deciding to host or participate in a hackathon, ask yourself:
Does your challenge need an injection of fresh energy or perspectives?
Do you have a clear plan for what happens to ideas after the event?
Do you – or partners - have the flexibility, resources, and time to nurture early-stage concepts that still need development?
Hackathons may not deliver fully developed solutions, but they can still play a crucial role in setting ideas on a path to real-world impact. When paired with a clear purpose and robust post-event support, they offer more than just a burst of energy — they can provide the spark that drives long-term innovation forward.