Replace this text: somebody will write something nice about LESSONS here! How to you process lessons learned through producing a game exhibition or event? How do you iterate on prior work to avoid repeating mistakes? What are some specific mistakes that can been avoided? What specific big successes are worth sharing? What tips should be provided for a newcomer?

Update 4-22: I'm Jose Luis, I'll just leave this over here, from my own experiences as a software developer and game event organizer, it's the main thing that goes through my mind when I hear someone talking about lessons. Also hoping someone will kindly continue developing the ideas further (Imagine it's like in the hot potato game )

This is an extremely useful and motivational advice for becoming a better event organizer over time. Cover the event as much as you can through photos, videos, interviews, writting, attendee satisfaction forms, and more. This allows you to have some references to compare and some general guidelines of your own experiences. From there, you will be able to notice what went right, what could have gone be better, list any learned lesson, what were the risks or unplanned dificulties and how were they managed?

As humans, it's completely alright to make mistakes, but noticing and measuring how an event's original expectations were fully or partially covered it's what let us enhance our future endeavours as organizers. Having a written compilation of facts and best practices is what is commonly known in Software and Game Development contexts as “Post-Mortem Documentation”.

Add yourself if you wrote something

Add yourself if you edited something