|
Closing
We try to keep the closing simple and serious. Simple in that there are no formal presentations and speeches. But serious, for this is the time for announcing commitments, next steps, and observations about what the event has meant. The closing event is best conducted in a circle with no "head table." Start anywhere, and go around the circle allowing each participant, who wants to, the opportunity to say what was of significance and what they propose to do. But do make it clear that nobody has to say anything. In very large groups, hearing from everybody is obviously impossible, but two or three folks may be asked to volunteer.
Formal Reports
The formal report-out session has apparently become a fixture of conference life. However, we find it to be boring and generally non-productive. There is never enough time for each group to say all they wanted to, and if sufficient time is allocated, the majority of conference participants are uninterested at any given time. As an alternative, we recommend using a simple word processing system, a computer conferencing system, or both.
In a recent conference 200 participants created 65 task force reports (a total of 200 pages) which were available as the participants left the conference. Mechanically, all that is required is a bank of computers (low-powered laptops will do) and a request to each group organizer to enter the results of their deliberations into the system. They can either type it in themselves, or for the "non-typables," a small group of secretaries will do the job. We print out each report as it is entered and hang it on the wall, providing an ongoing, real-time record of the discussions. The obvious advantage here is that participants find out what is happening, as it is happening, rather than waiting until the end when it is too late. Of course, having the proceedings at the end of conference, rather than six months later, is a pleasant and positive surprise.
Meals
You will notice that meals are not listed on the agenda, nor are there any coffee breaks. The reason is quite simple: once the conference starts to operate in small groups, there is usually never a time when something of substance is not going on. And in accord with the Third Principle, it will take place in its own time. All of this creates a small, but not insoluble, problem for such things as meals and coffee-breaks. Our solution has been to have coffee and other refreshments available in the main meeting room, so people partake when they are ready. No need for the whole group to get into lockstep, and stop an important discussion just because it is coffee-break time. Likewise with meals. We suggest buffets, open and available over a several hour period, so people can eat when they want to. There are two exceptions to the flexible meal/coffee-break schedule: an opening dinner if there is one, and dinner on the last night.
The whole point is that the pacing and timing of the conference must be determined by the needs of the group and its learning process, and not by the requirements of the kitchen.
by Harrison Owen
Excerpted from A Brief User's Guide to Open Space Technology, by Harrison Owen
http://www.openspaceworld.com/users_guide.htm
A complete description of the method and the theory behind it can be found by reading Harrison Owen's book,
"Open Space Technology: A User's Guide" -- Berrett-Koehler, publishers, San Francisco.
This book can be ordered for a slight discount through the Open Space Institute of the US.
Contact them at: http://www.openspaceworld.org/wiki/wiki/wiki.cgi?BooksAndVideos
Reproduction and distribution of these pages are encouraged -- however, copies may not be sold --
and please cite the source. Feel free to contact me if you have any questions: lisaheft@openingspace.net
|