For your first game jam, choose one thing the player can do and make that work. A tiny game someone can play is a better learning project than a large design nobody can try.
There is research behind paying attention to scope. A 2019 study by Markus Borg and colleagues, reporting a survey of 198 Global Game Jam participants, described practices including scope management, communication and playtesting. It is a historical participant survey, not evidence that joining a jam guarantees employment.
Write the smallest design
Use this original project card:
The player tries to ___.
They can ___.
The game responds by ___.
The round ends when ___.
We will leave out ___.
For an invented example, the player might sort falling objects into two baskets. You can test that idea with simple shapes before drawing characters, adding a story or composing music.
Agree who owns each small task and where files go. A teammate should be able to open the latest version without guessing which chat attachment is current.
Let someone else play early
Watch a person use the game without your commentary. Do they discover the controls? Can they recognise success or failure? Where do they stop?
Fix the confusing part before adding another feature. Keep a note of what changed and why; it becomes a useful account of your work afterward.
If you join an organised jam, read that event's current participation, submission and asset-use conditions. Do not assume a rule from an old event applies to yours.
Protect time for sleep and your existing commitments. Finishing a learning exercise should not depend on proving how long you can remain awake.
Hustl's belief in work with dignity includes recognising the small contributions inside a team: naming files, testing a build or writing clear instructions. For other ways to record useful experience, see building a work reputation.
End with something playable, a short explanation and a clear record of what you would improve next.