Game Arts Curators Kit

User Tools

Site Tools

Trace:
lessons

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
lessons [2021/04/23 14:04]
admin 		lessons [2021/06/01 10:33] (current)
joseluis [LESSONS]
Line 4: Line 4:
  
  
----- +==== Document the experience =====
- +
-**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, this is the main or relevant 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 :-D) +
- +
----- +
- +
-=== Document the experience ====+
  
 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?  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? 
Line 16: Line 10:
 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//". 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//".
  
-=== Document the audience ===+==== Document the audience ====
 When documenting a performance, audience documentation is paramount, document their reactions at the time of the performance but also their impressions once the performance is over. This helps future historians to understand how a work was received, what values it affected, and give them a better perception of what the synchronic audience valued and prioritized. When documenting a performance, audience documentation is paramount, document their reactions at the time of the performance but also their impressions once the performance is over. This helps future historians to understand how a work was received, what values it affected, and give them a better perception of what the synchronic audience valued and prioritized.
  
Line 22: Line 16:
  
 Jose Luis Pacheco Boscan Jose Luis Pacheco Boscan
 +
 Rene G. Cepeda Rene G. Cepeda
  
lessons.1619204696.txt.gz · Last modified: 2021/04/23 14:04 by admin

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki