True Cost of Mediation Requests: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
(Convert to proper MediaWiki formatting)
 
(12 intermediate revisions by the same user not shown)
Line 1: Line 1:
= The True Cost of Mediation Requests: A Framework for Analyzing Community Attention =
= The True Cost of Mediation Requests: A Framework for Analyzing Community Attention =
Use this page as a reference for creating better conflict routing systems, ones that take into account '''the amount of work that the community takes on just by taking the request''', starting from the request itself following through to the point at which some kind of mediation might actually happen.


== I. INTRODUCTION: Why Counting Costs Matters ==
This page is meant as '''a guidepost, not a policy'''.  If this page starts being used as an excuse to demonize people just for asking for mediation, please see if the [[Policy Injection]] social antipattern might apply here.


'''Opening premise:'''
'''If you are seeking mediation and you find this page: please rest assured we still want you to ask for mediation.'''
Every mediation request invokes community resources regardless of outcome. When requests are structurally frivolous—lacking bounded harm, stated repair objectives, or reciprocal participation—the community pays a hidden tax in attention, emotional labor, and opportunity cost.


'''The question this document answers:'''
This page focuses on the negative cases -- examples of how our mediation process can be abused in the first phase (from request to coordination) -- as a way of educating about what structurally frivolous mediation requests look like.  The idea is to inform mediators so that community time is not wasted (as much) and scarce mediator energy levels stay available to those who need them.
"What is the true cost of a mediation request, and how can we identify requests that will waste community resources?"


'''Who should use this framework:'''
== I. INTRODUCTION: Why Counting Costs Matters ==
* Mediators assessing whether to take requests
* Community members deciding whether to invoke mediation
* Stewards evaluating process effectiveness
* Anyone noticing patterns of process weaponization


== II. THE BASE COST OF ANY MEDIATION REQUEST ==
A request for mediation. What could be more innocuous? More demonstrative of an overall willingness to participate in reasonable discourse?


'''Minimum unavoidable costs''' (even if the request is immediately rejected):
Unexaminedly, sure.  But every mediation request invokes community resources regardless of outcome.


=== A. Initial Broadcast Cost ===
When requests are structurally frivolous -- lacking bounded harm, stated repair objectives, or reciprocal participation -- the community pays a hidden tax in attention, emotional labor, and opportunity cost.
* Weekly meeting chat announcement
* Likely readers: 3–4 people minimum
* Time per reader to parse context + emotional valence: ~1–2 minutes each
* '''Subtotal: 6–8 minutes'''


=== B. Containment Response ===
And, realistically speaking, some people consciously reach for community process *knowing* that it will cost them little, and cost the community a disproportionate amount of time and attention.
When a mediator steps up, they must:
* Read the complaint summary
* Assess scope and appropriateness
* Respond quickly to prevent meeting derailment
* Track it over time (context switching)
* Write mediation framing + rules
* Monitor for follow-through


'''Conservatively: 1.5–2 hours''' of mediator labor minimum
<div style="background-color: #f0f8ff; border-left: 4px solid #0066cc; padding: 15px; margin: 20px 0;">
'''Quick Stats:'''
* Cost to requester: '''5 minutes'''
* Cost to community: '''4 hours''' (baseline)
* Cost if it hits weekly meeting: '''7 hours'''
</div>


=== C. Community Member Attention ===
''This page was created using handwritten notes from a case study written down in Discord by [[User:Nthmost]] then fed into Claude Code which added quite a bit of fluff so it got trimmed down and yes it's a little repetitive but you know what it's fine.''
Others who get pulled in:
* Person posting for visibility: ~15 min
* Members reading and assessing: ~5 min each × N readers
* Members posting concerns/questions: ~5 min each


'''Subtotal: 25+ minutes''' (scales with visibility)
== II. THE BASE COST OF ANY MEDIATION REQUEST ==
 
=== D. The Parties Themselves ===
* Respondent reads, processes, writes response: ~30–45 min
* Complainant (if engaged): ~30–45 min
* If not engaged: opportunity cost still exists


'''Estimated Base Cost: ~4 hours of collective community attention'''
<div style="background-color: #fffbf0; border: 1px solid #ffd700; padding: 10px; margin: 10px 0;">
💡 '''Key Insight:''' This is what you spend even when the mediation doesn't proceed.
</div>


This is what you spend even when the mediation doesn't proceed.
{| class="wikitable" style="width: 100%;"
! Component !! Activities !! Time Investment
|-
| '''A. Initial Broadcast'''
| Weekly meeting chat announcement, readers parse context + emotional valence
| '''6-8 minutes'''
|-
| '''B. Containment Response'''
| Mediator reads complaint, assesses scope, responds to prevent derailment, tracks over time, writes framing/rules, monitors follow-through
| '''1.5-2 hours'''
|-
| '''C. Community Attention'''
| Person posting for visibility, members reading/assessing, members posting concerns
| '''25+ minutes''' (scales with visibility)
|-
| '''D. The Parties'''
| Respondent processes & writes response, complainant engages (if at all)
| '''30-90 minutes'''
|-
| style="background-color: #ffebcd;" | '''TOTAL BASE COST'''
| style="background-color: #ffebcd;" | Collective community attention
| style="background-color: #ffebcd;" | '''~4 hours'''
|}


== III. THE MULTIPLIER EFFECT: What Escalates Costs ==
== III. THE MULTIPLIER EFFECT: What Escalates Costs ==


=== When Requests Go to Weekly Meeting ===
=== When Requests Are Announced at the Weekly Meeting ===
 
If no mediator steps up and it reaches the weekly meeting agenda:


'''Phase 1: Topic Introduction & Context Loading'''
{| class="wikitable" style="width: 100%;"
* Someone summarizes the request
! Phase !! What Happens !! Cost
* Various people add "context"
|-
* Someone needs to step up to take the mediation
| '''Phase 1: Context Loading'''
* Time: minimum ~5 minutes
| Someone summarizes, people add "context", someone steps up (or doesn't)
* People engaged: minimum 15
| '''~75 person-minutes''' (5 min × 15 people minimum)
* '''Cost: ~75 person-minutes, unavoidable once it hits the meeting'''
|-
| '''Phase 2: Derailment'''
| Drama complaints, newer attendees check out, agenda items rushed, side-channel DMs
| '''~75 person-minutes'''
|-
| '''Phase 3: Procedural Labor'''
| Note-taking, reassurance, volunteering/being volunteered
| '''~30 person-minutes'''
|-
| style="background-color: #ffcccc;" | '''TOTAL MEETING COST'''
| style="background-color: #ffcccc;" |
| style="background-color: #ffcccc;" | '''~7 hours'''
|}


'''Phase 2: Derailment & Opportunity Costs'''
<div style="background-color: #e8f5e9; border-left: 4px solid #4caf50; padding: 10px; margin: 10px 0;">
* Someone complains about "drama" at Noisebridge
✓ '''Mediators who take requests early save the community ~3 hours''' — but still spend ~4 hours of collective time.
* Newer meeting attendees check out
</div>
* Other agenda items get rushed (no one likes long meetings)
* Side-channel DMs afterward
* Someone feels compelled to "follow up later"
* '''Estimate: ~5 minutes of diminished effectiveness across the group'''
* '''Cost: 75 person-minutes'''
 
'''Phase 3: Procedural Meeting Labor'''
* Note-takers document it
* Someone reassures someone else
* Someone volunteers or is volunteered to "look into it"
* '''Cost: 30 person-minutes minimum'''
 
'''Total Meeting Cost: ~7 hours of collective attention'''
 
'''Key insight:''' Mediators who take requests early save the community ~3 hours, but still spend ~4 hours of collective time. This is structural—not anyone's fault—but it means we must be selective about what we accept.


== IV. IDENTIFYING STRUCTURALLY FRIVOLOUS REQUESTS ==
== IV. IDENTIFYING STRUCTURALLY FRIVOLOUS REQUESTS ==
Line 90: Line 89:
A mediation request is '''structurally frivolous''' when it exhibits these markers:
A mediation request is '''structurally frivolous''' when it exhibits these markers:


=== Marker 1: No Community-Bounded Harm ===
=== 🚫 Marker 1: No Community-Bounded Harm ===
'''The test:''' Does the primary grievance occur within Noisebridge spaces or involve Noisebridge community norms?


'''Red flags:'''
{| class="wikitable"
! The Test
| Does the primary grievance occur within Noisebridge spaces or involve Noisebridge community norms?
|-
! Red Flags
|
* "This person excluded me from an external group"
* "This person excluded me from an external group"
* "This person was rude at a non-Noisebridge event"
* "This person was rude at a non-Noisebridge event"
* "This person disagrees with me online"
* "This person disagrees with me online"
|-
! Why It Matters
| Noisebridge mediation is not a general-purpose conflict resolution service.
|}


'''Why this matters:''' Noisebridge mediation is not a general-purpose conflict resolution service. Using it to adjudicate external disputes weaponizes community process.
=== ❓ Marker 2: No Stated Repair Objective ===
 
=== Marker 2: No Stated Repair Objective ===
'''The test:''' When asked "What improvement are you seeking?", can the complainant articulate a specific, achievable outcome?


'''Red flags:'''
{| class="wikitable"
! The Test
| When asked "What improvement are you seeking?", can the complainant articulate a specific, achievable outcome?
|-
! style="background-color: #ffdddd;" | Red Flags
|
* Complainant never answers the question
* Complainant never answers the question
* Answer is vague ("I want respect")
* Answer is punitive ("I want them banned")
* Answer is punitive ("I want them banned")
* Answer shifts when challenged
* Answer shifts when challenged
|-
! style="background-color: #ffffdd;" | Yellow Flag
|
* Vague answer ("I want respect") -- may be EQ related communication difficulties (mediator's discretion)
|-
! Why It Matters
| Mediation is meant to repair relationships. Without a repair goal, the process becomes a stage for performative grievance.
|}


'''Why this matters:''' Mediation repairs relationships. Without a repair goal, the process becomes performative grievance—theater using community attention.
=== 👻 Marker 3: No Reciprocal Participation ===
 
=== Marker 3: No Reciprocal Participation ===
'''The test:''' Does the complainant show up, engage authentically, and respond to mediator requests?


'''Red flags:'''
{| class="wikitable"
! The Test
| Does the complainant show up, engage authentically, and respond to mediator requests?
|-
! Red Flags
|
* Invokes mediation, then vanishes
* Invokes mediation, then vanishes
* Responds to some messages but ignores direct questions
* Responds to some messages but ignores direct questions
* Engages only to reassert grievance, not to work toward resolution
* Engages only to reassert grievance, not to work toward resolution
* Shows pattern of triggering processes without follow-through
* Shows pattern of triggering processes without follow-through
 
|-
'''Why this matters:''' "Summon community, then vanish" treats mediation as a weapon, not a tool. All subsequent attention becomes sunk cost.
! Why It Matters
| "Summon community, then vanish" treats mediation as a weapon, not a tool. All subsequent attention becomes sunk cost.
|}


== V. CASE STUDY: Anatomy of a Frivolous Request ==
== V. CASE STUDY: Anatomy of a Frivolous Request ==


'''Summary:''' Complainant invoked Noisebridge mediation regarding exclusion from DC510 (external group) and some Discord interactions. Mediator stepped up, saving ~3 hours of meeting time, but complainant never articulated repair goal despite multiple requests and eventually stopped responding.
<div style="background-color: #fff3e0; border: 2px solid #ff9800; padding: 15px; margin: 15px 0;">
'''Summary:''' Complainant invoked Noisebridge mediation regarding exclusion from DC510 (external group) and some Discord interactions. Mediator took on role before mediation request hit the meeting saving ~3 hours, but complainant never articulated repair goal despite multiple requests and eventually stopped responding.


'''Total cost: ~4 hours of collective community attention'''
'''Total cost: ~4 hours of collective community attention'''
</div>


=== Why It Was Structurally Frivolous ===
=== Why It Was Structurally Frivolous ===


'''1. Not community-bounded:'''
{| class="wikitable" style="width: 100%;"
* Primary harm: exclusion from DC510, not Noisebridge
! Marker !! Evidence
* Secondary complaints: tone in Discord conversations
|-
* Makes Noisebridge mediation an instrument for external conflicts
| style="background-color: #ffebee;" | '''🚫 Not Community-Bounded'''
 
| Primary harm: exclusion from DC510 (external), not Noisebridge. Makes NB process an instrument for external conflicts.
'''2. No repair objective:'''
|-
* Mediator asked directly: "What improvement are you seeking?"
| style="background-color: #ffebee;" | '''❓ No Repair Objective'''
* Complainant never answered despite multiple opportunities
| Mediator asked directly: "What improvement are you seeking?" Complainant never answered despite multiple opportunities.
* Easy answers were available ("I'd like more respect for my triggers")
|-
* Silence suggests goal was visibility/vindication, not repair
| style="background-color: #ffebee;" | '''👻 No Participation'''
 
| ~5 minutes of provocation vs. ~4 hours of community cost
'''3. No reciprocal participation:'''
|}
* Complainant invoked process
* Posted initial complaint
* Then repeatedly did not show up
* ~5 minutes of engagement vs. ~4 hours of community cost


=== Cost Breakdown ===
=== Cost Breakdown ===


* Mediator (containment, framing, monitoring, closure): ~2 hours
{| class="wikitable"
* Community members reading/commenting: ~25 min
! Who !! What !! Time
* Respondent (multiple thoughtful replies): ~45 min
|-
* Complainant (minimal engagement): ~5 min
| Mediator || Containment, framing, monitoring, closure || ~2 hours
* '''Total: ~4 hours'''
|-
| Community || Reading/commenting || ~25 min
|-
| Respondent || Multiple thoughtful replies || ~45 min
|-
| Complainant || Minimal engagement || ~5 min
|-
| style="background-color: #ffebcd;" | '''TOTAL'''
| style="background-color: #ffebcd;" |
| style="background-color: #ffebcd;" | '''~4 hours'''
|}


For context: '''This is baseline'''. If it had reached the weekly meeting, cost would have been ~7 hours.
<div style="background-color: #e1f5fe; border-left: 4px solid #03a9f4; padding: 10px; margin: 10px 0;">
📊 '''For context:''' This is baseline. If it had reached the weekly meeting, cost would have been ~7 hours.
</div>


=== What Made It Recognizable ===
=== What Made It Recognizable ===
Line 165: Line 195:
# '''Non-participation''' (ghosted after initial post)
# '''Non-participation''' (ghosted after initial post)


'''Lesson:''' These markers can be detected in the first 24-48 hours, allowing early closure before costs compound.
<div style="background-color: #e8f5e9; border-left: 4px solid #4caf50; padding: 10px; margin: 10px 0;">
💡 '''Lesson:''' Some of these markers may often be detected in the first 24-48 hours, allowing early closure before costs compound.
</div>


== VI. COST CATEGORIES: A Detailed Framework ==
== VI. COST CATEGORIES: A Detailed Framework ==


When analyzing mediation costs, track these categories:
{| class="wikitable" style="width: 100%;"
 
! Category !! Examples !! Note
=== A. Direct Labor Costs ===
|-
* Mediator time (reading, framing, monitoring, responding)
| '''A. Direct Labor'''
* Party time (writing, processing, engaging)
| Mediator time, party time, note-taking
* Note-taking and documentation
| Easiest to measure
 
|-
=== B. Attention Costs ===
| '''B. Attention Costs'''
* Number of people who read/engaged
| Number who engaged, context-switching, emotional processing, background worry
* Context-switching for each reader
| Scales with visibility
* Emotional processing time
|-
* "Background worry" for invested members
| '''C. Opportunity Costs'''
 
| Meeting time diverted, steward attention pulled, community energy spent, goodwill erosion
=== C. Opportunity Costs ===
| Often invisible
* Meeting time diverted from other agenda items
|-
* Steward attention pulled from other issues
| '''D. Cultural Costs'''
* Community energy spent on unproductive process
| Weaponization normalized, trust decreased, mediator burnout, chilling effect on legitimate requests
* Goodwill erosion when patterns repeat
| Long-term damage
 
|-
=== D. Cultural Costs ===
| style="background-color: #fff9c4;" colspan="3" | '''Key insight:''' Direct labor is measurable. Attention and opportunity costs are harder to quantify but often larger.
* Normalized weaponization of process
|}
* Decreased trust in mediation as effective
* Burnout of mediators and stewards
* Chilling effect on legitimate requests (when frivolous requests dominate)
 
'''Key insight:''' Direct labor (hours spent) is measurable. Attention and opportunity costs are harder to quantify but often larger.


== VII. DECISION FRAMEWORK: Should This Request Proceed? ==
== VII. DECISION FRAMEWORK: Should This Request Proceed? ==


'''Use this checklist when evaluating mediation requests:'''
=== Threshold Questions ===


=== Threshold Questions (all must be YES) ===
{| class="wikitable" style="width: 100%;"
 
! Question !! Requirements
'''1. Community-bounded harm?'''
|-
* ☐ Primary grievance occurs within Noisebridge spaces
| '''1. Community-bounded harm?'''
* ☐ Involves Noisebridge community norms/behavior
|
* ☐ Not primarily about external conflicts
* Primary grievance occurs within Noisebridge spaces
 
* Involves Noisebridge community norms/behavior
'''2. Stated repair objective?'''
* Not primarily about external conflicts
* ☐ Complainant can articulate what they're seeking
|-
* ☐ Goal is specific and achievable
| '''2. Stated repair objective?'''
* ☐ Goal is relational (repair), not punitive (punishment)
|
 
* Complainant can articulate what they're seeking
'''3. Both parties participating?'''
* Goal is specific and achievable
* ☐ Complainant responds to mediator questions
* Goal is relational (repair), not punitive (punishment)
* ☐ Respondent engaged in good faith
|-
* ☐ Both show willingness to work toward resolution
| '''3. Both parties participating?'''
|
* Complainant responds to mediator questions
* Respondent engaged in good faith
* Both show willingness to work toward resolution
|}


=== Red Flags (any ONE suggests frivolous request) ===
=== Red Flags (any ONE suggests frivolous request) ===


* ☐ Complainant ghosts when asked for specifics
<div style="background-color: #ffebee; border-left: 4px solid #f44336; padding: 10px; margin: 10px 0;">
* ☐ Request invokes mediation for leverage in external dispute
🚩 '''Warning Signs:'''
* ☐ Complainant has pattern of process invocation without follow-through
* Complainant ghosts when asked for specifics
* ☐ Repair goal is actually punishment in disguise
* Request invokes mediation for leverage in external dispute
* ☐ Request timeline suggests performative urgency
* Complainant has pattern of process invocation without follow-through
* ☐ Complainant answers different questions than asked
* Repair goal is actually punishment in disguise
* Request timeline suggests performative urgency
* Complainant answers different questions than asked
</div>


=== Risk Assessment ===
=== Risk Assessment ===


'''Low risk (proceed):'''
{| class="wikitable" style="width: 100%;"
* All threshold questions YES
! Risk Level !! Indicators !! Action
* No red flags present
|-
* Both parties showing good faith
| style="background-color: #d4edda;" | '''✓ Low Risk'''
* Harm is clear and bounded
| All threshold questions YES, no red flags, both parties showing good faith, harm is clear and bounded
 
| '''Proceed'''
'''Medium risk (proceed with caution):'''
|-
* Threshold questions mostly YES
| style="background-color: #fff3cd;" | '''⚠ Medium Risk'''
* 1-2 minor red flags
| Threshold questions mostly YES, 1-2 minor red flags
* Set clear expectations and deadlines
| '''Proceed with caution:''' Set clear expectations and deadlines, monitor for participation
* Monitor for participation
|-
 
| style="background-color: #f8d7da;" | '''✗ High Risk'''
'''High risk (consider declining):'''
| Any threshold question NO, multiple red flags present, pattern of weaponized process visible
* Any threshold question NO
| '''Consider declining:''' Likely to consume resources without resolution
* Multiple red flags present
|-
* Pattern of weaponized process visible
| style="background-color: #f5c6cb;" | '''⛔ DECLINE'''
* Likely to consume resources without resolution
| Multiple threshold questions NO, complainant non-responsive, clear process weaponization, harm primarily external
 
| '''Decline the request'''
'''Decline:'''
|}
* Multiple threshold questions NO
* Complainant non-responsive to basic questions
* Clear evidence of process weaponization
* Harm primarily external to community


== VIII. MEDIATOR SELF-PROTECTION ==
== VIII. MEDIATOR SELF-PROTECTION ==


'''Remember:''' You are not required to accept every request.
<div style="background-color: #e3f2fd; border: 2px solid #2196f3; padding: 15px; margin: 15px 0;">
 
⭐ '''Remember:''' You are not required to accept every request.
=== When to Decline ===
</div>
 
It's appropriate to decline when:
* Request is not community-bounded
* Complainant won't articulate repair goal
* You see pattern of weaponized process
* You lack capacity (time, emotional bandwidth)
* Request seems designed for visibility rather than resolution


=== How to Decline ===
=== How to Decline ===
Line 281: Line 305:


When you do accept:
When you do accept:
# '''Set participation expectations:''' "I need both parties to respond within 48 hours"
 
# '''Require articulation of goals:''' "What specific outcome would constitute success?"
{| class="wikitable"
# '''Set timeline:''' "I'm committing 2 weeks to this; if we're not making progress, I'll close it"
! Boundary Type !! Example Language
# '''Reserve right to exit:''' "I may close this if I see process weaponization"
|-
| '''Participation expectations'''
| "I need both parties to respond within 48 hours"
|-
| '''Articulation of goals'''
| "What specific outcome would constitute success?"
|-
| '''Timeline'''
| "I'm committing 2 weeks to this; if we're not making progress, I'll close it"
|-
| '''Exit rights'''
| "I may close this according to my own judgement"
|}


=== Recognize Sunk Cost Fallacy ===
=== Recognize Sunk Cost Fallacy ===


<div style="background-color: #fff9c4; border-left: 4px solid #fbc02d; padding: 10px; margin: 10px 0;">
If you're 1 hour in and seeing red flags:
If you're 1 hour in and seeing red flags:
* '''Don't think:''' "I've already invested time, I should continue"
* '''Think:''' "I can prevent 3 more hours of waste by stopping now"
'''Closing a mediation is not failure.''' Recognizing structural problems is expertise.
== IX. COMMUNITY-LEVEL PATTERNS ==
=== Warning Signs at the Community Level ===
Watch for these patterns across multiple incidents:
'''1. Serial process invocation'''
* Same person(s) repeatedly invoking mediation
* Requests rarely reach resolution
* Pattern of ghosting or non-participation
'''2. Mediation as performance'''
* Requests posted publicly first (rather than seeking mediator directly)
* Emphasis on documenting grievance rather than seeking repair
* Requests coincide with other conflicts/visibility needs
'''3. Process as punishment'''
* Mediation invoked immediately after disagreement
* Used as threat ("I'll request mediation")
* Goal appears to be forcing respondent to perform emotional labor
=== Community-Level Interventions ===
When patterns emerge:
'''Document the pattern:'''
* Track frequency of requests
* Note outcomes (resolved / abandoned / declined)
* Identify if specific individuals show weaponization patterns
'''Name the pattern publicly:'''
* "We're seeing mediation requests used for X rather than Y"
* Share this framework in meetings
* Make costs visible to community
'''Adjust norms:'''
* Require repair goals to be stated upfront
* Set participation expectations
* Normalize declining frivolous requests
* Respect mediator assessments as expert data
== X. PHILOSOPHICAL FRAME: Why This Matters ==
=== Mediation as Commons ===
Mediation is a '''community resource''', like:
* Workshop space
* Meeting time
* Shared equipment
Just as we don't let people monopolize the laser cutter, we shouldn't let process weaponization monopolize community attention.
=== The Attention Economy ===
'''Community attention is finite.'''
* 4 hours spent on frivolous mediation = 4 hours not spent on legitimate needs
* Mediator burnout from frivolous requests = fewer mediators available
* Cultural erosion from weaponized process = people stop trusting mediation
'''Protecting the commons means being selective about what we accept.'''
=== Anarchist Principles Applied ===
This framework is '''anarchist''' because:
* '''Distributed authority:''' Any mediator can decline any request
* '''Transparency:''' Costs and criteria are made legible
* '''Accountability:''' Mediators can be challenged on their decisions
* '''Protection of the commons:''' Resource stewardship is communal responsibility
'''Declining a frivolous request is not gatekeeping.''' It's responsible stewardship of collective resources.
== XI. IMPLEMENTATION GUIDELINES ==
=== For Mediators ===
'''Before accepting a request:'''
# Read the initial complaint
# Check the three threshold questions
# Look for red flags
# If uncertain, ask clarifying questions
# Set clear expectations if accepting
# Don't feel guilty about declining
'''During mediation:'''
# Monitor for participation from both parties
# If red flags emerge, name them
# Set and enforce deadlines
# Exit if you see process weaponization
# Document why you're closing it
'''After closing:'''
# Briefly state reason for closure
# Add to your personal "attention ledger" (estimate hours)
# Share pattern observations with stewards if relevant


=== For Community Members ===
* ❌ '''Don't think:''' "I've already invested time, I should continue"
* ✓ '''Think:''' "I can prevent 3 more hours of waste by stopping now"


'''Before requesting mediation:'''
'''Closing a mediation is not failure.'''
# Ask yourself the three threshold questions
</div>
# Articulate your repair goal to yourself first
# Consider if direct conversation might work
# Assess if this is truly community-bounded


'''If you're the respondent:'''
== APPENDIX 1: Cost Estimation Worksheet ==
# You can also assess if request is frivolous
# You can point out missing repair goals
# You can decline to participate in structurally broken process
# You're not required to perform emotional labor for someone's visibility needs


=== For the Community ===
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; padding: 10px; background-color: #f9f9f9;">
 
<div style="font-weight: bold; cursor: pointer;">📋 Click to expand: Cost Estimation Worksheet</div>
'''Create supporting infrastructure:'''
<div class="mw-collapsible-content" style="padding-top: 10px;">
# Link to this framework from mediation documentation
# Reference it in meeting notes when discussing mediation
# Normalize mediators declining requests
# Track and share aggregate statistics (number of requests, outcomes, estimated costs)
 
'''Adjust cultural norms:'''
# Treat mediator assessment as expert data
# Don't pressure mediators to accept every request
# Respect closure decisions
# Make costs visible and discussable
 
== XII. CONCLUSION ==
 
'''Key takeaways:'''
 
# '''Every mediation request costs ~4 hours minimum''' (baseline community attention)
# '''Structurally frivolous requests''' can be identified early via three markers:
#* Not community-bounded
#* No stated repair objective
#* No reciprocal participation
# '''Mediators have authority''' to decline requests and should exercise it
# '''The community benefits''' when frivolous requests are declined early
# '''Making costs visible''' protects the mediation commons
 
'''The responsibility:'''
 
In anarchist spaces, protecting commons resources is everyone's job. That includes:
* '''Requesters:''' Only invoke mediation for community-bounded harm with clear repair goals
* '''Mediators:''' Exercise judgment; decline frivolous requests; exit weaponized process
* '''Community:''' Support mediators in boundary-setting; make costs legible; adjust norms
 
'''Going forward:'''
 
When you see a mediation request, ask:
# Is the harm community-bounded?
# Is there a stated repair goal?
# Are both parties participating?
 
If the answer to any is "no" within 48 hours, that's dispositive data for closure.
 
'''Protecting the mediation commons means being selective about what we accept.'''
 
That's what responsible anarchist stewardship looks like.
 
----
 
== APPENDIX: Cost Estimation Worksheet ==


Use this to estimate costs for any mediation request:
Use this to estimate costs for any mediation request:
Line 487: Line 372:
* Would community pay this cost again for similar outcome? (Yes/No): _____
* Would community pay this cost again for similar outcome? (Yes/No): _____
* Lessons learned: _____________________________________
* Lessons learned: _____________________________________
</div>
</div>
== APPENDIX 2: Prompt History ==
<div class="mw-collapsible mw-collapsed" style="border: 1px solid #ccc; padding: 10px; background-color: #f9f9f9;">
<div style="font-weight: bold; cursor: pointer;">📝 Click to expand: Prompt History</div>
<div class="mw-collapsible-content" style="padding-top: 10px;">
This page was created through an iterative process with Claude Code. The original notes are not included here; readers can find exactly what was fed in from the Discord post here: https://discord.com/channels/720514857094348840/1450385404632240159
# <code>let's make a new wiki page turning the thing i'm pasting you here into a framework for analyzing the true cost of mediation requests.</code>
# <code>can you just do ti?</code>
# <code>let's change the name of the page to True_Cost_of_Mediation_Requests</code>
# <code>OK great, now the formatting is super bad, it needs to be wikimedia formatted.</code>
# <code>i made some edits on the wiki, pull down the current revision and then please suggest some ways to make it more visually pleasing.</code>
# <code>sure, go for it.</code>
# <code>it looks awesome, can you scan and make sure the page is clean fact-wise? i.e. reference the prompt i gave you with the numbers i wrote and make sure the current wiki page has all of the same facts and figures. if you find discrepancies, show me first before fixing.</code>
The progression: Raw framework → Published → Renamed → MediaWiki formatting → Visual enhancements → Fact-checked
</div>
</div>


----
----


''This framework emerged from a case study analysis conducted January 2026. It represents one mediator's attempt to make structural costs visible and create decision-making tools for future community stewardship. Like all Noisebridge documentation, it is a living document and can be challenged, improved, or replaced.''
''This framework emerged from a case study analysis conducted January 2026. It represents one mediator's attempt to make structural costs visible and create decision-making tools for future community stewardship. Like all Noisebridge documentation, it is a living document and can be challenged, improved, or replaced.''
[[Category:Conflict Resolution]]
[[Category:Community Process]]
[[Category:Documentation]]

Latest revision as of 15:16, 29 January 2026

The True Cost of Mediation Requests: A Framework for Analyzing Community Attention[edit | edit source]

Use this page as a reference for creating better conflict routing systems, ones that take into account the amount of work that the community takes on just by taking the request, starting from the request itself following through to the point at which some kind of mediation might actually happen.

This page is meant as a guidepost, not a policy. If this page starts being used as an excuse to demonize people just for asking for mediation, please see if the Policy Injection social antipattern might apply here.

If you are seeking mediation and you find this page: please rest assured we still want you to ask for mediation.

This page focuses on the negative cases -- examples of how our mediation process can be abused in the first phase (from request to coordination) -- as a way of educating about what structurally frivolous mediation requests look like. The idea is to inform mediators so that community time is not wasted (as much) and scarce mediator energy levels stay available to those who need them.

I. INTRODUCTION: Why Counting Costs Matters[edit | edit source]

A request for mediation. What could be more innocuous? More demonstrative of an overall willingness to participate in reasonable discourse?

Unexaminedly, sure. But every mediation request invokes community resources regardless of outcome.

When requests are structurally frivolous -- lacking bounded harm, stated repair objectives, or reciprocal participation -- the community pays a hidden tax in attention, emotional labor, and opportunity cost.

And, realistically speaking, some people consciously reach for community process *knowing* that it will cost them little, and cost the community a disproportionate amount of time and attention.

Quick Stats:

  • Cost to requester: 5 minutes
  • Cost to community: 4 hours (baseline)
  • Cost if it hits weekly meeting: 7 hours

This page was created using handwritten notes from a case study written down in Discord by User:Nthmost then fed into Claude Code which added quite a bit of fluff so it got trimmed down and yes it's a little repetitive but you know what it's fine.

II. THE BASE COST OF ANY MEDIATION REQUEST[edit | edit source]

💡 Key Insight: This is what you spend even when the mediation doesn't proceed.

Component Activities Time Investment
A. Initial Broadcast Weekly meeting chat announcement, readers parse context + emotional valence 6-8 minutes
B. Containment Response Mediator reads complaint, assesses scope, responds to prevent derailment, tracks over time, writes framing/rules, monitors follow-through 1.5-2 hours
C. Community Attention Person posting for visibility, members reading/assessing, members posting concerns 25+ minutes (scales with visibility)
D. The Parties Respondent processes & writes response, complainant engages (if at all) 30-90 minutes
TOTAL BASE COST Collective community attention ~4 hours

III. THE MULTIPLIER EFFECT: What Escalates Costs[edit | edit source]

When Requests Are Announced at the Weekly Meeting[edit | edit source]

Phase What Happens Cost
Phase 1: Context Loading Someone summarizes, people add "context", someone steps up (or doesn't) ~75 person-minutes (5 min × 15 people minimum)
Phase 2: Derailment Drama complaints, newer attendees check out, agenda items rushed, side-channel DMs ~75 person-minutes
Phase 3: Procedural Labor Note-taking, reassurance, volunteering/being volunteered ~30 person-minutes
TOTAL MEETING COST ~7 hours

✓ Mediators who take requests early save the community ~3 hours — but still spend ~4 hours of collective time.

IV. IDENTIFYING STRUCTURALLY FRIVOLOUS REQUESTS[edit | edit source]

A mediation request is structurally frivolous when it exhibits these markers:

🚫 Marker 1: No Community-Bounded Harm[edit | edit source]

The Test Does the primary grievance occur within Noisebridge spaces or involve Noisebridge community norms?
Red Flags
  • "This person excluded me from an external group"
  • "This person was rude at a non-Noisebridge event"
  • "This person disagrees with me online"
Why It Matters Noisebridge mediation is not a general-purpose conflict resolution service.

❓ Marker 2: No Stated Repair Objective[edit | edit source]

The Test When asked "What improvement are you seeking?", can the complainant articulate a specific, achievable outcome?
Red Flags
  • Complainant never answers the question
  • Answer is punitive ("I want them banned")
  • Answer shifts when challenged
Yellow Flag
  • Vague answer ("I want respect") -- may be EQ related communication difficulties (mediator's discretion)
Why It Matters Mediation is meant to repair relationships. Without a repair goal, the process becomes a stage for performative grievance.

👻 Marker 3: No Reciprocal Participation[edit | edit source]

The Test Does the complainant show up, engage authentically, and respond to mediator requests?
Red Flags
  • Invokes mediation, then vanishes
  • Responds to some messages but ignores direct questions
  • Engages only to reassert grievance, not to work toward resolution
  • Shows pattern of triggering processes without follow-through
Why It Matters "Summon community, then vanish" treats mediation as a weapon, not a tool. All subsequent attention becomes sunk cost.

V. CASE STUDY: Anatomy of a Frivolous Request[edit | edit source]

Summary: Complainant invoked Noisebridge mediation regarding exclusion from DC510 (external group) and some Discord interactions. Mediator took on role before mediation request hit the meeting saving ~3 hours, but complainant never articulated repair goal despite multiple requests and eventually stopped responding.

Total cost: ~4 hours of collective community attention

Why It Was Structurally Frivolous[edit | edit source]

Marker Evidence
🚫 Not Community-Bounded Primary harm: exclusion from DC510 (external), not Noisebridge. Makes NB process an instrument for external conflicts.
❓ No Repair Objective Mediator asked directly: "What improvement are you seeking?" Complainant never answered despite multiple opportunities.
👻 No Participation ~5 minutes of provocation vs. ~4 hours of community cost

Cost Breakdown[edit | edit source]

Who What Time
Mediator Containment, framing, monitoring, closure ~2 hours
Community Reading/commenting ~25 min
Respondent Multiple thoughtful replies ~45 min
Complainant Minimal engagement ~5 min
TOTAL ~4 hours

📊 For context: This is baseline. If it had reached the weekly meeting, cost would have been ~7 hours.

What Made It Recognizable[edit | edit source]

The three markers were visible early:

  1. External harm (DC510 exclusion mentioned in first message)
  2. No repair goal (never articulated despite direct asks)
  3. Non-participation (ghosted after initial post)

💡 Lesson: Some of these markers may often be detected in the first 24-48 hours, allowing early closure before costs compound.

VI. COST CATEGORIES: A Detailed Framework[edit | edit source]

Category Examples Note
A. Direct Labor Mediator time, party time, note-taking Easiest to measure
B. Attention Costs Number who engaged, context-switching, emotional processing, background worry Scales with visibility
C. Opportunity Costs Meeting time diverted, steward attention pulled, community energy spent, goodwill erosion Often invisible
D. Cultural Costs Weaponization normalized, trust decreased, mediator burnout, chilling effect on legitimate requests Long-term damage
Key insight: Direct labor is measurable. Attention and opportunity costs are harder to quantify but often larger.

VII. DECISION FRAMEWORK: Should This Request Proceed?[edit | edit source]

Threshold Questions[edit | edit source]

Question Requirements
1. Community-bounded harm?
  • Primary grievance occurs within Noisebridge spaces
  • Involves Noisebridge community norms/behavior
  • Not primarily about external conflicts
2. Stated repair objective?
  • Complainant can articulate what they're seeking
  • Goal is specific and achievable
  • Goal is relational (repair), not punitive (punishment)
3. Both parties participating?
  • Complainant responds to mediator questions
  • Respondent engaged in good faith
  • Both show willingness to work toward resolution

Red Flags (any ONE suggests frivolous request)[edit | edit source]

🚩 Warning Signs:

  • Complainant ghosts when asked for specifics
  • Request invokes mediation for leverage in external dispute
  • Complainant has pattern of process invocation without follow-through
  • Repair goal is actually punishment in disguise
  • Request timeline suggests performative urgency
  • Complainant answers different questions than asked

Risk Assessment[edit | edit source]

Risk Level Indicators Action
✓ Low Risk All threshold questions YES, no red flags, both parties showing good faith, harm is clear and bounded Proceed
⚠ Medium Risk Threshold questions mostly YES, 1-2 minor red flags Proceed with caution: Set clear expectations and deadlines, monitor for participation
✗ High Risk Any threshold question NO, multiple red flags present, pattern of weaponized process visible Consider declining: Likely to consume resources without resolution
⛔ DECLINE Multiple threshold questions NO, complainant non-responsive, clear process weaponization, harm primarily external Decline the request

VIII. MEDIATOR SELF-PROTECTION[edit | edit source]

⭐ Remember: You are not required to accept every request.

How to Decline[edit | edit source]

Template response: 

After reviewing this request, I don't think mediation is the right tool here
because [specific reason: not community-bounded / no stated repair goal /
appears to be about external conflict].

If you can clarify [specific missing element], I'm willing to reconsider.
Otherwise, I'd suggest [alternative: talking directly / external mediation /
letting it rest].

Setting Clear Boundaries[edit | edit source]

When you do accept:

Boundary Type Example Language
Participation expectations "I need both parties to respond within 48 hours"
Articulation of goals "What specific outcome would constitute success?"
Timeline "I'm committing 2 weeks to this; if we're not making progress, I'll close it"
Exit rights "I may close this according to my own judgement"

Recognize Sunk Cost Fallacy[edit | edit source]

If you're 1 hour in and seeing red flags:

  • ❌ Don't think: "I've already invested time, I should continue"
  • ✓ Think: "I can prevent 3 more hours of waste by stopping now"

Closing a mediation is not failure.

APPENDIX 1: Cost Estimation Worksheet[edit | edit source]

📋 Click to expand: Cost Estimation Worksheet

Use this to estimate costs for any mediation request:

Direct Labor[edit | edit source]

  • Mediator time: _____ hours × 1 person = _____ person-hours
  • Complainant time: _____ hours × 1 person = _____ person-hours
  • Respondent time: _____ hours × 1 person = _____ person-hours
  • Note-taker/steward time: _____ hours × 1 person = _____ person-hours

Subtotal: _____ person-hours

Attention Costs[edit | edit source]

  • Community members who read it: _____ people
  • Average time per reader (context + processing): _____ minutes
  • Members who commented: _____ people × 5 min each = _____ minutes

Subtotal: _____ person-minutes = _____ person-hours

Meeting Costs (if applicable)[edit | edit source]

  • Meeting time discussing: _____ minutes
  • Meeting attendees: _____ people
  • Meeting cost: _____ min × _____ people = _____ person-minutes
  • Derailment/opportunity cost (estimated): _____ person-minutes

Subtotal: _____ person-minutes = _____ person-hours

Total Estimated Cost[edit | edit source]

_____ person-hours of collective community attention

Cost-Benefit Assessment[edit | edit source]

  • Was there a positive outcome? (Yes/No): _____
  • Did it achieve stated repair goal? (Yes/No): _____
  • Would community pay this cost again for similar outcome? (Yes/No): _____
  • Lessons learned: _____________________________________

APPENDIX 2: Prompt History[edit | edit source]

📝 Click to expand: Prompt History

This page was created through an iterative process with Claude Code. The original notes are not included here; readers can find exactly what was fed in from the Discord post here: https://discord.com/channels/720514857094348840/1450385404632240159

  1. let's make a new wiki page turning the thing i'm pasting you here into a framework for analyzing the true cost of mediation requests.
  2. can you just do ti?
  3. let's change the name of the page to True_Cost_of_Mediation_Requests
  4. OK great, now the formatting is super bad, it needs to be wikimedia formatted.
  5. i made some edits on the wiki, pull down the current revision and then please suggest some ways to make it more visually pleasing.
  6. sure, go for it.
  7. it looks awesome, can you scan and make sure the page is clean fact-wise? i.e. reference the prompt i gave you with the numbers i wrote and make sure the current wiki page has all of the same facts and figures. if you find discrepancies, show me first before fixing.

The progression: Raw framework → Published → Renamed → MediaWiki formatting → Visual enhancements → Fact-checked

This framework emerged from a case study analysis conducted January 2026. It represents one mediator's attempt to make structural costs visible and create decision-making tools for future community stewardship. Like all Noisebridge documentation, it is a living document and can be challenged, improved, or replaced.

Retrieved from "https://main-wiki.extremist.software/index.php?title=True_Cost_of_Mediation_Requests&oldid=87754"