Running a 100% Fish hackathon
An agenda for a weekend hackathon, built on the Iceland Ocean Cluster’s own hackathons, with the key points for each step, dos and don’ts, and ways to get strangers working together.
A hackathon brings people who may never have met together around a real challenge, and in a weekend turns their ideas into working prototypes. This template is built on the agendas and reports of the Iceland Ocean Cluster’s own events, above all the Copernicus Ocean Hackathons of 2025 and 2026 and Hack the Ocean in 2023. Adapt the times, the challenge and the partners to your own ecosystem; where it says IOC, read your own cluster or organizing team.
What IOC hackathons share
Every IOC hackathon follows the same five-beat arc: inspire, form teams, build with mentors, pitch, then a path forward. The differences are in how the inspiration is delivered, through talks or site visits, and in how long the build lasts.
- Inspiration comes from industry, not the organizers. Both Copernicus editions opened with 10-minute talks from member companies; Hack the Ocean replaced the talks with a day of site visits.
- A single, framed challenge. Hack the Ocean used one “How might we…” question; Copernicus 2025 used four themes (pollution, overfishing, climate and biodiversity) and a hard rule: use at least one Copernicus Marine product.
- Data or tools onboarding on day 1. Mercator Ocean walked the teams through the data before work started.
- Mentors in a scheduled window, not just “available”: a two-hour slot on the Saturday in 2025.
- Skills timed to need: vibe coding (AI-assisted coding) early, to prototype fast; an investor’s perspective midway; pitch training on the final morning.
- Pitches to a mixed jury of the IOC, a partner, an investor and an industry operator, with published criteria.
- A next step for winners: cash, plus startup space at the Ocean Cluster House, mentoring hours and follow-up support.
- Food and social time on the agenda, from Friday pizza to meals all weekend.
A weekend agenda
A Friday-evening-to-Sunday format, built on the timings of the 2025 and 2026 Copernicus hackathons. The step numbers match the key points below. Times are a starting point: swap in a site-visit morning (step 2b) when the theme is physical, as Hack the Ocean did.
| Step | When | What | Length | Led by |
|---|---|---|---|---|
| Before the weekend | ||||
| 0 | 4–8 weeks before | Pre-event: challenge owners, the call, selection, a kick-off session | — | IOC team |
| Friday evening | ||||
| 1 | 17:00 | Welcome and the challenge | 10 min | IOC host |
| 2 | 17:10 | Inspiration talks from industry | 4 × 10 min | Member companies |
| 2b | Friday or Saturday morning (optional) | Site visits or a field trip | 3–4 h | Host companies |
| 3 | 17:50 | Data and tools onboarding | 15–30 min | Data or tech partner |
| 4 | 18:20 | Idea pitches and team formation | 40 min | Facilitator |
| 5 | 19:00 | Food and networking; the teams start | — | — |
| Saturday | ||||
| 6 | 09:00 | Morning check-in, and a skills workshop (for example, vibe coding) | 15 min + 60 min | Facilitator, partner |
| 7 | 10:15 | Build block 1 | about 2.5 h | Teams |
| 8 | 13:00 | Mentor sessions, in booked slots | 2 h | Mentors |
| 9 | 15:00 | An investor’s perspective | 30 min | Investor (for example, Blue Nova) |
| 10 | 15:30 | Build block 2, and optional evening work | to 22:00 | Teams |
| Sunday | ||||
| 11 | 09:30 | Pitch training | 30–45 min | Pitch coach |
| 12 | 10:30 | Final build and pitch rehearsal | about 3 h | Teams, mentors |
| 13 | 14:00 | Final pitches to the jury | 5 min + 3 min of questions per team | Jury |
| 14 | 15:30 | Jury deliberation, with networking for the audience | 30 min | Jury |
| 15 | 16:00 | Awards and next steps | 30 min | IOC and partners |
| After the weekend | ||||
| 16 | 1–4 weeks after | Follow-up: a report, support for the winners, a debrief with partners | — | IOC team |
For a two-day format, merge steps 6 to 10 into day 1 and steps 11 to 15 into day 2. The 2025 report recommends the opposite where possible: one extra day, so that teams reach working prototypes.
Key points for each step
What each step should cover. Points marked IOC are drawn from past IOC events; the rest are recommended additions.
- Pre-eventStep 0
- Recruit challenge owners among member companies, and get one real problem from each (IOC).
- Write the challenge as one “How might we…” question plus three or four sub-themes (IOC: Hack the Ocean, Copernicus 2025).
- Run a short kick-off, or a “Co-Location Coffee” with experts, to sharpen the question (IOC: August 2023).
- Decide on in-person only: the 2025 hybrid lost all but one online team (IOC).
- Publish the prizes, eligibility, team size (four) and judging criteria with the call, and send the full schedule to registrants.
- Book mentors and the jury in named slots; confirm food, rooms and late-evening access.
- Welcome and the challengeStep 1
- Why this challenge matters to your blue economy, in numbers.
- The rules: the required data or tool, team size, deadlines, and what “done” looks like (a working prototype and a pitch).
- The judging criteria up front, the prizes, and what happens to winners afterwards.
- Logistics: wifi, rooms, meals, opening hours, who to ask.
- Inspiration talksStep 2
- Three or four member companies, 10 minutes each, each framed as “here is a problem we actually have” (IOC: Snjallgögn, GreenFish, Hefring Marine, Oceans of Data).
- Speakers stay on as mentors afterwards, so that teams can follow up.
- The site-visit variant (2b): three or four stops showing working examples, ending with a short workshop on site (IOC: Hack the Ocean).
- Data and tools onboardingStep 3
- Where the data lives, how to access it, and one worked example (IOC: Mercator Ocean).
- A shared starter kit: links, notebooks, sample datasets, API keys.
- Team formationStep 4
- 60-second idea pitches from anyone with an idea; the others join by interest (IOC: Hack the Ocean grouped people by topic).
- Aim to mix technical and business skills in each team; the facilitator places solo registrants.
- Each team registers its name, challenge and one-line idea before leaving.
- Skills workshopStep 6
- Rapid prototyping or AI-assisted coding, so that non-coders can build (IOC: Blue Nova Ventures’ vibe-coding workshop, 2026).
- Short and hands-on: teams apply it to their own idea straight away.
- Build blocksSteps 7, 10, 12
- Clear milestones: the problem validated, the data working, a prototype that can be demonstrated, the pitch drafted.
- The facilitator walks the room at least twice a day to unblock teams.
- Mentor sessionsStep 8
- Bookable 15–20 minute slots for each team, on using the data, refining the concept and technical problems (IOC: 2025 report).
- A mix of profiles: data, an industry operator, business models, an investor.
- An investor’s perspectiveStep 9
- What makes an idea fundable in the blue economy, and what investors want to see in a pitch (IOC: the 2025 and 2026 programs).
- Practical, and tied to the teams’ own projects.
- Pitch trainingStep 11
- A structure: problem, solution, data used, demo, business case, team, ask (IOC: Startup Iceland, Justine Vanhalst).
- One timed rehearsal for each team, with feedback, before the final.
- Final pitchesStep 13
- A fixed time for each team, strictly kept; open to the public and partners (IOC: Hack the Ocean’s open session).
- A jury of four or five, mixing the IOC, a funder or partner, an investor and an operator (IOC: the 2023 panel).
- A scoring sheet with the published criteria: pitch quality, use of data, fit to the challenge, innovation, feasibility, team (IOC: the 2025 criteria).
- Record the pitches, for an after-movie and for partners (IOC: 2023 videos).
- Awards and next stepsStep 15
- Cash prizes, plus something that continues the work: startup space, mentoring hours, follow-up support (IOC: all editions).
- Tell every team, not only the winners, how you can keep supporting them.
- A group photo; thank the mentors, jury and funders by name.
- Follow-upStep 16
- Report to the funder: sign-ups, withdrawals, teams, outcomes and lessons (IOC: the 2025 FPCUP report).
- Meet the winners within two weeks, and connect promising teams to investor days.
- Share an after-movie and press coverage (IOC: RÚV covered 2025).
Dos and don’ts
Drawn from the lessons of IOC hackathons and from research on thousands of hackathon projects, which finds that most projects stop within days: what you design before and after the weekend matters as much as the weekend itself.
Do
- Let real challenge owners write the challenges: processors, ports and research institutes, each with a problem and the data or samples that go with it.
- Frame one question, a “How might we…” with three or four sub-themes, and publish the rules and judging criteria with the call.
- Prepare teams and data before day 1, with a data-access webinar and a team-matching session the week before.
- Build mixed-skill teams on purpose: a coder, someone from fisheries or aquaculture, and a business mind.
- Book mentors in named slots, and time the skills workshops to when teams need them.
- Teach the business side too, such as a value-per-kg or unit-economics session, since by-product ideas live or die on volume and price.
- Give winners a next step that continues the work: a pilot with the challenge owner’s side stream or data, startup space, mentoring, a slot at an investor day.
Don’t
- Don’t go hybrid. In 2025, all but one of the online teams dropped out; hold it in person.
- Don’t squeeze the build. Where you can, add a day so that teams reach working prototypes, as the 2025 report recommends.
- Don’t reward all-nighters. A frantic all-nighter can lower the odds of a project surviving; protect sleep.
- Don’t leave mentors just “available”. Book them in a window, with a slot for each team.
- Don’t let the organizers do all the inspiring. Inspiration comes from industry: real problems from member companies, or site visits.
- Don’t let talks or pitches overrun. Timebox everything with a visible timer, and keep each team’s pitch time strictly.
- Don’t stop at the awards. Meet the winners within two weeks, and tell every team how you can keep supporting them.
Getting strangers to work together
A hackathon often starts with a room full of strangers. The methods that work best get everyone talking in small groups early, use a question that matters, and let people build something together quickly.
Facilitator tips
- Talk less, structure more: the facilitator moderates the process, not the content.
- Start in pairs, not plenary: silent thinking time first, then pairs, so that quieter people and non-native speakers get heard.
- Make the question visible: write the session’s question large on the wall and on each table.
- Timebox everything with a visible timer, and announce “2 minutes left”.
- Capture as you go, on tablecloths, sticky notes or with a graphic recorder, so that ideas don’t evaporate.
- End with a harvest and a next step: what we heard, who owns what, when we meet again.
Six tried-and-tested methods
| Method | How it works | Time | Best for | Ocean twist |
|---|---|---|---|---|
| Impromptu networking | Three rounds of pair conversations with new partners on two set questions, such as “What challenge do you bring? What do you hope to get?” | 15–20 min | Opening any event; surfacing shared challenges | “What part of the fish or the ocean do you work with, and what’s wasted?” |
| 1-2-4-All | 1 minute alone, 2 minutes in pairs, 4 minutes in fours, then share the best idea with everyone | 12–15 min | Generating ideas where everyone’s voice counts | Use it in place of “Any questions?” after a challenge owner’s talk |
| World Café | Tables of four to eight; three 20-minute rounds; people rotate while a host stays, ideas are written on the tablecloths, then a whole-group harvest | 60–120 min | Co-creation workshops on shared priorities, like Blue Visions | One table for each side stream or sector |
| The marshmallow challenge | Teams build the tallest free-standing tower they can from 20 sticks of spaghetti, a yard each of tape and string, and a marshmallow, in 18 minutes | 30 min, with the debrief | The first hour of a hackathon: the debrief teaches fast prototyping | Debrief: “What’s the marshmallow in your project?” |
| Personal values map | Each person sketches their name, why they care about the ocean, their skills and one wish; pairs swap and introduce each other | 20 min | Teams of strangers finding shared values | Add “my first memory of the sea” |
| Human spectrogram | Read out a statement (“Zero-waste seafood is possible within 10 years”); people line up from agree to disagree, then talk to someone at the other end | 10–15 min | Surfacing views and starting a debate fast | Use 100% Fish or multi-use statements |
Impromptu networking and 1-2-4-All are Liberating Structures. The personal values map and the human spectrogram are widely used formats with many variants rather than single published methods; adapt them freely.
Forming teams of strangers
- Interest-based clustering: put sector or challenge signs around the room; people stand by the one they care about, then mix skills inside each group (the IOC did this at Hack the Ocean).
- Skills badges: colored stickers for coder, designer, scientist, business and industry; each team needs at least three colors.
- A team charter in 10 minutes: a name, a shared goal, each person’s role, how we decide, how we’ll know we’re done.
- A quick win first: give each new team a 20-minute micro-task, such as sketching the user of their idea, before the big build, so that they learn to work together early.
Checklist
The 2025 Copernicus report names two fixes: go in-person only, and add a day so that teams reach working prototypes. Of 60 sign-ups, 4 withdrew and 31 presented; of the 8 online sign-ups, one team presented.
- Challenge owners and the “How might we…” question confirmed
- The required data or tool named, with a starter kit ready
- Prizes that include a continuation (space, mentoring, follow-up support)
- Judging criteria published with the call
- The in-person format, and room access to late evening, confirmed
- Mentor slots booked by name and time
- The skills workshop, investor talk and pitch coach booked
- A jury of four or five, with mixed profiles, confirmed
- Meals planned for every day
- A photographer or video, for the pitches and an after-movie
- A press contact (for example, RÚV) briefed
- A funder report template ready: sign-ups, withdrawals, teams, winners, lessons
- A follow-up meeting with the winners booked within two weeks
Sources
From the Iceland Ocean Cluster’s IOC Events & 100% Toolkit (October 2026), which brings together the IOC’s event pages and reports and research on hackathons.
- Copernicus Ocean Hackathon 2026, Ocean Cluster House: event page; recap
- Copernicus Ocean Hackathon 2025, Reykjavík: event page; timeline; final report; EU Space news
- Hack the Ocean: Multi-use at sea, 2023: IOC page; Nordic Innovation; VASEK
- Co-Location Coffee, 2023: outcomes report
- Research on what makes hackathon projects continue: IEEE overview; Wits study; ICTworks; University of Tartu; ECIE paper
- Other ocean hackathons: Ocean Hackathon® 2026; Copernicus Marine Hackathon 2026
- Facilitation: t2informatik; Liberating Structures: 1-2-4-All; World Café; the marshmallow challenge