After the summit, we're going to Oktoberfest! More information in this Facebook event:

https://www.facebook.com/events/281482819003293/

If you need to be added to it, ask me!

Excellent Summit! Thanks and congrats to the team! :)

For those who joined and for those who didn't enjoy

a) Documentation (restitution) --> https://docs.google.com/document/d/119S7jjh7Nz_9gHD08J1qHSQAFYmWdh9lhczQESQTuFY/edit

b) Pictures --> https://www.facebook.com/david.altabev/media_set?set=a.10159328134180361.1073741866.802020360&type=3&pnref=story

:heart: @albertcanigueral

+++ FOLLOWUP REFLECTION +++

Hey everyone, after the Summit we took some time to reflect on the organization and program and also got valuable feedback from you. Here we share with you the most important aspects to learn from:

Organization

• Location: We wanted to create a space for deep connection between people and communities. Choosing a rural place played a big and crucial role in contribution to this aim and should be considered for upcoming summits.
• Food: Covering meals with a full service vegetarian catering was a pretty good thing for us, as it left time to focus on other topics and was compatible for the vast majority. However, we realised that the amount was too much. We did not check the exact amount of food the catering service calculated per person. So it’s useful to really check in detail with the catering provider.
  
• Communication: We tried to keep the touchpoints as simple as possible (loomio for all detailed community communication, strikingly for external communication, billetto for booking process, slack channel #summitmunich17 for questions and individual requests, telegram for confirmed participants). We observed that channels were not used for their given purpose and although we wanted to avoid to fall into push communication mode, there was a request for more push communication. Maybe it could help to clarify the touchpoints and their purpose at the beginning to really operate in pull communication.
• Coordination: The timeframe for booking was used responsibly by the majority although long planning period beforehand did not help to bring people there. Nevertheless there were some bookings really late without prior notification to the organizing team which made coordination more complicated and also caused additional costs. We want to encourage every future participant to handle your coordination responsibly to support the summit organizing teams, for example by submitting registration on time.
• Budget: When we did first calculation draft we took for granted that we won’t have a funding via cobudget (the open bucket was not filled). We missed to communicate again on this issue to find solutions as a community to make it affordable for more people to attend this summit. We were missing a lot of you guys <3

Program:

• Structure: What proved to be good is the balance between covering lots of topics and going deep into real working. Nevertheless time always limits the depth we can take for each topic. Especially because there should always be a buffer left and time for informal interaction. To solve this two ideas came up: One is to dedicate a summit to a specific topic or at least to a limited amount of topics. Another is to organize issue-specific retreats additionally.
• Content: The program seemed to fit pretty much to the needs the community had at that time. To sense & respond to what the community needs at that moment, the usage of the survey sent beforehand as a sensing tool was extremely helpful.
• Methods: Here we want to share 3 learnings with you. First: Many of you were cheering the creative mood board in the beginning and expressed the wish to continue working with such creative methods. Second: Tensions are within our DNA and should get a big space to be transformed into positive energy and actions. To have a big slot already at the first day proved to be good, as it allows flexibility to schedule session for them. Third: We still want to improve on design for different reflection types. This could be solved by recurring sessions on same topics with individual reflection in between to continue to work on it after this kind of breaks.
• Roles & Facilitation: To prepare the program we paired in a core team of two and asked some contributors to be involved to evaluate iterations. We definitely recommend this mode. Additionally, we experimented with distributed facilitation which went pretty well. Nevertheless there is a struggle between roles (participating and facilitating) Distributed facilitation helps in this. But another idea is to get a semi- external facilitator, especially for sessions about tension.

Thanks a lot @saraheisenmann for sharing. I added this notes here https://docs.google.com/document/d/1HbWaNhJ6cLIYyXPCeyCk0SJ5mKg0eFYhS9MlIl7zeRI/edit (OS Global --> 10 OS Summit --> 1 Read First - Resources) :)