[OSList] Swarmwise; how to organise community like a Wave Riding Pirate

[Lucas Cioffi via OSList]

Hello Thomas,

"Consensus by veto" means anything that is not vetoed is treated as
consensus.  The occupy movement made decisions this way.  People could give
several hand signals to indicate their sentiment when someone else was
talking without having to talk over them.  Here's a list on Wikipedia of Occupy
movement's and signals
<http://en.wikipedia.org/wiki/Occupy_movement_hand_signals>.

You'll see a hand signal for "hard block" which means the listener is
hearing something morally objectionable (i.e. they are vetoing it).  By
defining consensus as "Not morally objectionable" (i.e. not vetoed) the
Occupy Movement was able to approve more member actions/initiatives than if
they went with "universally agreed upon" as their definition of consensus,
because their members were eclectic and unlikely to agree 100% on
everything.

I witnessed that OccupyDC's Facilitation Committee would change the
operational definition of consensus as the months went by so that even 1 or
2 vetoes were still seen as consensus when they wanted to have fewer
roadblocks from their own members.  So the veto number is variable as a
facilitation technique.
-- 
Lucas Cioffi
Co-Founder, QiqoChat.com <http://qiqochat.com/>
Charlottesville, VA
917-528-1831





On Thu, Oct 16, 2014 at 8:32 AM, Thomas Perret via OSList <
oslist at lists.openspacetech.org> wrote:

> Thanks John, great. I read your notes and this one raised a question:
>
> "for necessary decisions (e.g. directing group resources), 'consensus' by
> veto is better than democratic decision-making by majority vote"
>
> What do you/the book mean by "consensus by veto" here?
>
> Thomas
>
>
> On Oct 16, 2014, at 3:51 AM, John Baxter via OSList <
> oslist at lists.openspacetech.org> wrote:
>
> Hello Wave Riders
>
> I've just finished reading Swarmwise, the tactical manual for organising
> community like a Pirate (i.e. Sweden's Pirate Party).
>
> Open Space methods are threaded through it, both overtly and implicitly.
> I thought it was an excellent vindication of the hunch that Open Space can
> be applied in very specific ways to processes much bigger than single
> events.
>
> I did have an initial reaction to how strong the influence of the
> individual leader-champion is.  But I came to the conclusion that sort of
> leadership fits the given objectives, and is no different than the sponsor
> setting the topic in OST.
> So a heads up, you may have the same averse reaction to ego-centric
> language that I did... but please forgive it in order to see the wisdom
> within.
>
> Recommended reading for all Wave Riders: Swarmwise
> <http://falkvinge.net/2013/02/14/swarmwise-the-tactical-manual-to-changing-the-world-chapter-one/>
> .
>
> Also if of interest, my notes
> <http://www.evernote.com/shard/s133/sh/265720ee-aa87-4377-9508-d191d48a966a/3ad0177a6c8434e45420dba77f54ff61>
>  (*not a permalink*)
>
> ​Cheers​
>
> *John Baxter*
> *​Co​Create Adelaide Facilitator, Director of Realise consultancy*
> CoCreateADL.com​ <http://cocreateadl.com/localgov%E2%80%8B> |
> jsbaxter.com.au <http://www.jsbaxter.com.au/>
> 0405 447 829
> ​ | ​
> @jsbaxter_ <http://twitter.com/jsbaxter_>
>
>  _______________________________________________
> OSList mailing list
> To post send emails to OSList at lists.openspacetech.org
> To unsubscribe send an email to OSList-leave at lists.openspacetech.org
> To subscribe or manage your subscription click below:
> http://lists.openspacetech.org/listinfo.cgi/oslist-openspacetech.org
>
>
>
> _______________________________________________
> OSList mailing list
> To post send emails to OSList at lists.openspacetech.org
> To unsubscribe send an email to OSList-leave at lists.openspacetech.org
> To subscribe or manage your subscription click below:
> http://lists.openspacetech.org/listinfo.cgi/oslist-openspacetech.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openspacetech.org/pipermail/oslist-openspacetech.org/attachments/20141016/2444e1e8/attachment-0004.htm>