Pattern 5: Forced Public Escalation

Stage Jump: 2 → 5

Force a conflict into public channels where there is a permanent record, the opponent cannot save face, and coalition dynamics favor the escalator

The Pattern

Core Mechanism: Transform private resolution attempts into public confrontations, eliminating face-saving options and creating permanent records.

Private vs. Forced Public

Private Resolution Forced Public Conflict
Both parties can adjust positions Positions locked by public record
Face-saving retreat possible Retreat = public admission
Limited audience Community as witness
Focused on resolution Focused on winning
Relationship preserved Relationship damaged by public record

Example: Justin Morrison DM → Bravespace (December 2024)

Justin's Private Attempt

Justin Morrison December 2024 (Private DM)
[Conciliatory message attempting de-escalation]

Elle's Public Response

Elle December 2024 (Bravespace, public)
"Bravespace is where Noisebridgers work out differences, not private texts. I have not responded to your private text. I ignored it."

Justin's Objection

Justin Morrison December 2024
"Also @Elle I did not consent for you to respond to my DM with a post here"

The Escalation

The Contradiction

Pattern: Forced public escalation is applied selectively - public when it advantages Elle, private when it doesn't.

When Public Works Against Elle

Elle September 2025
"I am getting tired of being dragged into Bravespace for the same thing over and over again."

When Elle is Overruled Publicly

Elle Sewing channel
"Would this private convo work better in DMs?"

The Pattern

Situation Elle's Preference
Opponent attempts private de-escalation Force public: "Bravespace is where..."
Elle being held accountable Complain: "tired of being dragged"
Public discussion goes against Elle Suggest private: "better in DMs?"

Why Forced Public Escalation Works

1. Eliminates Face-Saving Options

In private, both parties can adjust positions without admitting error. In public:

2. Locks Positions in Place

Once positions are stated publicly:

3. Creates Coalition Dynamics

Public conflicts naturally build coalitions:

4. Provides Permanent Record

Discord messages are searchable and permanent:

  • Can be quoted later as evidence
  • New members see historical conflicts
  • Reputational effects persist
  • Difficult to move past recorded statements
  • How This Escalates Unnecessarily

    Example Analysis: Justin Morrison

    If Private Discussion Succeeded

    • Justin and Elle work out fundraising approach
    • Both save face (no public record of disagreement)
    • Relationship preserved
    • Justin continues fundraising work

    After Forced Public Escalation

    • Public confrontation in Bravespace
    • Justin must defend publicly
    • Permanent record of conflict
    • Justin disengages from fundraising
    • Community loses contributor

    Legitimate vs. Forced Public Discussion

    Important: Some issues do need public discussion (policy changes, community decisions, etc.). Forced public escalation is different - it's using publicity as a weapon.
    Legitimate Public Discussion Forced Public Escalation
    Issue affects community (policy, resources) Personal conflict between two people
    Both parties agree to public forum One party forces public against other's will
    Private resolution attempted first Private attempts rejected or ignored
    Goal: Community input/decision Goal: Win conflict via public pressure
    Focuses on issue substance Focuses on opponent's character

    Key Questions

    Community Impact

    Contributors Lost

    Governance Challenges

    Trust Erosion

    How to Counter This Pattern

    If You're the Target

    1. Assert consent boundary: "I did not consent for you to respond to my DM here."
    2. Propose return to private: "Let's continue this conversation privately."
    3. Question the necessity: "Why does this need to be public?"
    4. Focus on resolution: "I'm interested in resolving this, not winning a public debate."

    If You're a Bystander

    1. Question whether public is necessary: "Does this need community input?"
    2. Support private resolution: "This sounds like something you two can work out."
    3. Note consent issues: "Did both parties agree to public discussion?"
    4. Avoid taking sides: Don't participate in forced coalition building

    For Community Governance

    1. Clarify channel purpose: What belongs in Bravespace vs. private?
    2. Protect consent: Policy on posting private conversations publicly
    3. Support multiple paths: Endorse both public and private resolution
    4. Education: Teach when public vs. private is appropriate

    What Makes This Stage-Skipping

    Normal Conflict Progression (Stages 1-3)

    Stage 1-2: Disagreement emerges
        Justin sends conciliatory private DM
        Attempt at private resolution
    
    Stage 3: Work it out privately
        Find compromise
        Both save face
        Move forward

    Forced Public Escalation (Skip to Stage 5)

    Stage 2: Disagreement emerges
        Justin attempts private de-escalation
    
    [SKIP private resolution]
    
    Stage 5: Public loss of face
        Force into Bravespace
        Permanent public record
        Positions locked
        Face-saving impossible