Using a 'Block'
Loomio currently treats a 'block' as a stronger 'no'. When a user blocks a proposal, the group process carries on as if they had simply said 'no'.
@alannakrause suggests:
"I feel the block option is the core of power and effectiveness in consensus groups, and our software should somehow culturally or technically support and illuminate this power to groups who use it. It's a very serious thing to block something, and it should be taken seriously by the software and by the people using the software. There should be consequences for the proposal, like shutting it down, and for the user, like they actually need to leave the group if they stick to their block and the rest of the entire group opts to push the proposal through anyway… "
Some options which have been suggested:
- remove the 'block' option
- give admins the choice about whether their group has a 'block' option, and a choice about whether any subgroups have one
- a 'block' turns the entire pie red (lets members know at a glance that there could serious problems if the proposal is passed without the block being resolved)
- a 'block' pauses the proposal, leaving everyone's position intact, until the objection is resolved in comments, or the proposal closed
- a 'block' closes the current proposal (knowing that it has this effect, a user would be less likely to 'block' as a strong 'no', but it would provide a way to stop a person strongly attached to their proposal from extending it indefinitely while trying to get agreement in comments)
- leave the 'block' option the way it is (the 'Ideas' feature will allow amendments/ other proposals to be offered to keep the process going)
Some Remarks on Consensus by David Graeber
http://occupywallstreet.net/story/some-remarks-consensus
Raphael wrote:
>> Imagine I make the proposal (all is of course exagerated)
“We should make loomio a proprietary software”
Well someone could use block as a big NO, because it's a danger related to the philosophy of the project.
Now I make a decision
“we should keep Loomio open source, even though we could sell it at a very expensive price if it's closed source”
And the suddenly people become greedy and say “no, let's make it closed source, and earn a lot of money, yum!”
What can we do with a big NO? <
I very much agree that a shared understanding of the meaning / use of a ‘block’ is vital - and maybe loomio can help with this. Tricky though because people don’t read instructions and you need to keep it short and sweet.
My idea would be that the effects of using a block might be something automatic and if it was a setting people could choose as they create a new loomio community and in any event well worth walking people through.
For instance you could auto-close the proposal (but you’d need to give people time to discuss and potentially amend things so as to allow the block to be removed).
Perhaps instead of auto-closing you’d make it so the whole circle goes a shade of red - thus signifying that it would in fact fail due to a single block (at the relevant time).
At OWS I remember hearing that people’s understanding of ‘block’ was that if you block it means that your understanding of the issue is that it is sufficiently important to you that should the proposal pass you would leave the group.
Not sure how but maybe that could be something built into the software somehow? (Though it only really works if some mechanism for revised consensus exists).
Again at OWS I saw that when someone blocked the group would occasionally go into ‘revised’ consensus which involved carefully counting up people that wanted to vote and then requiring a 95% majority to pass a motion despite the block. I guess this was necessary due to the real world and size of the crowd. Some people found it very frustrating that in this particular context the expectation was that the blocker would then leave the group - except they didn’t. But at the time I thought it could be something built in if you were doing this online.
So worth thinking about. In a mature online environment with potentially hundreds or thousands of members I guess these things might be well worth thinking about.
@milesthompsonkapit >> you’d need to give people time to discuss and potentially amend things so as to allow the block to be removed). <<
The proposal text cannot be edited, to avoid people saying 'yes' to one thing, and finding the proposal has changed to something they're not comfortable with by the time it closes. I think if there is any possibility of an amendment helping, the person would be saying 'no', instead of blocking, which is why I propose auto-close instead.
Perhaps instead of auto-closing you’d make it so the whole circle goes a shade of red - thus signifying that it would in fact fail due to a single block (at the relevant time). <<
I do think this makes a lot of sense.
Generally speaking, I am wary of automating or standardising the definition and implementation of any protocols, if it can be avoided.
I understand the desire for clarity, as it makes things more accessible, but leaving it open-ended allows for nuance, individual interpretation, and adaptability. On balance I've found that to be a positive thing. I'm not 100% clear on what problem you're identifying @strypey.
If the Blocking protocol were formalised, I think that would immediately raise the second question of 'who may participate in this decision?'
At the moment, there's not a pressing need to answer that question, and once again, I think that is a good thing.
Keeping things un-standardised forces us to engage as humans and relate to each other as if we were unique and infinitely complex individuals, each with divinely subjective experiences of reality!
yes I agree @richarddbartlett . Talking with users it is clear one of the things people like about Loomio is they can use their current or newly developed group deciion making protocol. As we develop group profile pages we can create space to make this more conscious and people can select from a menu the definition of each button. But for now open and easy to interpret for each group seems very important
I think this will depend on the types of groups that use Loomio in their collaborative decision making processes and for what purposes they use it.
My hope is that there will be continuum of options so that groups using it can make it work for their groups. In saying that it is also important to take into account that in different groups decisions sometimes also have different thresholds to block a proposal.
For example in one national organisation that I work with in the UK there is a 75% threshold to change the constitution.
So I'm for having the options there so groups can make Loomio work for them, rather than having a prescriptive approach decided by the software developers.
How about when a proposal is blocked it turns red and no one else can state a position until it has been removed. Kind of like a 'pause'. This would focus the whole group to resolve this issue in the discussion, and it could not thus get overlooked, or obscured.
I'm not sure what the solution is, but I feel the block option is the core of power and effectiveness in consensus groups, and our software should somehow culturally or technically support and illuminate this power to groups who use it. It's a very serious thing to block something, and it should be taken seriously by the software and by the people using the software. There should be consequences for the proposal, like shutting it down, and for the user, like they actually need to leave the group if they stick to their block and the rest of the entire group opts to push the proposal through anyway...
I don't have a clear idea of the problem we're trying to solve.
@richarddbartlett I think @alannakrause explains the problem to be solved quite nicely. In a nutshell; the software makes no distinction between a ‘no’ and a ‘block’.
I don’t think I’ve ever blocked consensus in person. I can only think of one occasion where I blocked, on an Indymedia email list. Consensus -1 was used, and life went on, but I felt deeply alienated, and eventually I did leave the group. So, I was profoundly disturbed when I found myself blocking in Loomio (slightly less so when others joined me, which is interesting).
In the past, I have made arguments against allowing blocks as part of consensus process at all. After all, if it’s not a situation where I can just avoid helping implement that decision, and my ‘no’ is not enough for the group to want to improve or defer the proposal, I’m probably better off not being part of the group.
However, as I discovered with Indymedia (and later with Oblong), this is one thing in an ephemeral protest group, quite another thing in an organisation I’ve invested a lot of time in, and that I depend on for key resources. IE if that organisation is a business co-operative on which I rely to make a living, leaving on principle has a high cost, and a drift towards dictatorship of the majority is a high risk. In such situations, the opportunity to block is essential, even if it’s rarely or never used, because the risk of a block derailing a project motivates the group to really hear and respect each other (David Graeber writes about this in his ethnography of Direct Action, which I strongly suggest you all read).
For the same reason, I think a block should not be treated simply as a “position”, which makes it tempting to use it as a strong ‘no’. A block should at least pause a proposal, as @aaronthornton suggest, if not close it.
How about this. A 'block' turns the whole pie red (warning: a group member believes core values are at risk of being compromised). It also resets everyone's position (although leaving their position comments intact), and allows the proposal text to be edited.
The discussion thread can then be used to understand the reason for the block, and the proposal text modified. Users can then take a position on the modified proposal.
I guess I haven't perceived the distinction between the no and block to be problematic. It would help me if we could dig into the problem a bit further before suggesting solutions.
p.s. +1 for reading Direct Action - it is incredible.
Problem: 1. People don't understand the difference between 'no' and 'block' 2. There doesn't appear to be a meaningful difference between the two.
Simplest solution that at least addresses the problem somewhat: If one person blocks a proposal the whole pie gets a tinge of red. Groups can make of this what they will.
If, at a later stage, loomio starts to have a list of approved proposals in this group etc, then obviously a proposal with a majority in favor but one 'block' will have been deemed not to have passed.
We address this in Econsensus and in our internal consensus process by using "Danger" rather than "Block". To me, it feels less final and violent than "BLOCK!" so maybe it feels less risky to use, and people occasionally use it in our decision making. This feels different from the UK activist consensus processes I've been involved in which still talked about "blocks" although that felt clumsy and it was rarely used, as people seem to be talking about here.
Some of the terms we are using at the moment ("Concerns", "Danger") come from the Likert scale used in Dotmocracy. We're talking about making it easy for users to redefine the scale we are using so that the terms match their understanding of their decision making process - maybe at first just renaming the terms that we have, and then we've also talked about making it open-ended with as many or few terms as people want, although that is definitely a far-away pipe dream at the moment :-)
We've been discussing the idea that groups will probably always need to define how they will use an online decision making tool, unless it's made totally rigid to one system, and what their own norms are. E.g. how does someone decide a decision is made, what are the norms for deadlines etc. We're currently looking into providing individual org pages where groups can record ad-hoc info like this.
Thanks for the insight @tomlord - we've talked about giving groups the option to configure as many decision buttons as they like, with names, colours and symbols that suit them.
Personally I am quite attached to the idea of having under-specified protocols, as it forces people to engage with each other instead of with a rule book.
Obviously this won't suit some groups. The challenge for us is how do we support groups with stricter protocols, without constraining those that prefer to be more fluid?
plugins
@richarddbartlett
The challenge for us is how do we support groups with stricter protocols, without constraining those that prefer to be more fluid?
With more options in group settings and each group enables what they want and what they don't!
Having options early on the development of Loomio is important. It will significantly increase the number of groups/organisations that can use it out of the box.
:-) where is that edit button? Apologies for the missing 'in'. It should read 'in the development'.
I love the idea of giving groups the option of setting up their own decision-making protocol, both by making the decision-button labels customizable, and by providing a specific space on the Groups page for groups to describe their agreed decision-making processes.
We've already seen a need for this in cases where Councils use Loomio as a public consultation tool - the group members in a case like that are not so much a defined decision-making body as participants in a collaborative discussion where people use Loomio to generate shared understanding and build on each others' ideas rather than making concrete decisions.
I'd be extremely reluctant to go down the track of automating 'blocks' (i.e. disabling voting etc), or anything else that would lock us in to one mode of decision-making.
In my mind, Loomio should strive to be as neutral a space as possible, so diverse groups are free to implement whatever decision-making protocol they want. This is all about lowering the cost of more participatory decision-making so that it becomes an easier option, not pushing people into consensus processes that may or may not be appropriate for them.
PS thanks heaps for sharing that @tomlord!
For anyone that hasn't checked it out already, Tom's amazingly awesome group Aptivate have been working on a really interesting open-source tool called e-Consensus.
Heaps of great process ideas for inspiration!
Stoked to have your expertise in here Tom :)
Thanks @benjaminknightloom :-) I haven't yet looked at Loomio's cool-looking markup text, and I left the links to my world stuff on my post on the introduction page, so thanks for giving me a context :-) And thanks @richarddbartlett for your context - I'm sure there must be loads of previous discussions like this that have gone on that I'm missing, so if I'm saying stuff you already heard then prod me :-) In general is this the place to raise feature suggestions or bugs, or do you use mainly github, or a combo, or something else?
@benjaminknightloom - totally agree about the flexibility and for groups to use things how they want, it's something we've been keen on over here. We have no idea how people will really use our stuff :-) And yes, pieces of a tool like this such as the discussion board in itself can be useful. I'm just about to start an instance of Econsensus for my housing coop of 85 people, where we don't want a discussion board (too many flame wars!) and we DO want to record policy changes that we've made over the years, so we'll be focusing on the decisions, not the discussions. We're agonising a bit over the difficulty of modularising all this stuff so that we can hive off useful pieces like this for re-use, and don't try to create "the one black box system that can do everything", even though we've probably drifted along that route a bit.
On a provocative note, seeing as it's Friday :-) Given that idea of flexibility, I'm curious about the behaviour of Loomio's deadline functionality. It seems that you have to enter a deadline for every proposal, and once it has passed, there is no way to bring a decision back to life. How does that work for your groups? The obvious edge cases I can see are... Do you ever get people who want to have an open ended discussion about something with no fixed deadline? Do conversations finish halfway through sometimes? How do people review decisions they've made - I guess you could create a new one that has precedence, although it might become unclear which decisions are "made" and which are "old" or "we didn't consent to anything here"... Or am I missing some technical tricks? Keen to understand how people use this model.
We are probably flexible to a fault here, in that anyone at any time can say "hang on, that decision is now un-made and it back in the proposal stage again!" This means that it's easy for us to review things in a month and record any changes to previous decisions, if we want to try something out that we're a bit nervous about. And we're far less savvy about deadlines, we display them as a table that can be sorted on, but we don't even send email reminders for them yet. One day...
Have a good weekend!
Does using a block force people to enter a position explaining why they are blocking?
If not, I think it should.
As @strypey has alluded to, the usual understanding in consensus groups is that a block should only be used if "core values are at risk".
Or, as described in the Seed for Change guide to Consensus: "A major objection isn't an 'I don’t really like it' or 'I liked the other idea better'. It is an 'I cannot live with this proposal if it passes, and here is why...!'
Similarly the Open Organization Guide to Consensus Decision making states that "It is acceptable to block a proposal only if you think that it violates the fundamental principles or purposes of being in the group, or if you think it endangers the very existence of the group. "
Sociocracy and Holacracy also take interesting/ potentially useful approaches when it comes to objections/ blocks.
In sociocracy they have to be "argued and paramount objections" which is essentially someone saying "some aspect of me is in danger of going out of safe limits or will be unable to perform as required is this proposal is implemented".
In Holacracy they have specific narrow rules about what counts as a valid objection e.g. will this harm us or move us backwards (not just fail to move us forward), would this objection still exist even if this proposal didn't go ahead? is the proposal safe enough to try?
The similarity between all of the is that you can't just block without good reason, so I think people should be forced to give a reason when blocking, ideally with some explanatory text, e.g. please explain how this propsal will harm/ damage/ is dangerous/ goes against core value/ violates fundamental purpose and principles etc.
Yes I have heard a couple of ideas that would be great treatments for the 'block' card. One is it requires a proposal on how to resolve the block, so you can't block unless you are prepared to put energy into resolution. This stops people taking a blocking role but not involving themselves in constructive resolution. The second is this idea the @josefdaviescoates has raised about having. To enter an explanation. Right now you have the option of explaining and as little as Block in used in Loomio, I have never seen it used without an explanation. I have also seen other people inquire further into the reason for the Block, and in some situations people challenging it didn't feel like a good enough reason to Block. This has given me a really high trust in the overall group and how it responds to Blocks. I think we could make a explanation linked to Blocking, but I am also totally comfortable that discussion are not being damaged and in some instances are being improved by the whole group taking responsibility, seeking clarification or issue ing challenge. Ya for group wisdom. I love it.
The problem as I see it is in the interaction of two aspects of the current UI, each of which was set that way good reasons:
- one proposal per discussion at a time
- uneditable proposal texts
Let's say someone has blocked a proposal, and offered a counter-proposal (as a comment) which is not just an amendment, but incompatible with the current text. In the current UI, the proposal text cannot be edited to make this amendment, even if there is support for it in the comments. If the proposer digs their heels in and refuses to close their proposal early (or even extends it), the group has to talk them around before someone can advance another proposal (or start another discussion or some other work around).
Now this problem may already be solved by the plans the coding group have for the next major roll-out. If would be good for those of us not working from Loomio HQ to have a place we can keep in the loop on feature decisions which have been made by the code team (on Loomio.org somewhere?).
It seems to me that, as it stands, the software allows someone to block progress by refusing to let their failed proposal close, as I did recently on the 'Editing Comments' thread (to my shame). In hindsight, I would rather that @neilmorris pushing the block button had closed my proposal, because I think knowing that would discourage him from saying 'block' if he really just mean 'no'. Then, if he did 'block', I would have found it easier to accept that he was serious about it, and we could have immediately shifted the discussion onto what the conflicting issues were/ are, and what amendments might pass consensus in a future proposal.
It's funny revisiting this thread after talking to @richarddbartlett and @benjaminknightloom about a Pause button, and seeing that this was the behaviour @aaronthornton suggested for the Block. I think if it's worth having a 'block' button (and it may not be), it's worth giving it a distinct effect. I'll admit though, that the problem I'm addressing ('state proposals'?) could also be fixed by other suggestions being discussed in other threads:
- allowing editing of proposals on-the-fly
- allowing multiple proposals on the same discussion
- a draft proposal feature
i saw today a person in my group use veto instead of no, and worry little because i don't know exact what effect can have to proposals.
Is it just simple strong no, or it has any effect like the proposal can't close?
At the moment, what effect a 'block' has on the decision depends on what rules you set as a group. As noted in previous comments, in consensus-based groups, a 'block' is usually a pretty clear sign that either:
* something is very wrong with the proposal
* someone is in the wrong group
* someone in the group is feeling disempowered and is using the 'block' as a defensive tool
some people use it for no reason. instead of no they are using block, and i don't know how the groups are going to work if someone uses block all time.
Will be an option in the future if some groups can disable it???
Why block could be considered as a big NO, choosing no may also be a "danger"" in some situation.
Blocking a poll, imho, is not necessarily saying no...
I see no reason why one proposal at a time per discussion shouldn’t remain, along with having uneditable proposal texts... provided the group has protocols in place and a proposer can remove their proposal before the time is up. To test my views and the group I’ll put a proposal.
As an example, the group could have rules like:
1. If a proposal is blocked it cannot pass.
2. The blocker must offer reasons for the block and a resolution.
Under these circumstances, the blocked proposer has the choice of continuing discussion in the hope of resolution, or ending it so another proposal can come forward. The proposer wants to keep the process alive, not stall it.... so why refuse to close early or extend it, which would be counter-productive? In my view it’s the proposer who should have the right to either continue discussion in hope of resolving the block, or choose to close the proposal, but NOT the blocker. Once closed another proposal can then come forward.
Block remains as is, one proposal at a time remains and uneditable proposal remains
proposal by Dean Satchell Closed Wed 4 Sep 2013 9:48AM
The group itself should make their own rules around “block”. However, only a proposer should be able to close their proposal before it times-out. If the proposer chooses to amend their proposal they can close it and make a new proposal. One proposal at a time provides a linear dialogue and clear decisions and no issues are identified which justify a change to this. This is the most appropriate model identified to date for consensus decision making.
Results
| Results | Option | Votes | % of votes cast | % of eligible voters | |
|---|---|---|---|---|---|
| Agree | 2 | 20 | 0 | ||
| Abstain | 2 | 20 | 0 | ||
| Disagree | 5 | 50 | 1 | ||
| Block | 1 | 10 | 0 | ||
| Not voted | 889 | 99 |
i honestly think we can do better than this
Not only does this proposal have multiple flaws in theory, the practical experience of using Loomio has seen these flaws cause problems in practice.
I think the point of just recording the block & the the why is strong and helps with consultation - I still would like the polling option added...
Else, i am not 100% sure, the software is doing what i would need it to do in a commercial team
Why not have block as an option the proposer can activate or deactivate?
Depending on the issue and desired outcome/action?
I'd suggest the same with abstain.
It should be the "block" as an option the proposer can activate or deactivate, or in the group to decide it!
I think allowing multiple proposals and people providing alternatives would be incredibly useful. I don't agree with giving the proposal creator all the control and the control should live with trained facilitators and admins.
Explication in comments
I'm not sure I understand exactly what's being proposed here. It feels like a few proposals in one.
See my comments
The proposal is that we stick with the status quo, which has produced multiple practical problems, as I've mentioned in comments. If a 'block' doesn't do anything different than a 'no', there's no point having it as an option.
i honestly think we can do better than this
i honestly think we can do better than this
@milesthompsonkapit I agree. Implementing protocols should be part of the development of this software. I'm proposing a starting point for discussion and to identify the real issues for development. In my view introducing “Ideas” will improve the collaboration/consensus toolbox dramatically from this starting point.
Will be an option in the future if some groups can disable it
I hope so. Having a 'block' option (whatever it does) is useful for a tight group who are agreeing on a course of action to take together. Removing the 'block' button would be the simplest way to make a decision-making group into a consultation group (which the Loomio Community is meant to be, for example).
The proposer wants to keep the process alive, not stall it
In practice, this is not what happens. Despite the best of intentions, it's all too easy for the proposer to become attached to keeping their proposal alive, regardless of its effect on the process. I've done this, and I've seen other users do it on numerous occasions.
Also, as @christaklis points out, a 'block' which has no immediate effect is used too lightly. I've also seen this happen a lot, particularly by people who are new to consensus process, and don't really understand the tradition of what a 'block' means.
The proposer wants to keep the process alive, not stall it
In practice, this is not what happens. Despite the best of intentions, it's all too easy for the proposer to become attached to keeping their proposal alive, regardless of its effect on the process. I've done this, and I've seen other users do it on numerous occasions.
Also, as @christaklis points out, a 'block' which has no immediate effect is used too lightly. I've also seen this happen a lot, particularly by people who are new to consensus process, and don't really understand the tradition of what a 'block' means.
If the 'block' has no immediate effect - even as mild as turning the whole pie red - it might as well be removed from the app.
I just used a block for the first time on Loomio, and possibly the first time ever. I can't help but think that if someone feels so strongly about their objection that they 'block' instead of just saying 'no', that is the end of the proposal in its current form. Perhaps the system should auto-close the proposal, so a new one can be created which may have some chance of passing consensus?