Greetings from Germany! I'm contributing with
yunity.org, a project aiming to release a multi-sharing and saving
platform. Adjectives describing this wonderful group of humans are not limited to: distributed, pluralistic, epicurist, practically moneyless, nomadic, unincorporated and anarchic. That might sound a bit chaotic. It is.
Without elected delegates or a 'judiciary' function (read: enforcement) and with 'legislative' and 'executive' functions evenly shared by everyone, people have to want to do things. What about when contributors disagree? This is the type of gig that you might expect to go down the
(unanimous) consensus/voting-with-veto/leave-no-one-behind path or the
autonomous/advice process/I'll-do-what-I-want-I'm-an-anarchist path. However there is exploration between the collectivist and individualist extremes. For the past 6 months we've been trying out Systemic Consensus (originally Austrian [lang:de] '
Systemisches Konsensieren'). In brief,
Ballots accept score votes (cardinal ratings) and always have two control options to make sure everyone has an option they can accept, these are:
- 'The passive solution' - maintain the status quo (details case dependent)
- 'Further solutions/repeat cycle' - essentially 'None of the above'. The vote is rescheduled for some future time and there is a return to forming more proposals.
Score voting proceeds in a negative fashion - voters score options from 'accept' (0) to 'fully resist' (n, usually 10 in our case). The option with least votes (the least resisted/most accepted option) is selected. In the case of a tie, approval voting or normal score voting can be used.
The rationale for negative voting is that making decisions people aren't happy with is bad because these people,
- may not help → frustration/burn-out
- may actively resist → conflict
- may potentially leave the group → fragmentation
... and it is thus most important to firstly assess how much people don't want to do something, before assessing how much people want to do something.
OK, so there you have it! Now I have been critically thinking about this system for some time with how/what could be made better. However, before I launch into my conclusions and flavor the conversation, I'd be interested to get feedback from people outside this bubble. Thought? Comments? Concerns? Questions? Fire them at me.
Cheers,
Doug
(p.s. I note that this framework was mentioned briefly on this mailing list some years ago. You can take a look at one of the project results here and our most current documentation on the subject here (lang:en))