← All articles

Play and creative projects

A First-Timer’s Guide to a Community Game Jam

Join a community game jam with a small idea, a useful role, and a plan for sharing and playtesting together.

Illustration for a first-timer’s guide to a community game jam: three neighbors sketching and playtesting a small tabletop game with paper cards and a die.

Find a jam that fits your time and interests

A game jam is a short, organized event where people make a game around a shared idea or set of limits. Some groups make digital games; others make card, board, or tabletop games. The event page should say which format it supports, how long the jam runs, where people meet, and whether teams form on site. Read those details before signing up, especially if you need to plan travel, costs, food, or time away from other commitments.

You do not have to arrive with a complete concept or a ready-made team. If joining people you do not know feels easier with some structure, ask the organizer how introductions and team choices work. If you would rather bring a friend, check that the format allows it. A jam is a shared activity, but every local group has its own schedule and expectations, so ask about anything the listing leaves unclear.

Choose a way to contribute

Game-making involves more than programming. Depending on the project, a team may need someone to suggest rules, write a short story, draw a card, gather sound effects, make a paper prototype, or watch people try the first version. Global Game Jam welcomes different backgrounds and describes non-digital games as part of the format. Ask the host which kinds of projects are welcome at your event, then offer a task that matches what you can do or want to learn.

At the start, share how long you can stay, what you would like to try, and any tools or materials you can bring. You can ask the group to agree on roles together. If the first task does not fit, say so early and see whether there is another useful job. Clear expectations help people collaborate without assuming that everyone has the same experience, equipment, or free time.

Keep the first version small

A theme can spark dozens of ideas, but a jam has a fixed end. Start with the smallest version someone else can play: one clear goal, a few simple choices, and a way to know when a turn or round is over. For example, a team could test a tiny card game with paper scraps before making finished artwork or adding more rules. The early version is there to answer a question, not to look polished.

Agree on a check-in time and what you hope to have ready by then. If the core idea is still hard to explain, simplify it before adding features. Cutting an idea can be part of making progress; a compact game that people can understand and try gives the team something concrete to improve together.

Playtest as a conversation

Invite someone outside the team to try the current version while you watch. Let them make choices before explaining every detail. Notice where they pause, what they misunderstand, and which parts make them want another turn. Then ask a few specific questions, such as what they expected to happen or what felt unclear. A playtest is for learning how the game works for another person, not proving that the idea was already right.

Take feedback as information, not a verdict on the person who designed the game. You may choose to keep a surprising part, change a confusing rule, or leave a suggestion for later. Making and testing a small thing together offers natural chances to listen, offer ideas, and share decisions, even when teammates have different strengths.

Plan a finish that includes people

Check how the event closes: there may be short demonstrations, a shared play session, or a place to post project notes. Ask teammates before sharing their names, art, or contact details beyond the group, and follow the organizer’s instructions for anything you submit. If a project remains unfinished, write down what works, what still needs attention, and who wants to continue. A jam prototype does not need to become a commercial game to make the time worthwhile.

Schedule breaks and agree on a stopping time that works for the team. You can leave when you planned, watch the other demos, or ask when the group meets again. A successful first jam can mean trying a role, learning how another person approaches a problem, or enjoying a few rounds of a game your group made together. Let the project stay small enough for everyone to take part.

Meet someone new on HMU