[seism]

Kudos on the idea, and for reaching out here! I build open source tools for hackathons, something I posted about here a few days ago. Your question is a great one, because small private events are not really addressed well by the typical guidance for large (100+) event organizers. Let me (with a little help from my fine-tuned assistant) give it a try:

Do: communicate the objectives and rules clearly (e.g. Gantt chart the timeline), encourage a diverse mix (friends and family, also to boost the audience), provide necessary resources for ideation (from high quality moderation kits to healthy snacks and water), allocate time for brainstorming, pitching, voting, and development stages, and ensure there are mentors available (at least people with some prior hackathon experience) to guide the teams. Think about some creative team-building activities.

Don't: overload participants with too many rules, micromanage the teams, celebrate individual achievements over ensuring all participants get something out of it, or make the hackathon too competitive.

In summary: focus on learning, collaboration, and having fun while documenting the process and outcomes for future reference. Especially for that last point, feel free to test Dribdat in our sandbox, or ping me if you want something more robust & private.

Good luck with your event!

[seism]

This article was mentioned in another HN thread, you might find it useful: https://taranjeet.medium.com/experience-organizing-an-intern...