Blog Post: Sneak peek into the future of Loomio
Check out the latest blog post: Sneak peek into the future of Loomio.
Inspiring mockups of the future of Loomio! What do you think?
Hi @olivermintersolvol - that's an interesting idea. The thing is, Loomio isn't really designed as a majority rules voting app. There are plenty of other apps that do that. Loomio is designed to work on the principle that groups can work together to co-create better solutions together, meaning the majority needs to take into consideration why the minority is nor agreeing, and work together with them to come up with a better proposal that addresses their issues. Not everyone participates in every decision often times, because people chose their own level of engagement and therefore stakeholding. How does all of this mesh with how your group is using Loomio? We're keen for people to use the tool in unexpected ways, so we can learn how to make it more useful, while still holding on to our philosophy that collaboration is a lot more than voting and going with a majority, but requires a lot of back and forth sometimes to get to something approaching consensus.
yes - we are 'kind of' addressing all those concerns already... we are finding it very important to try and let our system be fair and representative and we are reading everybodys reasons for and against etc.. Recently we are coming to a concensus on the fact that we need to have a "minimum" number of members that have "stated their position" in order for us to percieve that particaular issue as being a fair representation of the members opinions. Atm we are "kind of" agreeing on a minimum of 60-70%. As i'm sure you are aware youself - it takes alot of time to present arguments and understand eachother and then come to some sort of concensus. We are ALL very aware within our own party that we don't want a hierarchical structure and that we all want to try to learn to understand eachothers DIFFERENT points of view. All the above is occurring as we use loomio to SELF-ORGANISE not really neccesarily to use loomio as a demo for the SOL Parliamentary Voting App. Its just that at the moment we can't find anyone with software for that purpose and we are still fairly unorganised as Party - like we haven't got to the stage of paying someone to make our app for us.
These are some profound questions about group dynamics and collaborative decision making - I think we're all on this learning journey together! Keep us posted about what you discover. Meanwhile, I can advise you just come to an agreement in your group about decision making protocols, like how many people need to state their position for a proposal to be valid, and then use "cultural technology" (as in, an understanding of how things are done in your group that's shared) to enact it. The software will never keep up with how fast groups learn about how they want to work! There are a lot of potential workarounds... like if a proposal is about to close but less than the agreed % of people have participated, someone could block it as invalid.
+1000 "Loomio isn’t really designed as a majority rules voting app."
I think the app should keep un-protocolized enough for each group to decide how will transfer the web result into a legitimate decision. That means less explained the buttons are, more possibilities. (Like in the case mentioned in the last comment, someone can actually block and explain the reason is poor participation.)
But it could help something in the small text below the graph like:
10% of members stated their position (10/100)
5% agree | 5% abstain | 0% block | 90% n/a
(Meaning not applicable or no answer)
(In spanish and catalan parlamients they call this "to abstain" (not voting), while the web abstention is a "blank vote")
If it helps: In my opinion and experience outside loomio, horizontal-assambleary-consensus-based groups can decide in it's first stages different levels of % to legitimate a decision. For example, changing "the big principles" or making concrete important actions need 100% active consensus (that meen, all "yes" ¡explained one per one! Regular decisions for the main group (general assembly) could be legitimated by a sum of 100% between yes (with no need to argue) + active abstention (need reason) and a minimum participation (lets say 51%). Subgroups (temporary workrgoups and stable comissions) are automomous, so they decide themselves its own decision protocols internally (normally the same or similar), their decisions are presented to the main group and are considered "accepted" without any participation needs, but with the block possibility as a veto for anyone.
In this case, a "no" is not like a veto, but its useful, it means something like "we need to work it more", and it should be accompanied with at least a proposal to solve it, while a veto is something like stop it! waste of time! against principles! etc
Ah! But even in that kind of groups you can propose "quick surveys", just to evaluate the opinions and have a general vision before working a consensus. That ones have lots of "yes/no", like in a normal voting system, but the results are always informative, not legitimate decisions.
So different % needed, different rules, while they are known and widely accepted, in loomio you can combine all of them in the same group!
We have always wanted Loomio to be as "agnostic" as possible, so that groups can define for themselves what decision making protocols to use. I guess we think that no matter what we designed, we'd never be as smart as all our users and the creative things they come up with, and the diverse circumstances they are in that we can't even imagine. So the idea is to keep it as simple as possible, and let groups adapt it to their needs.
However, I would argue for Loomio to be "subtly opinionated" - meaning while it doesn't tell you how to operate explicitly, it does "nudge" you to be more collaborative and approach consensus where possible. A good example of this is when a proposal finishes with 51% yes and 49% no, that's not the end of the discussion but only the beginning, because pretty much half the group is unhappy, and in that instance I would guess the group could find a much smarter solution somehow.
For me, a "no" means "we can do better". A proposal failing is not a failure for the group, but a success. It means the issues at hand are becoming clear, and the group is building the shared understanding it requires to do problem solving together.
@zombilechuck I think I have agreed with every single thing you've posted since you got here!
Re: 'quick surveys' - imagine if this "add comment" box had another option "add survey", which would inject a really lightweight polling system into the flow of the discussion. It wouldn't have the weight of a binding decision, but it could be a really useful way to gauge support for a range of options, in the process of getting to a decision.
@alannakrause. Keep it "agnostic" (great word for un-protocolized, neutral) and with the UX as simple as possible force to discard the majority of new features (sadly, even though they are great ideas) An equilibrium between simplicity and more options need to be found. That is the major error, in my opinion, in lorea's n-1.cc
@richarddbartlett In that sense, I'm not sure if the "quick survey" is adding "good or bad" complexity in the route map. We should pay attention on how people uses limited options to add funcionalities being creative (and without coding!). For example, in twitter, people asks for little surveys/votations in a tweet:
"Do you think we should do this? RT yes / FAV no"
It's awesome.
So, maybe the like button just need a dislike button, with a small +1 -1 count for each comment. That's a really lightweight polling system.
By the way, I remember dislike buttons were often used before facebook's possitiveness dictatorship XD
@jonlemmon might have some interesting reflections on this discussion.
Again, you're absolutely right @zombilechuck - we have discussed ideas like that. It's always challenging to add useful functionality without overcomplicating it.
I am working for SENATOR ONLINE an Australian political party which uses the concept of DIRECT DEMOCRACY. We are using Loomio atm to self-organise as a party. One thing that is missing from the Loomio application atm is that you don't automatically calculate the end vote in a %. You only calculate the % of members that have stated their position (very useful i think) but then u only display the end result in a pie graph and i am having to use a calculator to tally up what the majority vote actually was. So maybe this could be changed in the future to make it easier for us?