Loomio

Organizing a growing Social.Coop: an idea for a proposal

Matt Noyes PublicSeen by 264

As Rene Magritte wrote, "this is not a proposal." This is a draft for discussion that may lead to a formal proposal for a new organizational body for Social.Coop. Drafted by Matt Cropp and Matt Noyes in consultation with the Community Working Group Ops Team.

On February 22nd, we will consult with interested members to consider creating a formal proposal.

See this editable pad document (feel free to comment, highlight, etc.): https://pad.disroot.org/p/Organizing_Social.Coop_Doc_Feb_4_23

Here is the text of the draft:

Organizing a growing Social.Coop: an idea for a proposal.

Matt Cropp and Matt Noyes, in consultation with the Community Working Group Ops Team

Process: initiate discussion of document on Loomio -> two weeks discussion -> make formal proposal on Loomio.

The Problem/Opportunity

Social.Coop has grown dramatically since November of 2022. The addition of new members has made the instance richer and more complex. It has also strained the existing forms of organization, particularly the Community Working Group Ops Team, which has been taking on onboarding, moderation, education, strategic planning and other tasks. 

Our existing organizational structure consists of three working groups: Tech, Community, and Finance (a legal working group is in the works), each of which functions differently and often with little coordination. Which decisions are made at which level and by whom, and who does the work, is inconsistent. Decisions made in one working group often have unexamined implications for other working groups. Groups change form: the CWG has lapsed and been replaced by the CWG Ops Team, for example. Ad hoc groups can also form, like the Reading Group.

With discussion and operations spread across multiple platforms – Mastodon, Loomio, Matrix – it is difficult for the membership to provide coordination and leadership. This lack of coordination and internal communication has resulted in, among other things, a tendency to do-ocracy and a deference to members who are perceived to be leaders, either because of longevity, activity on the instance, or other qualities. This raises the risk of “tyranny of structurelessness” type dynamics, and has troublesome implications for diversity and inclusion. It also undermines accountability. Finally, while Social.Coop functions collectively, we still lack the kind of organization needed to really operate as – and achieve, if we want it, the legal status of – a cooperative.

To meet our current needs for coordination and to organize Social.Coop members to take this experiment in member owned, governed, and operated social media to the next level, we intend to propose the formation of a Social.Coop Organizing Circle, with the features described below.

Create a Social.Coop Organizing Circle (OC)

A group of people consistently committed to holding this group (circle) and coordinating among working groups and ops teams, providing a space for ongoing conversation and coordination.

  1. Composition (who is on it? How are they chosen?)

    1. A mix of ops team and at large members

      1. one member from each working group/ops team, 

      2. seven members elected at large

  2. Nominations and Elections

    1. Social.Coop members* can self-nominate

    2. OC members will be elected to two year terms

    3. Half of the OC to be elected each year, to maintain continuity

    4. Subject to recall vote upon petition of 10% of members* [*active? Good standing? Registered?]

    5. Election process: juried sortition (to ensure diversity and inclusion)

  3. Roles:

    1. OC Coordinator (coordinates the circle)

    2. Membership Coordinator (maintains membership list, coordinates onboarding)

    3. Treasurer (keeps and shares financial information)

    4. Communications (keeps and shares records)

  4. Decision-making process

    1. [something like sociocratic consent]

  5. Compensation

    1. OC members will receive a stipend for attending OC meetings

    2. OC members with designated roles (coordinator, membership coordinator, treasurer, communications coordinator) will receive an additional stipend for work out of meetings

  6. Scope of Responsibility (what will these people do?)

    1. Coordination The Organizing Circle (OC) should meet at least monthly to coordinate, monitor, guide the work of the cooperative, and communicate with members.

    2. Strategic Planning The OC will facilitate a strategic planning process and adopt a strategic plan (subject to member approval), with regular periodic reviews and updates of the plan. The OC will also make major agreements with external organizations (like joining another organization) subject to membership approval.

    3. Financial Oversight and Budgeting The OC will provide financial oversight for Social.Coop, creating and approving an organizational budget, including budgets for each Ops Team; approving expenses above budgeted amounts; approving expenses not coming from Working Groups or Ops Teams. 

    4. Support and Oversight of Operations The OC will provide support and oversight to the Ops Teams, help create new Ops Teams, approve budgets, and approve the selection of Ops Team members who are compensated for their work. 

    5. Communications The OC will receive regular reports from ops teams and share that information with the membership, maintaining a shared calendar. 

  7. Scope of Authority

    1. Relation to membership

      1. The OC will review and decide on expulsions of members proposed by the CWG Ops Team

    2. Relation to working groups/ops teams

      1. The OC will review and decide on appeals of Working Group or Ops Team decisions

  8. Transparency

    1. Meetings open to members

    2. OC members can choose to meet in closed sessions for things like negotiations with vendors, personnel issues related to ops team staffing, and expulsion of members

    3. Budgets, income and expenses, are public via Open Collective

    4. Meeting minutes and recordings available on Loomio

  9. Sample Decision-making matrix

    1. (This is just an example to illustrate how we might designate at which levels decisions are made. Need to consult bylaws.)

Working Groups/Ops Teams

Organizing Circle

Members

Elect OC Members

X

Dissolve Social.Coop 

X

Create New Operations Teams

X

Propose Paid Ops Team Members

X

Approve Paid Operations Team Members

X

Develop and Propose Strategic Plan and Modifications

X

Ratify Strategic Plan and Modifications

X

Approve non-budgeted expenses

X

Create ad hoc groups (like the reading group)

X

Approve the budget

X

Decide how to spend Ops Team/WG budget

X

Propose expulsion of a member

X

Hear appeals of Ops Team/WG decisions

X

Change the SC bylaws

X

...

Matt Noyes

We now have

  • 1,920 (approx) registered users on the instance

  • 578 active users/week;

  • 750 Open Collective financial contributors;

  • 341 people registered on Loomio;

  • 86 on Meet.Coop.

As of 11/25/2022 the numbers were

  • 1,800 registered users

  • 622 active

  • 641 Open Collective contributors

  • 270 registered on Loomio

  • 66 on Meet.Coop

Two years ago:

  • 1,200 registered users;

  • 165 active;

  • 317 OC contributors. (Don't have Loomio stats handy. No meet.coop then.)

179 reports received by the Ops Team since November, up from 6 reports over the previous 3 months.

Dynamic

Thanks for the numbers. I'm not sure what meet.coop is. Can you link to documentation its relationship to social.coop?

Dynamic

Ah, ok. I totally must have registered there to attend the 101 meeting at the end of last year. Lots of platforms to keep track of!

Boris Mann

Thanks for these numbers. I’m confused why we have more registered members than we have OC contributors.

I thought that was the point — contribute to fund a communal instance?

I actually would be interested in eg sponsoring open user accounts for those that can’t afford it — but ideally that would be clear that people donate to fund those open accounts.

Dynamic

As I voice my support here, I want to note that it's interesting for me to see myself taking this position because most of the time I prefer the idea of direct democracy (or better yet, consensus decisionmaking). But from the few conversations Loomio I've had the privilege to participate in since joining the server, I can really see how this could be important for where we are right now. Even leaving aside the obvious problems of increased complexity with growing membership, the low turnout for most votes has been worrying me. It feels like a situation where concerted organization by a motivated minority could result in approval of decisions that don't reflect the values of the community as a whole.

Having a dedicated body that meets regularly and makes the core decisions could help to protect against this.

Scott McGerik

I wonder how many of those on social.coop that do not participate on Loomio also are not active on social.coop. Is there anyway to correlate activity between the platforms?

Dynamic

I don't know. I tried posting a poll on Mastodon about who votes and who doesn't, but got precisely zero responses. I imagine a more coordinated polling effort, being intentionally boosted by others interested in seeing the results might give better data, but even then, Mastodon posts can easily zip by without being seen by people who are only occasionally active (even on a daily basis).

Boris Mann

Please post the doc inline here. Once we have the new wiki launched that will be great to onboard all onto, but for now it should at least all work on Loomie

The EtherPad doesn’t work well on mobile (see screenshot) and I can’t see / open the ODT on mobile either. An image of the matrix attached in this thread would be appreciated.

Kathe TB

I agree that there is a clear need for a coordinating/organizing circle and think that this is an excellent start on a proposal. Do we formally have sociocracy adopted for our governance team/circles?

alain

Thank you for this initiative. I definitely see the tension and love the way you effectively respond to it with this already impressive draft.

I really think having a sociocracy-like structure of nested circles (connected by leaders and/or delegates) is something to explore and try to make work. So, thank you for that. This with consent decision making would be the sweet spot between democracy and operationnality.

Doug Belshaw

+1 to using sociocratic circles, I have proposal fatigue.

Graham

Definitely the way to go, thanks the Matts for making this happen. One point worth making is that it doesn't all have to happen in one go, but can be built out over time, which in my view is the better approach.

Paul030

I'm one of those newbies and not in-depth familiar with (y)our current organization, but this sounds like a very reasonable proposal to me - also because transparency and diversity are already taken into account in the draft. Thank you!

Justin du Coeur

Added a bunch of comments on the Etherpad. I like the general framework, but we're going to need to flesh out a bunch more details in order to get this right, I think.

Nathan Schneider

I appreciate the general direction a lot. Thanks for getting some momentum going here. A couple initial thoughts:

  • Why 7 at-large members? I think it would be adequate to have an equal or equal +1 number at large compared to the WG members. Each member is an additional expense, and also reduces the nimbleness of the group. I worry that a circle of over 10 people might be too large.

  • How does this translate to operational responsibility? Does that still occur at the WG level? One observation I have had in WGs is that we often end up with situations where the responsibility is with the group, but then no individual actually feels empowered/responsible to actually do stuff. Alongside the clarity you're presenting for governance, I think we need an improvement in the delegation of ops responsibility.

Nick Sellen

I mostly agree with the description of the problem, but less so with the solution. My sense is that the problems arise from an incoherent culture, or spirit (... maybe purpose/mission too).

Decisions made in one working group often have unexamined implications for other working groups.

I would like to be part of a culture where people intuitively check in with the people impacted by their actions.

I imagine people who have a job working in structured bureaucracies are used to working in silos where you do your thing, and it's somebody elses job to knit it together into coherence, but we don't have that here. I see this proposal as creating that bureaucracy (and it can probably succeed).

I wonder a lot at the moment about this kind of organisational inertia, where we keep things going, and keep fixing problems, to keep the thing alive, ... but without there being a clearly felt reason to do so.

It might be more a reflection of me and my relationship with social.coop than the organisation/project as a whole. I think I might just be moving in a different direction. Thanks for reading.

Moon Baron

I just wanted to add my overwhelming support for such a proposal. I think this sort of thing will make social.coop a lot stronger, and more agile in facing challenges.

Here are some thoughts:

  • as @Nathan Schneider suggested, i also agree we should really spell out our rational for why 7 is the number we've chosen as it has many implications. What's more, it's my opinion we should probably outline when we should consider growing/shrinking this number, and possibly describe the conditions under which we can do so. This proposal (rightly, in my estimation) points out that we should meet a certain quorum for recall, and I think that should maybe also be the case for such a group. Otherwise, I fear we might risk some "stealth" expansion or shrinking of the group as a way to evade the recall quorum.

  • when we speak of sortition, is the pool to be all those nominated? If so I'd make that more explicit because it's currently a bit ambiguous.

  • it may occur that there are too few nominees for the CWG Ops. I think we'd benefit for some protocols in such an event.

Dynamic

I agree that the sortition process needs to be clarified. I glossed over the word the first time I looked at the document because I didn't know what it meant. The comments added include a Wikipedia link, and if I understand it correctly, sortition is a lottery system (like jury duty in the U.S.).

I love the idea of a lottery system (I might take it a step further and have it be something people need to opt out of rather than self-nominate for), but hadn't realized that that was what we were talking about for selection of at-large members.

Matthew Cropp

On sortition, my thinking is something roughly along the lines of the below:

  • A pool of candidates willing to serve as members if the Organziing Circle is identified.

  • A randomly selected jury of X-number of members is selected as either an electing or recommending body. Jurors would be paid for the meetings they attend, and if someone does not want to serve, they can be set aside and another random member is selected to ensure the group has the intended number of members.

  • The jury meets 3x. First meeting to review the scope of the Organizing Circle member role, and discuss the skills, identities, etc., that would be good to have in the group. Second meeting to interview the candidates. Third meeting to discuss the interviews and vote to either select the members of the Organizing Circle directly, or to make a recommendation if the committee members are still going to be elected via a vote open to all members.

The idea is that it would make the selection process more deliberative, rather than potentially being simply a social capital-driven popularity contest, which is what mass elections in organizations can often devolve into, to the detriment of candidates with marginalized identities or uniquely valuable skills/experiences who don't have a high profile.

Dynamic

Oh, wow. That's a super interesting proposal. I'd been imagining that the at-large Circle would be identified through randomized jury process, but this is really good... possibly better, though I'm not sure.

Nathan Schneider

I propose that rather pre-nominating possible members, that sortition should occur on the basis of the entire membership, with people able to opt-out if they prefer. I think this would be more inclusive, particularly of people who are less actively involved in Loomio stuff.

tanoujin

I support this. However I see some problems with giving persons two hats at one time, the executive and the supervising hat. Would it be a possibility to reserve the right to vote on supervising issues to the Representatives (7 is workable), while the Execs should be present and be heard at least? We can still move defined decisions of importance to the plenum. Problem2: please let us avoid to become too dependent on technical frames for decision making. Public meetings with transcripts or records are absolutely sufficient - and they have a low threshold of participation.

Darren

Im sad to see this idea floated again.

Theres been repeated attempts to form a central governance body for social coop and each time its failed when put before the membership.

As already mentioned by Nick, Im not at all sure that the described problems would be solved by creating a centralised body to govern the coop.

Theres repeatedly been problems finding people to do the work needed to keep social coop running. We've relied upon the heroic voluntary efforts of a number of people whove done whats necessary to keep the wheels spinning.

I just dont think creating another opaque group where discussions are had and decisions made is conducive to getting more people to put in voluntary efforts. I think this is part of why the community working group (CWG) ops team finds itself overwhelmed. The CWG has been largely abandoned and theres no easy way for members to get a feel of whats involved with the CWG ops team work or maybe even help them out with some work/ideas/decisions.

Theres also been problems with closed teams having very low rates of participation (see Finance Working Group - sorry you cant because its closed). If stuff isnt organised in closed groups its easier for members to get an idea of whats going on and to potentially pick up the slack, without having to commit to what could be significant workload and responsibility load of taking on a position/role (eg. CWG ops team member)

I think if CWG ops team is feeling the strain we need to look at getting more folks involved in the stuff theyve been doing, very likely breaking up the workload, maybe pulling some of it back into the open CWG and encouraging people to get involved.

Think rather than creating a new group we need to find ways to drive more member participation in the work that needs doing. Creating new groups doesnt appear to be working so well (legal and participatory budgeting groups have had very little activity). Working out pattern to create easy ways for members to get involved in the work of running the instance and guiding folks into that feels like much more valuable efforts to undertake.

Matt Noyes

I am very interested in what @Nick Sellen and @Darren are saying. I think the key is to look at our existing practice, including work and culture, and see how to enhance it, concretely, specifically. The rationale of creating a new circle is to cultivate more member participation in the work and governance instead of relying on a de facto do-ocracy combined with uneven social influence/reputation. How to do that is the question. My sense is that organizing people is the key, but who do we imagine will do the organizing? How? Under what conditions? I get the concern with bureaucracy, so if there are specific things we can do to clarify the intent and reinforce the participatory and collaborative practices, let's talk about them. Encouraging people to get involved is not enough, right?

hamish campbell

It's an interesting discussern to dip into, as I have been working to solve/mediate this issue for the last 2 years. Reading between the lines, you have the traditional vertical (need more structure/control) vs horizontal, need more culture/trust balance stress.

Let me make a suggestion, you actually need more structure (control) to build a more trust based community, outcome you need to build a bridge :)

tanoujin

Thank you, hamish! I hope to hear more from you. And again, I am asking for public meetings with minutes, a financial report, an organigram with names and functions on it as it is now, and maybe even a founding story. And let me admit it is frustrating to see persons stomping on the breaks when someone asks for minimum structures for an organization that would like to be a co-operative. That‘s what I would take as trust building measures.

Moon Baron

I will say that while I am in favour of such an organising group, I very, very much appreciate those who are expressing their disquiet and concerns with the idea. IMHO, it's been constructive and can help us put things into perspective. If anything, I'd personally like to hear even more about what concerns and fears folk have regarding this proposal and what it might become.

By understanding everyone's nightmare scenario, perhaps we can help to avoid it by adopting changes to the proposal or even reconsidering it entirely if we feel the need to.

Matt Noyes

Strongly agree with this.

Dynamic

Yes! The voices of concern are extremely important here.

tanoujin

Okay, Moon, point taken, I will survive ;) Meanwhile I would like to know what happened to the community working group? It looks like that went wrong - but why? Analysis, anyone? Can we learn somthing from that fail?

Matt Noyes

My impression is that we were not able to keep up the momentum in the Community Working Group in part because some of its most active members were now on the Ops Team. One way to think of it is to look at the Tech Working Group, which is really an Ops Team -- a crew of people discussing and doing the hands on work. The CWG became redundant since we could just take proposals to the membership without running a preliminary vote in the CWG as was supposed to happen. I think it's best to think work --> structure instead of creating structures and trying to fill them with work.

tanoujin

I agree. And I believe the hands on work is well done - but transparency, trust, communication, this kind of community work needs to be done too, constructively, to build that bridge hamish has mentioned. Look, if the supervising board asks for a financial report they usually do not go down to single payments, that is treasurer stuff and does not need to and should not be known in detail at large. Nonetheless the supervisors could go down to that level if they see fit. It is much the same with moderation. The Representatives/Supervisers approve a report, there are minutes, I as an ordinary member can trust my Reps that all is fine and the Exec is not railroading their way like a military junta in 1970 Chile… that is useful work, and it should be done, imho. And yes, consensus is always the better option, but we do not have to re-invent the wheel. I would join a study group in administration or general co-op organization any time, to learn something new and have a qualified opinion. Otoh I can hardly appreciate what the ops team or the tech group are doing, if I do not know what is going on…

Matt Noyes

@tanoujin The CWG Ops team and TWG do post their minutes on Loomio, announced on Mastodon

tanoujin

@Matt Noyes Thank you, Matt, I know (by now). Yet the minutes I have seen were cryptic, I was not able to make anything out of it. So I would kindly ask to write whole sentences in an educational style, dreaming of references to an agenda, but any improvemend in intelligibility would be very welcome… it is okay for now, let us focus on the main topics, you might want to mention it elsewhere if you can keep it in mind, otherwise we can come back to that another time. tc

Nathan Schneider

Reading through the comments, one crack at an alternative proposal:

  • Create a new central body that is a spokescouncil of recognized working groups, with one participant per working group at each meeting, with some rotation.

  • Formalize a process of populating working groups with sortition, nominating members randomly and inviting them to join to replace departing members. Members would not be obligated to say yes. We could have a clear, annual cycle for choosing all working groups to help ensure it happens.

I think this would help retain the goal of decentralized organizing, while also creating capacity for central coordination and mutual accountability among the working groups. And sortition at the WG level would help bring more members into operations teams.

@Matt Noyes @Matthew Cropp

Matt Noyes

On the first point, I think having at large members is a good practice. When we first started the CWG ops team we included two spots for at large members who had no work obligation other than to attend ops team meetings. This made it easier for people from oppressed groups to participate. Also, the spokescouncil should not add to the work of people on the ops teams. So maybe specify that participating in the spokescouncil counts as an on call shift (speaking of the CWG ops team).

Matt Noyes

Another concern: if social.coop wants to move toward having official co-op status, we will need positions like those specified in our proposal, even if they are essentially paper positions. [edit: what I mean by "paper positions" is that under many cooperative laws a cooperative is required to have certain executive positions. These are real positions that have legal powers and responsibilities, but the organization can nonetheless adopt bylaws and practices that allow for a much flatter form of governance.]

tanoujin

With all due respect, I’d rather be gangbanged by the ops team for free once a week than taking on a paper position to roleplay democratic control. If you do not want democratic control, don’t go official. These structures are demanded for good reason.

tanoujin

And - correct me if I am wrong - “the CWG died off bc all active Members moved to the Ops team”. Guess why? You need an independent, democratically legitimated 2nd board to hold the exec accountable. Otherwise People drop it once they understand the game. It is interesting to follow this discussion. Possibly the distrust goes both ways?

Darren

First of all Id like to say that I really appreciate everyone who has put in time helping to organise or otherwise put time into keeping social coop running. Both the Matts who have presented this idea have put a lot of hours into doing stuff for the coop for years and I am truly grateful

Over the weekend I looked and noticed theres some stuff about the Organising Circle minuted from the Community Working Group Operations Team (CWGOT) meetings in January and Feburary. Minutes are in the Community Working Group Loomio. You have to be a CWG member to view these but any co-op member is free to join CWG (may have to wait for an admin to approve a request to join ?) , theres no work expected if you do so. Generally I try and take a look at both CWGOT and tech working group (TWG) minutes but had missed some the last few months.

Issues

I list here, and comment upon, a number of issues which are identified in the original post, also some others I think are worthy of consideration.

Video call meetings

can be very valuable and Im in favour of video calls being used for coop stuff. Theres often better more deep understanding that can be gained hearing a voice and seeing someone as they explain stuff.

Video meetings can be problematic for some people. Having to be available at an agreed time with a good enough connection is a higher bar to participation than asynchronous text discussions. A video (or audio) recording of a meeting is not as easy to search or, for many people, as quick to digest as text presentations or discussions (maybe the odd diagram?).

Due to personality type, command of language etc. some people will be less comfortable than others discussing issues via video. CWGOT and I imagine this suggested circle would be meeting via video call.

Structureless

Despite some comments in the original post above,that kind of makes hints otherwise, we are not currently structureless. We have a reasonably well defined structure

See this diagram (it wouldnt upload and embed here)

>also see bylaws,& wiki (or could check out our new wiki under development). We dont always follow/work within the defined structure, but as long as everyone is happy I dont think that is a bad thing.

CWGOT overwhelmed

I would suggest CWGOT gets some more members and/or splits off some of the workload elsewhere. Likely both is best if we can find people interested in helping.

Why did they take on co-op strategy? This was never their remit - of course its fine for anyone to chat about that stuff.

They were always supposed to be working in tandem with CWG. I was always a bit disappointed that they didnt really attempt to work along with the CWG structure, but have always been happy and grateful for everyone that took on CWGOT work. I was always somewhat concerned with how their work and decisions were often opaque to the rest of the coop and pushed hard, for months, for minutes to be published and have often made efforts to share them with the rest of the coop.

Inter Group Communications

Ive been active in TWG and CWG and tried to keep up with CWGOT & TWG work. Ive not noticed any major issues. Its easy to post in the appropriate working group in Loomio, message known working group/ops team members on Mastodon, or post to the appropriate matrix group (the matrix tech working group chat feels a lot like its home)

I think (and even modern management theory would agree) theres value in having a multiplicity of places where people from the coop can chat about the coop, whether thats Mastodon, Loomio, Matrix, email, video meetings, real life meetups /conferences or their local coffee shop. Its likely not necessary, desirable or possible for anyone to know everything about the coop.

Suggested structure

Im worried about adopting a structure which may not address current issues the coop faces but will cost money that could maybe used more effectively elsewhere (e.g. more money towards the stuff CWG ops team have been doing).

Its a load of work! People would have to go to the Circle meetings and Circle members would likely be spending time outside meetings learning about all kinds of areas of the coops work, without likely ever having as good an understanding of the issues involved as the actual people doing the work.

TWG payments

Tech working group folks tend to have well paid jobs, the money offered to them is comparitively insignificant. I get the impression that generally they'd rather see it spent elsewhere.

Do-ocracy

This suggestion could equally apply to the proposed structure. Despite at least a couple of "elections" of groups in the coop, I dont think we have had any where we had enough people step forward as candidates/volunteers that we ever had to vote. So we'd likely end up with something like a more formalised and closed do-ocracy anyway. Only those prepared to take on the work involved in the circle get powers to vote on some things.

Exclusion

I think it would be valuable to make efforts to help avoid exclusion. Encourage and maybe offer to pay some folks from marginalised groups to participate more in the organisation and governance of the coop. We can do this anyway and I suspect there would be strong support from members.

Ongoing participation

There have often been problems with levels of participation. People drop out of roles they have been doing, dont attend meetings, dont get involved in Loomio (CWGOT) or matrix (TWG) discussions. In a recent Finance Working Group (FWG) vote to approve an expense (pay rental costs for our server conputers) I was the only person to vote and Im not even officially in the FWG (I was let into their closed Loomio group to discuss a financial issue). Its likely a new closed Organising Circle would also suffer.

Closed group governing the coop

The proposed structure could lead to an additional number of people participating more in organising the coop because they feel they have a responsibility to do so, as they have taken on a role and are getting paid . They would also get privileges/powers over the coop other people wont have.

Personally I find it a bit sad we cant spend some efforts to find a way of making it more easy for/inspire people to step up and help out anyway (this does happen a fair bit in the TWG which is an open group happy and welcoming to new participants)

I know most people are pretty familiar with operating within centrally organised hierarchical structures with a closed group leading things. Apparently many here feel comfortable with the proposed structure. It makes me sad to see repeated attempts to push this type of structure onto the coop.

I haven't spent much time working within such structures. It doesnt feel comfortable to me. I have been largely involved in numerous, (I guess somewhat unusual?) groups, coops, projects, living & working situations over the years with participants numbering from 2 to tens of thousands. From squatter camps (Ive spent a number of years "officially" homeless - the squatter camps were often lovely communities, often very happy homes!) to open source software projects, to renewable energy coops, to community farms, to community land trusts.

Often they have not had strong formal (or any) governance structures. Ive lived through a number of terrible Tyranny of Structurelessness type experiences, but its not always that way. Often I have operated within very horizontal governance structures and my experiences over the years have shown me people will participate (look how far social coop has come!). Obviously organisers will come and go and sometimes projects will come to a natural end, but stuff can work pretty well without adopting a hierarchical organised structure.

We can create any or many different structures and processes through which members can participate with organising the affairs of the co-op, exercise their agency and take on their responsibility as owner members of the coop.

I worry that voting for Organising Circle members will, as often with other representative democracies, discourage people from deeper participation and interest in the organization/governance of the coop - vote away their responsibilities!

I think we would have much better societies if more people actively participated in the organisation and active governance of their housing, workplaces, communities, communication systems, energy & food supplies etc.

I think its valuable for many more people to hone the skills to effectively share the workload and responsibility of doing so together.

I think it would be better if we looked at our problems, we could maybe list them out somewhere, open up discussions to find solutions, rather than present a "solution" and make a list of problems that may justify it (I kind of get that feeling here)

Theres more I could say, including suggestions for some ways we could try and organise/improve stuff, but I'll leave you with this huge wall of text for now!

tanoujin

Thanks for that insight, Darren! Just to make sure I am getting you right: you are fine with social-dot-coop being the benevolent dictatorship of a clique? So, the only difference to other instances is just that there is a team playing around with advanced group dynamics?

Edit:

Comments on Darrens stance:

1. Option to join the Community Working Group: very welcome, who are the admins?

2. Video call meetings: pro, as an add on, with minutes at least. (I am honing my skills in making transcripts atm... possibly I would volunteer). Best practice: have them relate to the asynchronous text discussions.

3. Operations Team Integration: pro recruiting volunteers. Pro focussing on day-to-day business. Pro taking strategic questions to a more appropriate circle. I strongly recommend to improve transparency on all levels.

4. Thanks for pointing me to the possibility of just joining the groups - there is in fact a threshold for the newcomer that could be lowered by fleshing out the invitation to do so. Comment: agree to "not necessary, desirable or possible for anyone to know everything about the coop." Yes, not everything.

5. A budget would be great.

6. Education and learning is within the scope of coop values... some persons like it, others not so much.

7. See my provocative question. Strongly disagree with a closed do-ocracy. We need transparency as a prerequisite of democratic control. Without that "democratic" is just a hollow label.

8. Participation/Passivity/Apathy: I calculate 5-10% active members from experience. It is not clever to design more seats than you can have occupied. I see that it usually comes down to a small group of notorious active persons. I believe it is crucial to stay welcoming and cultivate openness in that situation.

Suggestion: re-activate the Community Working Group to prepare structures as suggested for the Organizing Circle. Big Picture: active members use the Community Working Group to cooperate. Develop an "Organizing Circle" or whatever the name is, within this structure, with proposals, feedback and vote, to overview operations, prepare strategic decisions of the plenum and what else comes to your mind.

tanoujin

I think it is time to give you some background information about me, skip this, if you are not interested. I was chair of a works council at an integration company for mentally disabled persons before I retired. That is why I compare the Operations Team to the companie's leadership. We had the role of representing the interests of the employees whithin a frame of co-management that excluded economic decisions. This kind of checks and balances is at the core of democracy imho. There are always persons who own the buttons. If they are clever, they welcome some supervision. So, that is where I come from. Thanks.

Darren

Hey @tanoujin thanks for your inputs

Thanks for that insight, Darren! Just to make sure I am getting you right: you are fine with social-dot-coop being the benevolent dictatorship of a clique? So, the only difference to other instances is just that there is a team playing around with advanced group dynamics?

I'm not at all sure you are understanding me, how our governance currently is structured and/or if we just have significantly different opinions. Maybe you are and we do.

In an attempt to further clarify my position -

I dont see a closed group structure - where a small group discuss and make decisions on significant issues concerning the coop, as being more democratic and less of a benevolent dictatorship clique than how our governance is currently structured where issues are (should be?) discussed and even voted upon in working groups open for any member to join.

Especially as the people within that closed group, at least for the foreseeable future, would only receive token payments for their time, so would effectively be people with the time/inclination to put in significant volunteer efforts.

Compare this to what we have now where members can (and do) dip into involvement with issues and voting depending on how much time, experience or interest they have.

Whats really gained?

We can create better rhythm to our governance and lines of communication without having to create a closed group to rule over us.

Sure whats been happening at times can be a bit messy or protracted, sometimes theres low participation, I think theres a lot we could do to improve things.

Personally over the years Ive learnt a whole lot during various conversations in the Loomios of Social Coop and its working groups. Its been a joy (although not always easy conversations) to hear from a big range of voices, and to see the votes start to stack up, when we've been dealing with issues people have felt strongly about.

Finally Im not sure its your intention, but your comments here can at times feel a bit unnecessarily abrasive. Sure I can cope.

tanoujin

Yes, Darren, I think I got it more or less by now, your post was helpful to learn a few more things about the coop, thank you.

What I see here reminds me a bit of a tribal structure with plebiscitary elements. You see, I can accept your experiences are leading to different conclusions compared to mine. I also accept this state of affairs as a not-so-bad starting point. I think there would be a lot to gain, but possibly it needs much more time. One important example: escape from the dependency on the engagement of the founders to create a project that is able to survive multiple generations of agents. There is much more, but this is not the place, it do not want to derail the debate.

I do not question your intentions. I am sorry to have caused irritation. I can be a little erratic sometimes. I am working on it.

You know how it is: the dogs are barking, but the caravan moves on. No doubt, the proposal discussed here would imo raise the standard to a level that could motivate me to really engage as an ordinary member.

Anyway I appreciate the instance as the best I can get in terms of social media, and I want to take the opportunity to thank everyone who took part in establishing and upkeeping it.

I need a walk through on basic knowledge to improve the quality of my contributions, as already stated elsewhere. I will enjoy reading you and be back at a later point in time.

Dynamic

I'm glad that you apologized to Darren, Tanoujin. I'm not sure exactly where I come down on the issues being discussed (honestly not sure I follow it all!), but the meanspiritedness of some of your comments really rubbed me the wrong way. Seeing nastiness in a policy discussion makes me feel wary of engaging, and I imagine there are others who would feel similarly.

Surely deterring people from engaging would not be good for democracy.

Bjorn Toft Madsen

I think the things that the OC can close the meeting for should be clearly defined, with a clearly defined process for changing the scope for why the OC can run closed meetings.

Are you interested in helping to re-write the proposal?

opt-in by Matt Noyes Closed Wed 1 Mar 2023 8:05PM

Outcome
by Matt Noyes

11 people have volunteered to help re-write the proposal, 12 if we include @Matthew Cropp the other original writer. Thank you! The next step is to go through the comments, pull all the suggestions and concerns, categorize them, and then see how to integrate/address them in a new proposal. Probably best to use the initial draft as a template/framework for categorization and then have a list of things that are more general. I will start a doc in NextCloud that we can all edit. (You may have to register on MayFirst -- https://wiki.social.coop/May-First.html) I will also start a new thread here on Loomio, with a link to that doc, and invite the folks who volunteered so we can discuss changes as we go.

Okay, the next step is to re-write the proposal, taking into account the various comments and suggestions.

Results

Matt Noyes
<span class="translation_missing" title="translation missing: en.poll_count_options.aceptar">Aceptar</span>

Want to move this forward.