Loomio
Thu 9 Feb 2023 2:00AM

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

MN Matt Noyes Public Seen by 263

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

...

A

alain Thu 9 Feb 2023 7:14AM

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.

DB

Doug Belshaw Thu 9 Feb 2023 8:02AM

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

G

Graham Thu 9 Feb 2023 8:07AM

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.

P

Paul030 Thu 9 Feb 2023 12:22PM

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!

JDC

Justin du Coeur Thu 9 Feb 2023 2:22PM

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.

NS

Nathan Schneider Thu 9 Feb 2023 3:11PM

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.

HC

hamish campbell Thu 9 Feb 2023 6:14PM

Interesting - this is exactly what a template on the #OGB would work like https://unite.openworlds.info/Open-Media-Network/openwebgovernancebody I brought this up here a year or so ago :)

NS

Nick Sellen Thu 9 Feb 2023 10:26PM

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.

MB

Moon Baron Thu 9 Feb 2023 11:23PM

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.

D

Dynamic Sun 12 Feb 2023 11:39AM

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.

Load More