Loomio

Has Loomio.org defined what a decision is for the app?

Ben Burton PublicSeen by 213

It may seem simple, but if we are creating a tool that helps us make decisions, what a decision is should be really well defined so we can assess if the tool is achieving its goals. If this isn't well defined then feature creep and other distractions could prevent the development of the tool from being as effective as possible.

Chad Mitchell

"a conclusion or resolution reached after consideration."

Ben Burton

Is that an official stance of the group building the tool or just copied from a dictionary? @chadmitchell

Chad Mitchell

Dictionary. Wanted to initiate with a concrete example.

Ben Burton

Ah, thanks. The dictionary definition is obviously where most people will start, but I see the need for something more clearly defined.

Chad Mitchell

That makes sense. Could start with a general discussion within the framework of social choice theory (http://ai.stanford.edu/~epacuit/classes/esslli/logsoc.html). Basically, how do we agree on a system that aggregates the individual choices of a population, allowing room for diversity and experimentation while also maintaining social order.

jacopo

is necessary to develop different model of decisions and each model will have a different format.

Ben Burton

@jacopo Could you elaborate? I have one method in mind but it's based on just a small bit of research/reading. I hadn't ever thought about multiple models before.

Alanna Irving

I think this is a really interesting discussion and worth digging into here. At the same time, I think each group will define for itself what a decision really means for their context. There's so much diversity among Loomio user groups it would be impossible to find one perfect definition. However, I think one thing Loomio could do better is guide groups to have a discussion amongst themselves to clarify what decisions mean in their case. I think just assisting groups to reach more clarity can have a big positive impact, even if each group comes up with its own different answer.

jacopo

The concept is simple, each proposal is generated as a possible solution from a specific problem or need. A model approach a different kind of problem or need. A model is a set of answers to the specifics aspects of the problems/needs, The combined answers form a proposal. When a problem have different solutions is necessary by the community to identify the best of the solution. Loomio at the present time is the answer to a problem with a single proposal with four positions Agree, Abstain, Disagree, Block but only two possible outcome... yes (agree) or no (disagree, block) Loomio simplicity is a strength but at the same time a weakness. A model can help the proposer to better identify the possible answers needed to prepare a proposal. Each answer can be discussed and voted each voted answer become a part of the main proposal.I see it as a loomio mini session within loomio main session.

Ben Burton

@alanna Yes, each group has to decide what their decisions mean for themselves, but that's different than the action of making a decision itself. Loomio as a tool is modeling some form of action that is defined as a decision making process. That model would be great to have explicitly defined.

Ben Burton

@jacopo In a different thread I suggested the ability to vote on "statements of fact" that would be added to a discussion. A group could vote on different facts that become part of the basis for a greater proposal and decision. This sounds a bit like the mini loomio session you mention.

Ben Burton

@alanna Alanna, if no definition has been put in writing, is there by chance a copy of the requirements that were used when initially kicking off the software development? That should have a rough idea of what "decision" meant during the development process. This could be a good starting point.

Greg Cassel

I'm thinking that a decision is a resolution, not necessarily permanent, to identify with one or more ideas. We all experience or 'have' various ideas, which we feel more or less attached to. Decisions are when we consciously resolve or commit to an idea.

I know that's a broad definition, but it seems appropriate to me. One could subcategorize decisions as relating to "identity" or "actions". Crafting a vision statement or group guideline is just as much of a decision as committing to a specific course of action.

Decisions can of course be 'hard' or 'soft', and they can be either personally authoritative (one or more 'bosses') or consensual. They can also be based on hierarchical or non-hierarchical organization.

I think Loomio could be used in most sorts of organizational structure, outside of dictatorships. For instance, it would be useful IMO to groups or subgroups with authoritative bosses/managers who genuinely strive for inclusive decision-making, including discussion and non-binding 'straw polls'. Loomio's great for consensus-developing process, and that's what drew me here. However, I think that a broad, basic concept of 'decision' is suitable for Loomio's goals of user-based design and empowerment.

jacopo

@Ben Yes it sound like, I will extend the ability to vote not only to "statement of fact" but to any arised discussions generated by a specific paragraph in the main proposal.

Greg Cassel

@jacopo Hi, I really like the basic idea of 'statement of fact'. I personally prefer the term 'agreement' to 'statement of fact', so I hope you might consider it.

'Fact' can be a controversial term. 'Agreement', by contrast, can be simply accepted as the basis or premise for further discussion and further agreements. Perhaps a later discussion will amend some agreements, just as the 'facts' in science can evolve over time.

Ben Burton

@jacopo I love the idea of the term “agreement”. The term “Statement of Fact” is a legal term in the United States and I’m not connected to it at all. It’s very dry. Agreement is less formal, more friendly and perhaps more loomio-like. :)

Ben Burton

@gregorycassel The problem I see with an overly broad definition of "decision" is that it's nearly impossible to actually build concrete software that meets the requirements of something overly general.

I think the mechanics of what a decision is (or resolution, whatever term we choose) can be explicitly stated even if the software affords the end users the flexibility to use the software as they see fit.

The mechanics of Loomio right now appear to be a discussion forum with a (fantastic) tool for voting. I feel like that can be refined to a tool that better helps drive a community and/or discussion towards a resolution.

Gray

Meta-observation:

As a strong visual thinker, I see decision making as a coalescence from amorphous chatter to a very specific point of action, from which other paths then become available.

Important not to lose sight that a decision on its own is largely irrelevant. A decision isn't an end point, but rather a portal to a new set of opportunities.

Within that Opportunity Space, iterative coalescence creates more decisions/portals to yet more opportunities.

The aim of any consensus process should be to minimise the friction/static of decision making so maximal energy can be devoted to the 'journey' rather than getting mired down at the waypoints.

Consensus should be one part of the tool-set of the Wayfaring Pathfinder.

Gray

Addendum:

Perhaps part of the role of a consensus tool should include the enablement of visioning future possible pathways beyond the decision point.

Too often I've witnessed consensus processes which had a high attrition rate. Decisions made at cost of personal well being and collective goodwill.

Without the positive energy to move forward, the act of achieving consensus may become terminal.

Ben Burton

@jgrey Yeah, one of the pieces I believe a decision must have is a goal that reached via consensus by the group. This goal would be similar to what you suggest with future possible pathways. A shared goal helps keep a group united and working forward.

Deleted account

Possibly there are multiple of discussions, one for the specific goal and others to allow discussion on the ultimate goal.

jacopo

My previous point where based on methodology, in Airesis we only have problem proposal and solutions, once is voted depending on the legal weight of the constituency can be a law a decision a statement of fact a resolution etc. The specific name should be choosen at the opening by the proposer/relater

Ben Burton

@jameswilson You used the word GOAL. To me, a goal is one of several essential pieces of a decision and I think we need to find a way to get that into Loomio.

Gray

Important to remember that not every decision by a collective is necessarily for the collective.

For example, a collective may decide to allow an individual access to specific collective resources for a personal objective.

While not necessarily sharing that person's objective, they acknowledge the importance of it to them. And agree to assist by collegiately sharing assets/resources.

Important to recognise & allow for individualism, within a collective environment. Collective ≠ Herd

Kurt Brenneman

I must like thinking about decisions about thinking: In my view, an observable decision exists where there is any evidence of action. An action resulting from thoughtful consideration, monetary consideration, or a proposal made for consideration, may indicate motive but it is not the decision, per se. As I understand it, loomio is about aggregating the actions of individuals through an interactive scientific process (beta:) to reach a logical conclusion that remains subject to ongoing revision utilizing the same or improved scientific method… or maybe something like that? --happy thanks and giving all ye weavers!

Alanna Irving

@BenBurton to answer your question, we held this intentional ambiguity right from the beginning for Loomio development - every group will define what a decision means to them differently.

So I'll still stick with my previous comment: I think Loomio could do more to help groups be explicit about how they define a decision for them (with some kind of wizard or help documentation or field you fill out answering that question in your group description), but I think we should not try to define it centrally. We'll never have an answer to suit everyone.

That said, I do think there is some connection to actionable outcomes. I think people are attracted to Loomio because the decision aspect makes it action-oriented, unlike some other discussion or project management tools.

Ben Burton

I'm less worried about what a decision means to any particular group and more interested in understanding the vision of the software. A clarity of vision will help the development group accurately create that vision. To me, software is best developed with clearly articulated requirements.

I certainly agree that one size does not fit all but vague is a concern on the opposite side of the spectrum.

vivien maidaborn

INteresting discussion. The thing I would add is about watching what emerges as an approach to noticing what defines a decision in a group rather than trying to tie it down first. At Loomio we didn't even have a discussion about when is a decision a decision until we noticed a situation where we had different views about that. By then we had a history of successful decisions and the actions that follow them to draw on.

Gray

@vivienmaidaborn Birthing of a community culture via iterative shared experiences and challenges. eg Enspiral's Retreats

Ben Burton

@vivienmaidaborn I would be really interested in a discussion of how we can review the process and pull useful information from the existing examples. I can rely on my own experiences and have my own understanding, but reaching consensus on a definition would be useful.

Searching for Enspiral’s Retreats pulls up a Loomio I don't have access to see.

Gray

Perhaps a starting point would be to self-examine the role of decision making within your own psyche. How do you know when you've made a decision, how often do you unmake? How does the process help you move forward (or not)? What does it feel like?

In many ways, the 'collective' is an aggregation of personal experiences of a shared universality.

Ben Burton

I'm pretty clear on my own definition of a decision. I'm really just interested in the definition that drove the requirements for the software development. I think revisiting and discussing these requirements could help the community make this software even more powerful.

Kurt Brenneman

I am most interested in the number of decisions that are made by unique and returning viewers to not engage, reflected in metrics/analytics: group page, discussion, and proposal views, etc...

Gray

@kurtbrenneman Not quite sure if satirical [ :-) ] in this context, but does raise valuable point that is sometimes overlooked.

Consensus involves a set of individual (collegiate) behaviours & communication skills which may need to be acquired by new users.

When introducing new platforms of interactivity, oft not enough thought is given to training/onboarding people into working with a new skill set (& implicit permissions etc)

Many folk are not accustomed to having a voice, while others talk too loudly & often, without listening.

Important roles for curation by elders etc.

Ben Burton

@jgrey I think the idea of teaching decision making dovetails nicely with @alanna's idea of a wizard to help. More work could be done to help move the process forward for those that aren't well versed in the group decision making dynamic.

Alanna Irving

Have many of you hosted discussions in your Loomio groups along the lines of "What does a decision mean for us?" - how did it go? What does a decision mean in your various groups?

Ben Burton

I'm also interested in how we all define the process of a decision. The group building I've done was before Loomio existed. I love the idea of documenting how people using Loomio define this process.