Making scheduling fair in a worker cooperative

That sounds genuinely exhausting: two hours a month of conflict, plus the dread in between. I’m glad you’re looking for a better way.

I’ll be straight with you, though: I’m not going to hand you a scheduling algorithm, and not because one doesn’t exist. It’s because if I did, it would fail the same way every past schedule has failed: it would arrive as a ruling from outside, and the people who lose under it would fight it. The Solution Seeking System would say your co-op doesn’t have a calendar problem yet. It has a conversation problem, and the calendar is where it shows up.

Before we go further, walk me through what actually happens in the room. When the meeting starts, what’s the first thing people do?

That’s a very clear picture, and it tells me a lot. Notice the shape of what you described: every person opens with a position: “I need weekends off,” “exams are untouchable,” “I’m done with holidays.” Positions are conclusions. What never enters the room is what sits underneath them: the actual constraints and needs each position is protecting.

Here’s a test. Does anyone in that meeting, including you, actually know what Dana’s weekend constraint is? Whether it’s every weekend or alternating custody weekends, whether Saturday and Sunday are the same, whether mornings differ from evenings?

A vote can decide, but it can’t resolve. If seven people outvote Dana on weekends, you’ll have a schedule and you’ll also have Dana, still carrying the same constraint, now with proof that the group didn’t want to hear it. Democratic form without mutual understanding just organizes the fight more efficiently.

In the system’s terms, your meetings are jumping straight to Solution Seeking (everyone arrives with their solution and battles for it) with zero Mutual Understanding first. Nobody has heard the constraints under anyone else’s position, so every proposal feels like an attack on somebody.

And there’s a second failure compounding it: your past compromises were never written down as testable agreements. Ruth says she’s covered every Christmas for nine years. Is that recorded anywhere? Was it ever agreed as a temporary arrangement with a review date, or did it just quietly become permanent because she didn’t fight?

Saying it out loud is exactly the right instinct: “she didn’t fight, so we assumed she didn’t mind” is how invisible martyrdom works, and naming it is the first repair.

On Ruth and Dana: you’re right that a group meeting is the wrong place for their conflict. It’s a specific, personal rupture between two people, and it needs the full Communication Protocol at that scale: Introspection, Mutual Understanding, Solution Seeking, one on one. I’d suggest each of them, separately and privately, spend time with the Solution Seeking Guide at /practice/guide before the group process starts. It walks a person through preparing for exactly this kind of conversation, at their own pace, with nobody watching.

The group process we design should explicitly not try to settle their history. It should give them a structure where their constraints get heard like everyone else’s, and their conflict gets its own separate track. Does that separation feel workable to you?

You’ve landed on the exact confusion the Fairness principle exists to untangle. Fairness means decisions are just, impartial, and considerate of everyone’s needs and contributions. It means applying standards consistently while also taking individual circumstances into account. Identical treatment is one tool of fairness. It is not the definition of it.

The system distinguishes equality (same treatment for everyone) from equity (adjusted treatment to meet real needs). Sometimes fairness requires different arrangements to create genuinely equal burden. An identical weekend rotation that costs Dana her custody time and costs a student nothing comparable isn’t equal burden at all; it’s equal arithmetic.

Which is why my strongest recommendation is this: before anyone touches the calendar, the co-op should agree on what fairness means here, explicitly and in writing. A starter list to react to, not adopt:

• Burden is shared over time, not necessarily identically in any single month.
• Constraints are honored transparently: an accommodation anyone can see and understand the reason for, and could ask for in the same circumstances.
• No invisible martyrdom: nobody quietly absorbs the worst shifts for years; hard shifts get tracked and credited.
• The reasoning behind every decision is stated out loud, so nothing looks like favoritism.

Here’s my question back: under criteria like those, what happens to Ruth’s nine years?

Exactly. And notice what just happened: the moment fairness stopped meaning “identical this month” and started meaning “burden shared over time,” Ruth transformed from one of your “problem people” into the person your old process wronged most. Her blowup wasn’t unreasonableness. It was nine years of uncredited burden finally presenting its invoice.

That’s worth saying to her, plainly, before any new process begins. Something like: the co-op sees that the holiday and weekend load has fallen on you for years without ever being agreed to or credited, and the new process is partly designed to make sure that can never happen invisibly again. An acknowledgment costs nothing and it’s owed.

Practically, it also means the new schedule should front-load relief for her. Her banked burden is a real input to the criteria, not a grievance to manage. Ready to design what the meeting itself looks like?

Here’s a structure, built for a democratic group rather than a pair. Four phases, in strict order, because the order is the whole point:

1. Constraint-sharing round. Before any schedule exists, go around the room: equal, uninterrupted time for each of the fourteen members. Each person shares their real constraints: which times are impossible, which are costly, which are merely unpreferred, and what makes them so. This is Mutual Understanding, done as a group. No proposals allowed yet, no responses except clarifying questions.

2. Criteria check. Read the agreed fairness criteria aloud. Confirm they still hold, or amend them. Everything after this point gets measured against them, which depersonalizes the arguments: “this draft violates burden-over-time” is a very different sentence from “you’re being selfish.”

3. Open proposals. Anyone, not just coordinators, may propose a schedule, alone or in a small group, provided it honors every stated hard constraint and they can explain how it meets the criteria. Proposals compete on the criteria, not on whose voice is loudest.

4. Pick one to pilot. The group selects one proposal (and this is crucial) not as the permanent schedule. As a six-week experiment. I’ll come back to why that changes everything.

One question first: can you see any member for whom the constraint-sharing round itself would be hard?

No, and the process shouldn’t require it. The rule worth writing down: you owe the group your constraint, not your biography. “I cannot work Tuesday evenings, and it’s a firm constraint” is a complete contribution. The criteria ask that constraints be honored transparently, meaning everyone can see what the accommodation is, not that anyone surrender their privacy about why.

That said, the system’s principles of Vulnerability and Bravery point somewhere real here: the more context people freely choose to share, the easier empathy comes, and constraint-sharing rounds tend to soften rooms in ways that surprise people. Invite openness; never demand it.

A few facilitation notes for running these meetings, since the facilitator makes or breaks this:

• Rotate the facilitator each cycle. In a co-op, a permanent facilitator quietly becomes a boss.
• The facilitator enforces phase order, kindly and firmly. When someone jumps to a proposal during the constraint round, it gets parked, not debated.
• Park pair conflicts by name. If Ruth-and-Dana heat flares, the facilitator names it as a separate conversation with its own track (the Guide work we discussed) and returns the room to the process.
• Timebox everything. Equal voice means the confident talkers don’t get triple time.

Shall we finish with the pilot: how you pick, and what happens in week six?

That worry is exactly why the pilot exists, and why I said “pick one to pilot” instead of “pick the winner.”

The system treats every solution as actionable, testable, effective, and time-bound and, crucially, revisable. This is what the system calls being a Living System: no agreement is a monument. The schedule you pick is a hypothesis about fairness, and the six-week pilot is its test. If it turns out unfair in practice, that isn’t the process failing. That’s the process working, catching what no one could have predicted from around a table.

So the selection question changes. Instead of “which schedule wins?” (a question that creates winners and losers), the facilitator asks: “Can everyone live with this for six weeks, knowing there’s a review at the end?” That’s a far easier yes. People will trial an arrangement they’d never accept as a life sentence, and the guaranteed review is what makes consent honest rather than resigned.

Then the review itself is a scheduled meeting, on the calendar from day one, with real questions: Did the burden land the way we predicted? Did anyone quietly absorb more than their share? Check especially for new invisible martyrdom. Do the criteria themselves need amending? Keep, adjust, or replace?

The review date is the piece that breaks your grievance-compounding cycle for good. Nothing can silently become permanent anymore, because everything has a checkpoint. Would a written version of all this help, something you could bring to the co-op?

Scheduling process cheat-sheet

The diagnosis to share with the co-op: Our scheduling fights come from skipping Mutual Understanding (we argue positions without hearing each other’s constraints) and from past compromises that were never written down, so burdens accumulated invisibly.

Fairness criteria (starter list: amend together, agree before touching the calendar)

• Burden is shared over time, not necessarily identically in any single month.
• Constraints are honored transparently: accommodations are visible, and anyone in the same circumstances could ask for the same.
• No invisible martyrdom: hard shifts are tracked and credited, including retroactively where burden is already known.
• The reasoning behind every scheduling decision is stated out loud.

Meeting structure (phases in strict order)

1. Constraint-sharing round. Equal, uninterrupted time per member. Share constraints, not positions: impossible times, costly times, mere preferences. You owe the group your constraint, not your biography. Clarifying questions only: no proposals, no rebuttals.
2. Criteria check. Read the fairness criteria aloud; confirm or amend.
3. Open proposals. Any member or small group may propose a schedule that honors all hard constraints, with a stated case for how it meets the criteria. Proposals are judged against the criteria, never against the proposer.
4. Select a pilot. The consent question: “Can everyone live with this for six weeks, knowing there is a review?” Not “which schedule wins?”

Proposal rules

• Every proposal must honor every stated hard constraint.
• Every proposal must explain itself against each fairness criterion.
• Known accumulated burden (for example, years of holiday coverage) counts as an input, and relief for it should be visible in the draft.

Pilot

• Length: six weeks, dates fixed at selection.
• Status: the schedule is a revisable solution under test (a hypothesis, not a verdict). We are a living system; agreements are meant to be revisited.
• Review meeting: on the calendar from day one.

Review questions

• Did the burden land the way we predicted?
• Did anyone absorb more than their share without saying so? Ask directly; check for new invisible martyrdom.
• Do the fairness criteria themselves need amending?
• Keep, adjust, or replace. Then set the next review date.

Facilitation

• Rotate the facilitator every cycle.
• Enforce phase order kindly and firmly; park early proposals without debating them.
• Park pair conflicts by name into their own track. For any pairing with real heat, each person can prepare separately with the Solution Seeking Guide at /practice/guide before or alongside the group process.
• Timebox every phase so equal voice stays equal.

Bring this as a proposal to the co-op, not a ruling. It should survive its own process. Good luck, and come back after the first review; I’d like to hear what six weeks teaches you.