Code
Ship real internal capabilities in two focused days. Not slides, not prototypes that die.
Internal · October 19–20 · Flight deck open
GO7 Hackathon 2026The Future of Travel Techbuilt toCode
Fasten your seatbelts. We are cleared for takeoff.
Gate · GO7-H26Open
To come on board to our hackathon, click here!
Board now
Flight GO7-HACK · Cleared for takeoff
Scroll for flight itinerary
◆Think small enough to ship◆Useful enough to matter◆Production-ready by Day 2◆Cross-team encouraged◆Live demos over slides◆3 projects in real use◆Think small enough to ship◆Useful enough to matter◆Production-ready by Day 2◆Cross-team encouraged◆Live demos over slides◆3 projects in real use
Flight itinerary
Event details
Passenger manifest
GO7 Hackathon
Flight GO7-H26
BOARDING OPEN
DEPDATE
October 19–20
GATEKICKOFF
Day 1 · 09:00
ETADEMOS
Day 2 · 16:30
ARRDESTINATION
Internal tools · GO7
TEAM SIZE 3–4 · CROSS-TEAM ENCOURAGED
Seat assignment: your squad
Innovate
Solve one clearly defined internal problem with clever, practical solutions people will use.
Fly High
Think small enough to ship. Useful enough to matter. Aim for production-ready by Day 2.
Ground control · HQ
The terminal is open
One mission across GO7 worldwide. Two days to ship what lasts.
Brand
Flight mark
Cleared for takeoff
HQ ops
Crew assembly
Cross-team. Face-to-face. Shipping together.
GO7 worldwide·Focus days · shared energy · real demos
Operating principle
Think small enough to ship.Useful enough to matter.
01 · Mission brief
Objective
Two-day internal hackathon focused on improving how we work internally. The goal is to build real, usable capabilities, not customer-facing features.
Where possible, solutions should be production-ready and available for actual use by the end of the hackathon.
Think small enough to ship. Useful enough to matter.
Operating principle
One problem
Teams focus on a single, clearly defined internal challenge.
Squads of 3–4
Cross-team collaboration is encouraged across GO7.
Deep focus
Roadmap work and meetings minimized. Emergencies excepted.
02 · Flight rules
Format
Departures · Internal ops
- DatesOctober 19–20
- Team size3–4 people
- CollaborationCross-team collaboration is encouraged
- FocusTeams should focus on one clearly defined internal problem
- Default modeRegular roadmap work and meetings should be minimized during the two days
- ExceptionProduction / customer emergencies are the exception
03 · Flight path
Process
Four stages from announcement to demos. Keep Confluence submissions intentionally short, and scope ruthlessly.
Stage 01
Announcement
Send a company-wide kickoff communication covering purpose, dates, problem types, team expectations, process, and definition of success.
- Purpose of the hackathon
- Dates
- What type of problems we are looking to solve
- Team size and expectations
- Process and timeline
- Definition of success
Stage 02
Team Formation & Idea Collection
Employees form teams of 3–4 people and submit their ideas. Each team fills the Hackathon Confluence page.
- Team members
- Problem
- Proposed solution
- Who will use it
- Expected impact
- What will be delivered by the end of Day 2
Keep this intentionally short.
Stage 03
Idea Approval
Short meeting with each team before the hackathon.
- Validate that the problem is relevant
- Make sure the scope is achievable within two days
- Identify dependencies/blockers in advance
- Push teams to reduce scope where necessary
- Agree on what "done" means
Output: Approved scope documented on the team's Confluence page.
Stage 04
Hackathon
Two days of focused build: kickoff, deep work, submit, demo, celebrate.
Day 1
- 09:00: Short kickoff
- Full day of focused work
Day 2
- Continue development
- 16:00: Hands off / submission deadline
- 16:30: Team demos
- ~17:30: Wrap-up, winners & drinks/food
04 · Showcase
Demo
Approximately 5 minutes per team
- 1Briefly explain the problem
- 2Live demo of the solution
- 3Explain the expected impact
- 4What happens next / who will use it
Prefer live demos over presentations.
05 · Judging
Evaluation
Keep judging simple. Five clear lenses.
Impact
Does it solve a meaningful internal problem?
Usability
Can people actually use it?
Completeness
How close is it to production / real usage?
Efficiency
Does it save time, effort, or cost?
Creativity
Is there something clever or innovative about the solution?
06 · Success criteria
The hackathon is not the end goal
Success means that we produce capabilities that continue to be used after the event.
Suggested target
At least 3 hackathon projects in real internal use within two weeks.
This brief stays at this level. Two additional artifacts come later: the kickoff announcement, and the short Confluence idea-submission template.
Gate · GO7-H26Open
To come on board to our hackathon, click here!
Board now
Flight GO7-HACK · Cleared for takeoff