Whether you’re gearing up for the Global Game Jam, our Summer Jam, or a random weekend itch.io challenge, game jams are the beating heart of the indie dev community.
They are chaotic, exhausting, and incredibly rewarding. But if you’ve never done one or if your last jam ended in a burnout induced pile of broken code you might be wondering how to actually get the most out of the experience.
So to discuss it in great detail, OGDA teamed up with the Indie Innovators to discuss the trials and tribulations of participating in a Game Jam. Listen to Vanessa Devine and James Smith (both OGDA EiRs & Founders) give a breakdown of why you should be jamming, and how to prepare so you actually cross the finish line.
A big thank you to Indie Innovators for hosting the interview and arranging the session.
What Are Game Jams Actually Good For?
It’s easy to look at a 48-hour or week-long timeline and think, “I can’t make a real game in that time.” You’re right. You usually can’t. But that’s not the point. Game jams are the ultimate sandbox for:
Failing Fast: Have a weird idea for a gravity-inverting puzzle mechanic? A jam is the perfect, low-stakes environment to see if it’s actually fun. If it fails, you only lost a weekend.
Building Your Portfolio: For students and juniors, shipping anything is better than having a folder full of half-finished, multi-year dream projects. Jams give you concrete, playable links to put on your resume.
Finding Your “Squad”: As we always say: Jam before you marry. Jams are the ultimate test of team dynamics. You will learn very quickly who communicates well, who handles stress, and who you want to build a studio with in the future.
Learning a New Tool: Always wanted to try Godot? Want to learn a new audio mixing tool? A jam forces you to learn by doing, with a hard deadline to keep you focused.
Jam before you marry. Jams are the ultimate test of team dynamics.
Game Jam Prep: Insights from Indie Innovators
To help you get ready for your next jam, we collaborated with our friends over at Indie Innovators to break down the essential prep steps.
Watch the full video collaboration here: Surviving a Game Jam with Indie Innovators
If you don’t have time to watch the full breakdown, here are our biggest takeaways and notes from the discussion on how to prep like a pro:
1. Update Your Stack Before the Clock Starts
Don’t spend the first 4 hours of a 48-hour jam downloading the latest version of Unity or fighting with your Git repository. Set up your blank project, update your drivers, establish your version control (GitHub, Plastic SCM, etc.), and download your base asset packs on Thursday night.
2. The Rule of Halves (Scope Brutally)
When the theme is announced, you will brainstorm a massive, amazing idea. Cut it in half. Then, when you start coding, cut it in half again. Your goal for a game jam shouldn’t be a polished game; it should be a single, playable Core Loop. Focus on the primary mechanic and make it feel good. Polish comes later if you have time.
3. Define the Done State
Before you write a single line of code, agree with your team on what Done looks like. Is it one playable level? A working main menu and a win state? Agreeing on the finish line prevents feature creep from destroying your weekend.
4. Sleep is a Development Tool
We cannot stress this enough: Do not pull all-nighters. The code you write at 4:00 AM on Sunday will be garbage, and you will spend four hours fixing it on Sunday afternoon. Eat real food, drink water, and sleep. You will work faster and make better decisions.
Your goal for a game jam shouldn’t be a polished game; it should be a single, playable Core Loop.
Ready to Jam?
Game jams are about community, creativity, and the sheer joy of making something from nothing.
Keep an eye on the OGDA Discord and ogda.ca for announcements about upcoming jams.