Hackathon Playbook
# Champions
# Driving Adoption
Step-by-step guide to running an internal Hackathon
September 17, 2025ChatGPT Hackathon template
A hackathon is a structured event where people come together to rapidly brainstorm and prototype ideas in a short time frame. While often associated with software, hackathons can focus on any type of problem-solving. In the context of ChatGPT, it’s an opportunity for teams to explore use cases, test workflows, and experiment with creative applications in a concentrated burst of time.
Remember that a hackathon is not just about what gets built—it’s about sparking new ideas, building confidence with AI, and fostering a culture of experimentation in a fun and exciting way.
Hackathon objectives
- Accelerate learning: Participants quickly build practical skills with ChatGPT by working hands-on. Results may include working GPTs, workflow prototypes, or documented ideas for future initiatives.
- Drive innovation: Hackathons surface new use cases and creative solutions that might not emerge during regular work. A safe, time‑bound environment lowers the barrier to try bold or unconventional ideas.
- Build community: Hackathons connect employees across functions, in a fun, low-stakes environment, creating shared experiences and sparking collaboration.
How to prepare
- Form a planning committee: Include representatives from different functions to ensure smooth preparation and day-of execution. Suggested roles and responsibilities:
Role | Responsibilities |
Facilitator/Organizer | Guides the event, keeps time, runs kickoff and closing, ensures smooth flow of sessions. |
Internal champions / power users | Share expertise, mentor teams, provide quick help with ChatGPT best practices. |
IT support | Ensure tool access, troubleshoot login or technical issues, support integrations and connectivity. |
Judges / Review panel | Evaluate projects, provide feedback, and recognize achievements. Use ChatGPT to create a scoring rubric. |
Participants | Collaborate, brainstorm, build prototypes, and present outcomes. |
- Define hackathon objectives: Clarify if the focus is general learning, prototyping, or producing usable outputs. Document how you will measure success of the Hackathon after the event. >> Brainstorm Hackathon objectives and success metrics
- Create teams: 3–6 participants per team encourages collaboration while staying nimble. When forming teams, consider role and skill diversity—mix technical and non‑technical participants, pair experienced users with beginners, and aim for cross‑functional representation to broaden perspectives. >> Create hackathon teams using ChatGPT user analytics data
- Ensure tool access: Confirm all participants have access to ChatGPT and any relevant collaboration tools.
- Communicate logistics: Share the date, duration, agenda, and expectations in advance. Clarify whether it will be virtual or in-person, outline how teams will be formed, note any resources provided (e.g., food, breakout rooms, templates), and communicate how demos and wrap-ups will be run so participants know what to expect.
- Encourage pre-work: Ask participants to do light preparation ahead of the event—such as reviewing example use cases, exploring ChatGPT basics, or jotting down pain points in their daily work that could inspire projects. This ensures teams arrive with ideas and helps maximize active build time. The OpenAI Academy for Work is a great place to start.
Sample Agenda
Here are common Hackathon formats to consider. When deciding, weigh factors like available time, number of participants, scope of goals, and resources (e.g., space and facilitation).
Format & duration | Logistics & notes | Sample agenda |
1‑hour sprint (60 min) | Great for quick exposure. Focus on a single challenge or brainstorm. Minimal setup needed; often run within a single team. | 0:00–0:10 Kickoff,
0:10–0:40 Brainstorm + build
0:40–0:55 Quick demos
0:55–1:00 Wrap‑up |
Half‑day hackathon (3–4 hrs) | Allows time for brainstorming, building, and short demos. Works well for departments or small groups. | 0:00–0:20 Kickoff
0:20–1:00 Brainstorm ideas
1:00–2:30 Build prototypes
2:30–3:30 demos + feedback |
Full‑day hackathon (6–8 hrs) | Provides space for deeper prototyping. Include structured breaks, kickoff inspiration, and checkpoints. | 0:00–0:30 Kickoff and inspiration sharing
0:30–2:00 Team brainstorming and prototyping
2:00–2:30 Break
2:30–5:00 Build and test 5:00–6:00 Demos,
6:00–6:30 Celebration |
Multi‑day hackathon (2–3 days) | Company‑wide or cross‑team event. Requires more planning: dedicated venue (physical or virtual), meals, facilitator roles, and strong scheduling. | Day 1: Kickoff + Brainstorm/prototype,
Day 2: Continue build + testing
Day 3: Final build + demos + awards |
Outcomes & follow‑up
To wrap up a hackathon effectively, document all outcomes—whether prototypes, proof-of-concepts, reusable prompts, team-specific GPTs, or insights—in a shared space accessible to participants and employees.
Tips for success
- Set clear objectives upfront: Share a defined theme, example challenges, and what success looks like. This avoids confusion or aimless work by giving teams a north star.
- Mix teams intentionally: Combine technical and non-technical participants, pair beginners with advanced users, and aim for role diversity. This prevents frustration from uneven skill levels and sparks more creative outcomes.
- Use milestones and checkpoints: Provide sample agendas, interim goals, and scheduled check-ins. This helps teams manage time effectively and avoids last-minute scrambles.
- Keep energy high: Build in breaks, food, energizers, and recognition moments. This sustains engagement and prevents burnout or drop-off.
Table Of Contents
Popular
Dive in