Reciprocity Check-In¶

Review ritual — instantiates Shared-Benefit Contribution Governance

A recurring, low-stakes conversation that surfaces imbalance, overload, and changed capacity early — so strain is repaired before it hardens into resentment or quiet withdrawal.

Cooperation rarely breaks all at once; it erodes as unspoken imbalance accumulates. Reciprocity Check-In is the relational maintenance channel that catches that erosion early. It is a standing, low-stakes conversation whose defining move is to ask specifically about the balance of the relationship — where someone is carrying more than their share, where their effort went unnoticed, where their capacity has changed — and then to repair it while it is still small. It is deliberately not a status or progress meeting: task updates crowd out the reciprocity signal, so this ritual leaves "is the work on track?" aside and asks "are we still even, and are you okay?" It is dyadic and continuous, which is what distinguishes it from a group retrospective's periodic, system-level look-back.

Example¶

Three adult siblings share care for their aging father. On paper the load is split; in practice the sister who lives ten minutes away silently absorbs every weekday emergency while the other two cover tidy weekend blocks. No one designed this — it drifted, and she is starting to feel like she "does everything." A monthly twenty-minute check-in (rotating through pairs) asks three questions and nothing else: what has felt heavy, what went unseen, what has changed in your capacity?

This month she says the weekday load became unsustainable when her own child's schedule shifted. A brother, genuinely surprised, offers to take Wednesday pharmacy and doctor calls remotely; the siblings agree she can pause the Tuesday run for two months without it being a defection. An imbalance that was hardening into "I do everything and no one notices" gets renegotiated while it is still a scheduling problem — before it becomes the resentment that quietly ends a sibling's participation.

How it works¶

Prompts for balance, not status. The questions target imbalance, underrecognition, overload, and changed capacity — the signals that predict withdrawal — rather than task progress.
Small and frequent. Low stakes and short cadence mean strain is named while it is cheap to fix, not saved up for a blow-up.
Ends in a change, not a verdict. Each check-in can renegotiate load or sanction a pause on the spot; the point is a concrete adjustment, however small.
Kept safe. Candor depends on the conversation being non-punitive, so disclosures do not become ammunition later.

Tuning parameters¶

Cadence — weekly versus quarterly. Too frequent breeds fatigue and "nothing to report"; too rare lets strain compound past the point of easy repair.
Scope — one-to-one versus small-group versus facilitated. One-to-one maximizes candor; group surfaces shared patterns but chills honest disclosure.
Prompt sharpness — open ("how's it going?") versus pointed ("where are you carrying more than your share?"). Pointed surfaces more but can feel confronting.
Repair mandate — whether the check-in can actually change the arrangement (grant a pause, reassign work) or only log concerns for later. Real authority is what makes showing up worthwhile.
Confidentiality — how protected disclosures are. More protection yields more truth but less shared visibility of the pattern.

When it helps, and when it misleads¶

Its strength is catching the slow slide into inequity while it is still cheap to correct, and legitimizing "I need to step back for a while" as an ordinary move rather than a betrayal — which keeps a strained contributor in rather than gone.

Its failure modes are specific. Without a real mandate to change anything, the ritual becomes venting theater and erodes trust by proving that speaking up changes nothing. Without safety, people answer "fine" and the strain stays buried until it ruptures. And it cannot fix imbalance that is structural rather than interpersonal — a load split that is wrong by design needs the whole arrangement redesigned, which is a retrospective's job, not a check-in's. The classic misuse is running it as a box-ticking ceremony that manufactures a feeling of fairness while the load never actually moves. The discipline that keeps it honest is to attach a genuine repair mandate and to track whether raised issues were actually resolved, because perceived inequity that is aired and then ignored corrodes faster than inequity never named at all.^[1]

How it implements the components¶

dispute_repair_and_renegotiation_path — it is a standing, low-stakes channel to surface imbalance and renegotiate load before it escalates into an open dispute.
protected_exit_or_pause_condition — it makes "my capacity changed, I need to pause" a sanctioned, face-saving move rather than a defection, so contributors can step back without leaving.

It does not recalibrate the whole arrangement or surface group-wide exclusion patterns (that is Cooperation Retrospective), keep a durable reciprocity ledger (Time Bank or Service Credit System), or escalate against a persistent free-rider (Graduated Free-Rider Response).

Instantiates: Shared-Benefit Contribution Governance — the check-in is the continuous repair channel that keeps contribution from eroding into resentment.
Sibling mechanisms: Cooperation Retrospective · Time Bank or Service Credit System · Contribution Board or Dashboard · Mutual Aid Roster · Graduated Free-Rider Response · Peer Commitment Round

References¶

[1] Equity theory (J. Stacy Adams): people compare their own contribution-to-reward ratio against others', and perceived inequity produces distress and eventual withdrawal. A reciprocity check-in is a channel to detect and correct the ratio before the withdrawal happens. ↩