True Cost of Mediation Requests

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.

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

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	"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

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

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

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:

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: 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?	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)

🚩 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 1: Cost Estimation Worksheet

📋 Click to expand: 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

📝 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.