True Cost of Mediation Requests: Difference between revisions
Add Appendix 2: Prompt History |
|||
| Line 18: | Line 18: | ||
<div style="background-color: #f0f8ff; border-left: 4px solid #0066cc; padding: 15px; margin: 20px 0;"> | <div style="background-color: #f0f8ff; border-left: 4px solid #0066cc; padding: 15px; margin: 20px 0;"> | ||
'''Quick Stats:''' | '''Quick Stats:''' | ||
* Cost to | * Cost to requester: '''5 minutes''' | ||
* Cost to community: '''4 hours''' (baseline) | * Cost to community: '''4 hours''' (baseline) | ||
* Cost if it hits weekly meeting: '''7 hours''' | * Cost if it hits weekly meeting: '''7 hours''' | ||
</div> | </div> | ||
''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 == | == II. THE BASE COST OF ANY MEDIATION REQUEST == | ||
<div style="background-color: #fffbf0; border: 1px solid #ffd700; padding: 10px; margin: 10px 0;"> | <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> | </div> | ||
| Line 66: | Line 64: | ||
| '''Phase 1: Context Loading''' | | '''Phase 1: Context Loading''' | ||
| Someone summarizes, people add "context", someone steps up (or doesn't) | | Someone summarizes, people add "context", someone steps up (or doesn't) | ||
| '''~75 person-minutes''' (5 min × 15 people) | | '''~75 person-minutes''' (5 min × 15 people minimum) | ||
|- | |- | ||
| '''Phase 2: Derailment''' | | '''Phase 2: Derailment''' | ||
| Line 82: | Line 80: | ||
<div style="background-color: #e8f5e9; border-left: 4px solid #4caf50; padding: 10px; margin: 10px 0;"> | <div style="background-color: #e8f5e9; border-left: 4px solid #4caf50; padding: 10px; margin: 10px 0;"> | ||
✓ '''Mediators who take requests | ✓ '''Mediators who take requests early save the community ~3 hours''' — but still spend ~4 hours of collective time. | ||
</div> | </div> | ||
| Line 184: | Line 182: | ||
<div style="background-color: #e1f5fe; border-left: 4px solid #03a9f4; padding: 10px; margin: 10px 0;"> | <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> | </div> | ||
| Line 375: | Line 373: | ||
</div> | </div> | ||
</div> | </div> | ||
== APPENDIX 2: 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 | |||
# <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 | |||
---- | ---- | ||
Revision as of 16:09, 18 January 2026
The True Cost of Mediation Requests: A Framework for Analyzing Community Attention
I. INTRODUCTION: Why Counting Costs Matters
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
💡 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
When Requests Are Announced at the Weekly Meeting
| 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
A mediation request is structurally frivolous when it exhibits these markers:
🚫 Marker 1: No Community-Bounded Harm
| The Test | Does the primary grievance occur within Noisebridge spaces or involve Noisebridge community norms? |
|---|---|
| Red Flags |
|
| Why It Matters | Noisebridge mediation is not a general-purpose conflict resolution service. |
❓ 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 |
|
| Yellow Flag |
|
| 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
| The Test | Does the complainant show up, engage authentically, and respond to mediator requests? |
|---|---|
| Red Flags |
|
| 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
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
| 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
| 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
The three markers were visible early:
- External harm (DC510 exclusion mentioned in first message)
- No repair goal (never articulated despite direct asks)
- Non-participation (ghosted after initial post)
💡 Lesson: These markers can be detected in the first 24-48 hours, allowing early closure before costs compound.
VI. COST CATEGORIES: A Detailed Framework
| 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?
Threshold Questions
| Question | Requirements |
|---|---|
| 1. Community-bounded harm? |
|
| 2. Stated repair objective? |
|
| 3. Both parties participating? |
|
Red Flags (any ONE suggests frivolous request)
🚩 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
| 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
⭐ Remember: You are not required to accept every request.
How to Decline
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
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
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: Cost Estimation Worksheet
Use this to estimate costs for any mediation request:
Direct Labor
- 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
- 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)
- 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
_____ person-hours of collective community attention
Cost-Benefit Assessment
- 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
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
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.can you just do ti?let's change the name of the page to True_Cost_of_Mediation_RequestsOK great, now the formatting is super bad, it needs to be wikimedia formatted.i made some edits on the wiki, pull down the current revision and then please suggest some ways to make it more visually pleasing.sure, go for it.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.