A community campaign hosted by The Jewish Federation of Greater Los Angeles

How to host a Jewish innovation hackathon in your city

A Jewish innovation hackathon brings people together to develop practical responses to community needs. In a concentrated event, participants identify a challenge, form diverse teams, test possible solutions, and present ideas to a panel of community judges. The format borrows the energy of technology hackathons while making room for Jewish learning, relationship building, and long-term communal responsibility.

The strongest events are designed around a real local purpose rather than novelty alone. A city might be seeking better ways to welcome young adults, support isolated seniors, strengthen Jewish education, respond to food insecurity, or create more meaningful connections across congregations and cultural backgrounds. A clear purpose gives participants a useful creative boundary.

The Jewish Federation of Greater Los Angeles’s Next Big Jewish Idea campaign offers a helpful model for community-led problem solving. Its emphasis on submitting, sharing, and voting on ideas shows how a public platform can turn individual creativity into a shared civic process. A local hackathon can apply the same principles at a smaller scale, with transparent criteria and visible follow-through.

Start with a shared community challenge

Before booking a venue or inviting speakers, identify the issue the event should address. Gather input from synagogues, Jewish schools, social service agencies, campus groups, cultural organizations, foundations, and residents who are often left out of planning conversations. Short interviews, listening sessions, and a simple online survey can reveal concerns that leadership groups may not see.

Try to frame the challenge as an opportunity rather than a predetermined solution. “How might we help Jewish families build meaningful connections during busy weeks?” invites broader thinking than “How can we create another family program?” A useful challenge statement should be specific enough to focus the room and open enough to support several types of response.

Set two or three measurable outcomes for the event. These might include producing six tested concepts, recruiting participants from at least five parts of the community, or selecting two ideas for small pilot grants. An outcome such as “generate innovative ideas” is difficult to evaluate. A concrete target helps organizers make decisions about time, staffing, judging, and follow-up.

Keep the connection to Jewish values visible without making the event feel like a lecture. Concepts such as gemilut chasadim, tikkun olam, machloket l’shem shamayim, and hachnasat orchim can guide the work. They offer participants a shared ethical vocabulary while allowing people with different levels of Jewish knowledge to contribute comfortably.

Build a diverse planning team

A successful hackathon depends on planning that begins well before the event. Form a small steering group with authority to make decisions and enough diversity to challenge assumptions. Include a community organizer, a Jewish educator, someone with event-production experience, a participant from the target population, and a person familiar with budgeting or program evaluation.

Recruit participants beyond the usual professional and institutional networks. Young adults, parents, retirees, students, artists, entrepreneurs, educators, social workers, and people who are less connected to formal Jewish life may bring valuable perspectives. Offer a simple registration process, clear accessibility information, and fee waivers or stipends when cost could prevent participation.

Make the invitation describe the work honestly. Participants should know that the event involves listening, collaborative design, rapid prototyping, and public presentation. It is not merely a networking gathering, and it is not a contest in which polished professionals automatically win. Explain that lived experience and curiosity are as important as technical expertise.

Choose a facilitator who can manage energy and disagreement. Jewish communal conversations may involve strong feelings about identity, inclusion, funding, and institutional priorities. The facilitator should establish norms for respectful debate, make room for quieter voices, and intervene when one person or organization begins to dominate. A short opening exercise can help participants practice active listening before teams form.

Design the event around experimentation

A one-day or weekend format works well when the agenda alternates between learning, ideation, testing, and reflection. Begin with a concise briefing on the challenge and the people affected by it. Follow with a participant story, short research presentation, or community data snapshot. Teams should understand the human context before they begin generating concepts.

A practical schedule might include problem exploration, idea generation, team formation, prototype building, feedback rounds, and final presentations. Do not spend the entire event in brainstorming mode. Teams need time to turn an attractive idea into something concrete: a service journey, sample lesson, mobile tool, event model, volunteer pathway, partnership agreement, or first-month pilot.

Jewish practice can shape the rhythm without taking over the program. A brief text study may introduce a question about responsibility or belonging. A communal meal can create informal connection, while a reflective pause gives participants time to consider whose needs remain unrepresented. For family-focused programming, organizers may draw on Jewish mindfulness practices to make the experience calmer, more attentive, and welcoming to different ages.

Every team should have access to basic materials and expert support. Provide large paper, markers, sticky notes, laptops, sample budgets, community demographic information, and a list of relevant organizations. Arrange short mentor sessions with people who understand nonprofit operations, Jewish education, technology, accessibility, fundraising, and the target community. Mentors should challenge assumptions rather than take over the projects.

Create fair criteria and a clear selection process

Participants need to know how their work will be evaluated before they begin. A judging framework can balance community value with feasibility. Useful criteria include the importance of the need, inclusion and accessibility, alignment with Jewish values, originality, evidence of participant input, potential for partnership, affordability, and the likelihood of testing the idea within six months.

Use plain-language scoring descriptions. For example, a high score for feasibility should mean that the team has identified realistic partners, resources, and first steps—not that the idea is already fully funded. If innovation is treated as technological sophistication, low-cost relationship-based ideas may be overlooked. Innovation can mean a new partnership, delivery model, volunteer structure, or way of reaching people.

Evaluation area What judges should look for Evidence teams can provide
Community need A clearly defined issue affecting identifiable people Interviews, survey findings, local data
Jewish purpose A meaningful connection to Jewish values, learning, or communal life Brief explanation, source text, participant insight
Inclusion Access for different ages, abilities, identities, incomes, and backgrounds Accessibility plan, outreach partners
Feasibility A realistic pilot, budget, timeline, and leadership structure Six-month action plan and sample budget
Collaboration Potential to involve institutions or groups that do not usually work together Named partners and shared responsibilities
Learning potential A credible way to test, measure, and improve the concept Pilot metrics, feedback method, revision plan

Avoid asking judges to rely on charisma. Require each team to submit a short written summary before presenting. Give every finalist the same amount of presentation time and the same questions. A mixed judging panel might include a young adult, service provider, educator, funder, community member, and subject expert. Their different perspectives can produce a more balanced decision than a panel made entirely of senior executives.

Consider separating awards by purpose. One prize might recognize the strongest immediate pilot, while another honors the boldest long-term concept or the best cross-community partnership. Small grants, coaching, workspace, or introductions to potential partners may be more useful than a single large prize that leaves other strong ideas without support.

Help teams turn concepts into prototypes

Teams should be formed around the challenge they want to explore, not around preexisting friendships. Ask each participant to share relevant experience, interests, and skills during registration. Organizers can then create groups with a mix of community knowledge, design ability, communication skills, operational experience, and subject expertise.

A prototype should make the idea visible and testable. A team proposing a new intergenerational program might create a sample three-session curriculum, recruitment message, participant journey, and draft budget. A team addressing food insecurity could map a referral process and conduct a role-play with a food pantry, synagogue, and social worker. A team developing a digital resource should sketch the user experience before investing in software.

Insist on contact with intended users during the event whenever possible. Invite parents, teens, older adults, educators, or service recipients to give feedback in short sessions. If direct participation is not possible, provide carefully gathered interviews and observations. Teams should be rewarded for changing their ideas in response to evidence, not for defending their first concept.

Partnerships can extend a hackathon beyond the Jewish communal sector. A Jewish day school exploring service learning, for instance, may learn from public school partnerships that already connect students with local needs and civic institutions. Collaboration with public schools, libraries, universities, food banks, arts groups, or neighborhood organizations can improve reach while preserving a clear Jewish purpose.

Make the final showcase a community moment

The final presentations should be accessible to people who did not attend the full event. Invite families, donors, partner organizations, local officials, educators, and residents who may become users or volunteers. A public showcase builds accountability and helps teams find supporters beyond the judging panel.

Keep presentations focused. Each team can explain the need, describe its proposed response, show the prototype, identify the first pilot site, and request a specific form of support. A short demonstration or participant story is usually more persuasive than a dense slide deck. Offer presentation coaching and accessible formats, including microphones, captions, readable visuals, and interpretation when needed.

Celebrate the work without implying that selection equals success. The event should recognize careful listening, collaborative effort, and useful learning as well as winning concepts. Display all submitted ideas online or in a public gallery when appropriate, with permission from participants. This preserves the broader community conversation and prevents the hackathon from becoming a one-night competition.

Document the process as it happens. Photograph prototypes, collect short participant reflections, and record the judges’ reasoning. Publish a concise event report with the challenge statement, participating groups, selected ideas, funding decisions, and next milestones. Transparency strengthens trust, especially when some worthwhile concepts cannot receive immediate support.

Build a path from ideas to action

The most important work begins after the showcase. Before the event, decide who will contact finalists, manage funds, provide coaching, and report progress. Each selected team should leave with a named sponsor, a modest pilot budget, a timeline, and a clear decision point. Without ownership, even excellent ideas tend to fade as participants return to their regular responsibilities.

Use a staged funding model. An initial microgrant can support user research or a small test. A second payment can follow evidence that the team has recruited participants, secured a partner, or improved the concept. This approach reduces risk and encourages learning before a program expands. It also gives organizers a chance to redirect resources when a promising idea proves impractical.

Define simple measures that reflect the project’s purpose. Attendance alone may not show whether people feel more connected. A team might track repeat participation, new relationships formed, referrals completed, volunteer retention, learning outcomes, or participant confidence. Gather feedback in ways that respect privacy and do not burden people who already have limited time.

Schedule a public progress gathering three or six months later. Teams can share what they tested, what failed, what changed, and what support they need next. Treat failure as useful information when it is documented honestly and achieved through responsible experimentation. A community that learns from pilots will produce better ideas over time than one that only celebrates finished programs.

Practical recommendations for organizers

A citywide Jewish innovation hackathon succeeds when it creates durable relationships as well as promising projects. The event should help people see themselves as contributors to Jewish communal life, whether they work inside an established institution or are participating for the first time. Its greatest outcome may be a new partnership, a stronger sense of belonging, or a practical idea that can be tested quickly.

Begin by convening a small planning circle and writing one clear community challenge. Invite varied voices, design a focused event, and commit resources to what happens afterward. With thoughtful facilitation and transparent follow-through, your city can turn shared Jewish values into experiments that meet real needs and strengthen the future of community life.