Client out of control! Need help!

[uwe weissflog]

Chris,
it is my experience that injecting "stuff" from the outside into an Open Space
event disrupts the free flow of thought. Therefor - I would not go along with
the keynote speaker. A possibility (if what this person has to say is of value)
is to let him/her speak in the space between the formal event and the Open Space.
As a sideline, I personally believe that there are no "holes" in an Open Space.
It might look like a hole, but actually it is part the whole thing.

Sometimes we might need to walk away from an opportunity to keep the integrity
of what we stand for.

regards Uwe

On 10/8/98, OSLIST wrote:
>A quick one, I'm not sure it's a problem, but...
>
>I'm preparing for an Open Space at the end of the month
>with a federal government department.  The planning
>committee I'm working with was sold on the idea of
>concluding a three day meeting with one full day in Open
>Space.  They chose a great topic and I'm confident that the
>day will go very well.
>
>The problem is that the committee I'm working with is
>accountable to a manager who distrusts facilitators
>and facilitated meetings of any kind.  (Perfect, thought I.
>Won't be a problem with OS).  The committee sold her on
>the concept, but I'm not sure she's grasped it fully and she
>won't talk to me.
>
>The day in Open Space has a hole in the middle ofit for
>people to eat lunch, continue with their group work, sleep or
>whatever.  The manager has now asked for a keynote
>speaker to be inserted into this "free" spot.  I'm uneasy, but
>thought I'd get some advice.  I've never done it this way
>before, and naturally I'm worried about what this highly
>structured presentation will do to the flow.  Will the group
>recover the momentum after being bored to tears at lunch?
>Should I back out if we can't get the keynote speaker
>cancelled?
>
>Chris
>
>
>
>
>RFC822 header
>-----------------------------------
>Status: U
>Return-Path: <owner-oslist at LISTSERV.IDBSU.EDU>
>Received: from heimdall.sdrc.com (heimdall.sdrc.com [146.122.132.195])
>       by mailhub-cvg.sdrc.com (8.8.8/8.8.5) with ESMTP id SAA06998
>       for <uwe.weissflog at mailhub-cvg.sdrc.com>; Thu, 8 Oct 1998
>18:46:36 -0400 (EDT)
>Received: from listserv.idbsu.edu (listserv.idbsu.edu [132.178.16.100])
>       by heimdall.sdrc.com (8.9.1/8.9.1) with ESMTP id SAA29725
>       for <uwe.weissflog at SDRC.COM>; Thu, 8 Oct 1998 18:46:35 -
>0400 (EDT)
>Received: from listserv.idbsu.edu (listserv.idbsu.edu [132.178.16.100])
>       by listserv.idbsu.edu (8.8.8/8.8.8) with ESMTP id QAA23552;
>       Thu, 8 Oct 1998 16:28:29 -0600
>Received: from LISTSERV.IDBSU.EDU by LISTSERV.IDBSU.EDU
>(LISTSERV-TCP/IP
>          release 1.8c) with spool id 230092 for
>OSLIST at LISTSERV.IDBSU.EDU;
>          Thu, 8 Oct 1998 16:28:28 -0600
>Received: from inac.gc.ca (ISERVER.INAC.GC.CA [198.103.249.251]) by
>          listserv.idbsu.edu (8.8.8/8.8.8) with SMTP id QAA20473 for
>          <OSLIST at LISTSERV.IDBSU.EDU>; Thu, 8 Oct 1998 16:28:26 -
>0600
>Received: from INAC1-Message_Server by inac.gc.ca with
>Novell_GroupWise; Thu,
>          08 Oct 1998 18:27:45 -0400
>X-Mailer: Novell GroupWise 4.1
>Mime-Version: 1.0
>Content-Type: text/plain
>Content-Disposition: inline
>Approved-By:  Chris Corrigan <corriganc at INAC.GC.CA>
>Message-ID:  <s61d0421.019 at inac.gc.ca>
>Date:         Thu, 8 Oct 1998 18:22:39 -0400
>Reply-To: OSLIST <OSLIST at LISTSERV.IDBSU.EDU>
>Sender: OSLIST <OSLIST at LISTSERV.IDBSU.EDU>
>From: Chris Corrigan <corriganc at inac.gc.ca>
>Subject:      Client out of control!  Need help!
>To: OSLIST at LISTSERV.IDBSU.EDU
>
>