I am struggling with the Loomio Feature discussions, how about you?
Today Rich made the comment to me that my level of engagement in the features discussions indicated I wasn't keeping up. OMG, how embarrassing, someone noticed!
So just to raise this issue abit more broadly, I am not keeping up, should I be? Are you? I am worried we aren't using clean user feedback processes here? Can we stop for a moment on features and focus on preparing for scale?
So really I just what to check in my expereince and see how others are doing too
To be honest the features discussions are way beyond me, they are technically orientated, and feel like people with high tech skills keep comicated the tool in ways pele like me can't keep up with or hope to communicate to anyone else. I am not even sure if I can use what currently exists well. Should I stop trying to track them, just switch off to all this disucssion, or should we improve the process so it is more considered, determined by strategy and takes intra count a broader range of user profiles and views?
Hey Rich, yes I got that but nonetheless it was a great comment cause sent me off on this whole inquiry, I kind off have the sense that I represent more of our users, especially the ones struggling to engage, then the more competent members of the team so on that basis I am reluctant to disengage, but on the other hand.....
There have been a number of feature discussions lately that have led to elegant solutions, and they are proving a good way to engage with our high-tech users (i.e. our contributors), so I wouldn't want to lose that.
However I completely agree that we're failing to engage just about every other user group. So let's identify what we can do to engage them.
We're releasing features twice a month. These features should be announced in the app as they are released, and that information should also go into a cumulative resource.
The Start New Group Wizard and how-it-works page are hints of what that cumulative resource might look like. I'm starting to think this is my new job description...
I have a feeling many users might have an easier time commenting on features we have released that they have gotten a chance to use, rather than abstractly coming up with potential new features or solve hard problems. I think we should continue to let interested technically-minded people hash out new features, since that's been working well so far. But how about a hosted feedback discussion along with our bimonthly feature releases, facilitated in a way that makes it easier for nontechnical people to engage? That way we could reap the benefits of their ideas and improve our features without expecting everything to think like a programmer.
I think it's really good that this has been brought up. To me there are two separate issues here:
- Accessibility of feature discussions
- The strategic priority of the features being discussed
My gut instinct tells me that we shouldn't worry too much about making the feature discussions immediately accessible. I think the way that we're headed with feature development (including mockups and detailed specs before development) will naturally make the feature discussions more accessible, and we can continue to improve this over time.
However, considering the strategic importance of the features being discussed is really important. Our processes around this is something that I've been thinking about for the past few days.
I think we have some defined strategic goals it will really help with this. Then when a feature is being discussed, we can say, "how does this fit in with our strategic goals?"
However, this isn't to say that features that don't fit into our immediate strategy shouldn't be discussed. But if we keep our strategic goals in mind I think it will inform the discussion early on and help us to keep our focus in the right place.
Scaling is one of the biggest challenges of consensus. One way to deal with it is specialization, with each person just deciding which channels they want to monitor, relevant to their skills, interests, and the kind of contribution they want to make.
The only problem with this is if important issues end up falling through the cracks. The usual solution is the spokescouncil model, where reps from subgroups feedback progress summaries to the parent group, and take comments back to the subgroup. This can be informal, or formal.
Random thought, could random feedback from less techy users could be the role of the Feedback subgroup?
http://www.loomio.org/discussions/1185
My suspicion is though that less techy users would rather send an email to a feedback@loomio.org type address.
Would it be possible to have a bot at that address automatically post the feedback sent to it in the feedback subgroup?
Have the big picture roadmap discussions already taken place? Or do they take place off-line, like at the coffee machine? I haven't really seen any big picture stuff. Is that a practical limiation?
Just thought this might be a good place to drop in our 'What we're working on' board for those that are interested.
It has some future feature direction in ideas that can be voted up. Of course if the big picture is universal collaboration it doesn't extend that far.
Thanks, had a look at the 'what we are working on" board. I see these as development tasks, the steps for moving the software from one revision to the next. The Loomio features I'd be looking for are more conceptual in nature, tying back to what the purpose and vision for the package as a whole is, where is it all going. Not the little steps but the direction and speed. Universal collaboration is a bit like peace, love and carbon neutrality on all scales. Could we look at what we (the developers) could achieve with Loomio's efficacy to support some/many types of democratic processes over a 2-3 year horizon, and build a roadmap?
Will or Should Loomio support some or many of the traditional decision making processes that people and groups use? Do we/any think that we can invent and replace traditional processes with a New Way? Should it be only new ways? Or should Loomio support many/most of the traditional ways of decision making plus add new ways?
For example, decision making doesn't occur very well in a vacuum. Access to resources and information, facts and opinions will improve the democratic processes. How can Loomio help facilitate the sharing or referencing of information critical to the decision making processes? Should it be more than the forum? In formal decision making processes, the convener and secretary will likely say - "we are here to make a certain decision - here is all the background information we have at this time - read it, talk about it, and make your decision." This is like a courtroom, just one way of democracy.
If the decision making process was fair and balanced, all the decision makers would have equal access to all the same background information, the letters and laws, the history, etc. There may also be observers, the observers also have a important role to play. There are clearly different roles to play.
Should Loomio support Player Roles? If so, who will assign the roles, who will engage the players? Right away we have adversion to hierarchies. Different world views and philosphies. Many will like flat egalitarian structures. Others will like hierarchies. We can't fight the battle or decide for anyone else the debate which has raged on for millennia.
Does the group backing the development of Loomio have a particular world view or philosophy about consensus formation? What is that?
My original understanding was that Loomio was firstly a tool which permitted asynchronous and geographically dispersed decision making. Easy to say. But what kinds of decisions? What kinds of groups would benefit? Do we really understand how decisions and consensus is reached?
Great questions Richard. Your not alone in asking for Loomio's future to be laid down, or at least spelt out. We have attempted to answer some of these questions internally to at least try and unify our own hopes and aspirations for Loomio. Agreed, we do need direction or else risk blowing needlessly in the wind, but being agnostic has also great merits. By not concretely defining what you are, you are available to wider audiences and do not exclude by aligning with any one philosophy. Your questions, I think, are all well received and important to planning our future I hope at some stage some if not all can be answered or at least considered deeply in building our roadmap.
agreed strategic phases of Loomio development provide a focus for each business area activity and a basis for accountability to the wider group
proposal by vivien maidaborn Closed Fri 14 Dec 2012 4:20PM
We remain committed to the current Loomio agile development approach and we also clarify the business development strategic phase we are in. In each phase there will be a degree of delegation to each team to make decisions that achieve the strategic outcomes of that phase. This is not too different than what we have been doing but probably needs sharpening up and formalizing how we communicate to each other how each team is doing according to the strategic priority. Also we need a roadmap setting out the next strategic phases in the context of our overall vision.
Results
| Results | Option | Votes | % of votes cast | % of eligible voters | |
|---|---|---|---|---|---|
| Agree | 3 | 75 | 0 | ||
| Abstain | 0 | 0 | 0 | ||
| Disagree | 1 | 25 | 0 | ||
| Block | 0 | 0 | 0 | ||
| Not voted | 895 | 100 |
Better internal processes, lines of communication and more idea of what the heck is going? Er, yeah.
I very much agree with the sentiment here. =) I also think that it would be a good idea to flesh out this proposal a bit more so that we know exactly what we're agreeing to.
Thanks for clarification Viv! Sounds like a sensible approach
I think a process for accountability needs to clarify to whom you're being accountable, and what proper channels for consultation or participation for various stakeholders are (incl. feature discussions). See my comment in the discussion for more. :)
I think product development should be left to people who have a passion and skill for developing products. Just having open processes and expecting everyone to be involved in the product development process isn't the right solution imho.
The same is true for financial management, relationship building, distribution channels, visual design, programming and a host of other specialist skills.
The challenge of a specialist team is having clear comms with other stake holders so teams have a sense of how they can work together on a bigger picture.
Hi @vivienmaidaborn , I'm a bit confused about what we're deciding on here? Possible to give some clarification about what it means to agree or disagree with this proposal?
@benknight
Agreeing to the proposal would mean you agree to:-
Do the work together to agree the strategic phases of the Loomio business development in a clear and recordable way. That each business team identifies the strategic objectives in that phase for their team and
That we agree a way to report progress to each other on those objectives.
Thanks for seeking clarification
@billy I am not sure if we are talking about the same thing. I have no problem seeing what people are doing or communicating either, my issue is more that we have an agreed focus and accountability without having to get really involved in every area of speciality. Really I guess I am sense making for myself, finding my way in this new democratic cultural organisation.
Hey sorry if I'm being dense, but while I understand the discussion topic and the proposal here, I really don't see how they are connected. Was this proposal raised in the right discussion?
Well it made sense in my mind. Kind of went like this...
Feeling overwhelmed by all the features discussions and how to best participate . In exploring that realized if I feel in touch with the current strategic priorities and these are agreed between us then I can back off the individual feature tracks. This thinking led out of @jonlemmon Post separating strategic importance from accessibility which I really appreciated. So in my mind still all one glorious developmental conversation. Totally agree it finished up in a different place it where it started though.
Haha love it @vivienmaidaborn. One thing I wanted to throw in the mix:
When the Facilitation Crew spins up we could start a new subgroup about the craft of collective decision-making generally, which might engage some of the user groups that aren't currently being engaged by the Features subgroup.
I imagine if there was a small community of people chewing on the problem of how Loomio fits with their facilitation practice, they'd soon run up against limitations of the software and consequently have an incentive to participate in the Features subgroup.
I'm concerned about the framing of the current proposal as a "decision", because I'm unclear about what the implications on governance are. I greatly respect the goal of ensuring accountability, but I also find it difficult to chime in, because of my unclear understanding of what power I'm wielding by doing so.
I'm one of the 71 people who is listed as a "member", but this is my first comment on the Loomio system (I contacted loomio because my PhD research is on online tools for consensus, but haven't participated much yet). Currently there are only 3 votes, so I could wield an enormous proportional power by adding a "no" or a "block", but I don't feel that my investment in the outcome is anywhere near as high as others'.
I'm throwing in a "No" vote here, because I think a decision about accountability needs to clarify to whom you're being accountable (e.g. who are the stakeholders, who are the members, etc.) and what the proper channels for consultation or participation are. That clarity might even help to ease the pressure on feature discussions if it can let people know what the proper channels and processes are.
But by all means, please disregard my vote if this seems out of line -- but my unclarity with where the line is motivates it. It feels weird to me to be part of a decision making process for a group I've not had much interaction with.
Great to see you on here @charliedetar !
Absolutely feel free to jump in to these discussions, and to ask for clarification wherever you feel it's needed.
I think what this highlights is that it would be really helpful for us to clarify the shared purpose of the Loomio Community group (in our own minds as well as for every user involved), and make sure we're putting decisions in the right place. Some decisions are appropriate to put out to the wider community, and others aren't. In this case I think the lack of engagement suggests this is something that requires more context to understand, and that most people didn't feel they had enough clarity/information to make a well-informed decision.
Part of the confusion I think has come from the fact that the Loomio Community group has organically grown out of the original Loomio group where the Loomio workers (mostly in the same office in Wellington) were making operation decisions as core stakeholders. The group organically expanded it's focus out to the wider community, but I guess we're still getting the hang of our group decision-making structure.
Good signal that there's some work to do with organising the structure of the network around the different types/levels of stakeholding!
I think Ben hits the nail on the head here. We are struggling with this issue in the FLOSS Coop group in some ways; what are the limits of direct democracy? Is it appropriate in an egalitarian/ consensus organisation to have any kind of central committee or board of directors? Again, these are really socio-political questions, not technical ones, and I don't think this as any one right answer.
This is a problem that every civil society organisation depending on volunteer input has to deal with if it survives long enough to provide services people actually depend on for their work. It's a problem that every open source project deals with, from GNU to Wikipedia to Ubuntu to OpenStreetMap to CreativeCommons. How d you provide security for employees, and good governance that keeps funders happy, while remaining open, accessible, and accountable to the volunteer community who generally do half the work; see Clay Shirky's TED talk for some stats on this:
http://tinyurl.com/institions-vs-collaboration
At the moment you have a self-selected open group of core contributors and power users able to participate in decisions. It seems like you have got to a point where you need a smaller, more agile group making operational decisions. But some are maybe concerned about that group becoming unaccountable, and that's a good thing to be aware of.
It's also the great thing about open source licenses. The accountability is built in because the primary asset is a common, and the secondary assets are the contributors and users themselves. If those undertaking governance are not responsive enough to the needs of the community, the community can fork the current version of the codebase and go elsewhere. The bulk of OpenOffice contributors did that when Oracle bought Sun (which owned the OO copyrights). They felt Oracle weren't respecting the community, so they formed the Document Foundation, and forked the code as LibreOffice.
Just checking I made it absolutely clear that my comment indicates a problem with our processes, not some flaw in your cognitive ability Viv :)