[OSList] Questions on continuous Open Space

[Jake Yeager]

Hi everyone!

I am drafting a proposal for a continuous Open Space operating process for
the OD team that I am on. The team is nine people.

I reference Birgitt's article on Wesley Urban Ministries:
https://www.openspaceworld.org/files/tmnfiles/social.htm

I also reference these notes I took on the Youth for Europe case study by
Hans-Georg Wicke:
https://docs.google.com/document/d/1Ft1HL4k3G-zlFOkI8ZQCIKComSXe1eV47iv0yJ8OySU/edit?usp=sharing
<https://docs.google.com/document/d/1Ft1HL4k3G-zlFOkI8ZQCIKComSXe1eV47iv0yJ8OySU/edit?usp=sharing>

Some questions I'd love to hear your thoughts on:

   - Within a continuous Open Space container, do you think that all
   meetings among the group should be announced to everyone? That is, should
   everyone be invited to every meeting? What happens if two people just want
   to have coffee and catch-up? In the Youth for Europe case study, the
   convener of the meeting determined whom to invite, which might not be
   everyone. It's like a mini-Open Space, rather than a meeting within an Open
   Space. But it can also get cliquish that way, and it seems less transparent.
   - Is it beneficial to have a theme? It doesn't seem like either
   organization had a theme in the case studies for the overall Open Space.
   Perhaps their purpose was their theme... In Youth for Europe, there was a
   theme for individual meetings, i.e., the mini-Open Spaces.
   - Any suggestions on how to handle push notification overload? So many
   meetings might start getting called that people's inboxes are stuffed, and
   they tone out.

I am pretty sure I'll have more questions later. :D

Thanks ahead of time!

All the best,
Jake
________________

When the mind is quiet, the sun of your heart will shine once again, and
you will be free of problems.
 - Robert Adams <http://www.robert-adams.info/>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openspacetech.org/pipermail/oslist-openspacetech.org/attachments/20200608/ba61d8e0/attachment.html>