Introduction
Hello! In our last lesson, we analyzed the 'Tragedy of the Commons' archetype, exploring how rational individual actions can collectively deplete a shared resource, using the fashion industry as our case study. We examined how solutions like privatization, regulation, and self-governance each have distinct trade-offs.
Today, we will focus on a different kind of systemic breakdown, one that is more intimate and personal: the 'Accidental Adversaries' archetype. This is the 'A' in your FLATS GEDS mnemonic for system limiters. This dynamic explains how partners or allies, who should be collaborating, can unintentionally find themselves in opposition, taking actions that undermine each other's success despite sharing a common goal.
Your learning outcome for this lesson is to apply the 'Accidental Adversaries' archetype to diagnose and resolve a communication breakdown between partners in a vee relationship. Your background as a social researcher familiar with interpersonal dynamics will be invaluable here, as we will connect the abstract system structure to the concrete thoughts and feelings that drive such conflicts.
1. Understanding the 'Accidental Adversaries' Archetype
At its heart, the 'Accidental Adversaries' archetype describes a scenario where cooperation breaks down not because of malice, but because of a structural flaw in how the parties interact. Two or more parties join forces for mutual benefit. However, when faced with pressure, each party takes independent action to solve their own local problem. These actions accidentally create negative consequences for their partner, which triggers a defensive reaction, creating a vicious cycle of escalating conflict.
The structure is a powerful example of how reinforcing loops can work against us. A positive reinforcing loop of successful collaboration is replaced by a negative reinforcing loop of mutual obstruction.
To formalize this understanding, let's explore the typical story and structure of this archetype.
This guide from ReThink Health provides a clear and concise explanation of the 'Accidental Adversaries' archetype, including its generic story and the pattern of its feedback loops.
Please read the sections 'The Main Idea' on page 1 and 'The pattern explained in loops' on page 2. Focus on how a virtuous cycle of partnership can unintentionally flip into a vicious cycle of adversity due to independent, well-intentioned actions.
The key insight is that the problem lies not in the people, but in the system. The parties are not truly adversaries; they are made to act like them by a structure that lacks proper coordination and feedback.
2. Diagnosing a Communication Breakdown in a Vee Relationship
Let's apply this archetype to your specific area of interest: a vee relationship. This structure inherently contains the potential for an 'Accidental Adversaries' dynamic between the two partners who are not in a relationship with each other (the "metamours").
The Scenario:
- The Vee: A husband, Mark (the hinge), is married to Sarah and is also in a long-term relationship with his girlfriend, Emily.
- The Shared Goal: All three want the overall relationship structure to be stable, happy, and sustainable. This means Sarah and Emily are, by definition, partners in the success of this shared goal.
- The Breakdown: Lately, communication between Sarah and Emily has become tense and fraught. They feel they are competing for Mark's time and energy. Each feels her needs are being ignored by the other.
Let's diagnose this using the archetype.
The "Accidents":
- Sarah's 'Local Fix': Feeling that her marriage needs more quality time to feel secure, Sarah starts planning spontaneous weekend getaways with Mark. From her perspective, this is a rational action to strengthen her primary relationship.
- Unintended Consequence for Emily: These spontaneous trips frequently cause Mark to cancel his plans with Emily. Emily feels that her relationship is treated as less important and that her time is not respected. This creates insecurity.
- Emily's 'Local Fix': To combat this insecurity and guarantee her time with Mark, Emily insists that they establish a fixed, unchangeable "date night" every Wednesday. From her perspective, this is a rational action to create stability.
- Unintended Consequence for Sarah: The rigid Wednesday date night prevents Sarah and Mark from accepting spontaneous invitations or managing family commitments that might arise mid-week. Sarah feels her family's flexibility is being dictated by Emily's needs, and she feels encroached upon.
This is a classic 'Accidental Adversaries' structure. Both Sarah and Emily are taking logical steps to solve their own problems, but these steps unintentionally undermine the other, feeding a vicious cycle of resentment.
To truly understand the breakdown, we must go beyond the external actions and map the internal experiences—the thoughts and feelings that fuel the cycle.
[PDF] Dyadic Dynamics in Interpersonal Cycles - Proceedings
The causal loop diagram shows us the 'what', but to resolve the conflict, we need to understand the 'why'—the internal thoughts and feelings driving the behavior. The following paper offers a powerful model for mapping these vicious interpersonal cycles.
Please read pages 5-7, starting from the paragraph 'I’ll focus on the details of the interpersonal cycle loop...' and ending just before 'We want to stop and reverse the vicious cycle.' Pay close attention to the Ted and Ann example in Figures 3 and 4. Notice how it deconstructs the dynamic into each person's specific Actions, which trigger Thoughts and Feelings in the other, leading to a self-reinforcing loop.
Drawing on that model, we can map the internal dynamic between Sarah and Emily:
| Sarah (Wife) | Emily (Metamour) | |
|---|---|---|
| Observed Action | Emily insists on a fixed, unmovable date night with Mark. | Sarah plans last-minute weekend trips with Mark, causing cancellations. |
| Resulting Thoughts | "She's trying to control our schedule." "She doesn't respect our family life." "She's being rigid and demanding." |
"She is deliberately trying to show me I'm less important." "She doesn't respect my relationship." "My time means nothing to her." |
| Resulting Feelings | Resentment, anger, feeling constrained. | Insecurity, frustration, feeling disrespected. |
| Resulting Action | Becomes less accommodating of Emily's schedule and more protective of "family time." | Pushes for even more rigid rules and explicit commitments from Mark. |
As you can see, their actions and interpretations form a perfect, destructive feedback loop. The system is now in charge, driving them further into adversarial roles.
3. Resolving the Dynamic: Restructuring the System
The solution lies not in deciding who is "right" or "wrong," but in changing the structure of their interaction. The goal is to move from unilateral, uncoordinated actions to collaborative, coordinated ones.
The 'Accidental Adversaries' guide provides a clear roadmap for this.
The guide we read earlier not only helps with diagnosis but also provides a clear roadmap for resolution by outlining how to re-establish a collaborative relationship.
Please read 'Part IV: Re-establishing a Collaborative Relationship' on pages 9-10. Focus on the four key action points for managing the dynamic.
Let's apply these strategies to resolve the breakdown between Sarah and Emily. This would likely require a conversation involving all three parties, facilitated by Mark.
-
Acknowledge "Accidents" & Build Timely Feedback:
The first step is for Sarah and Emily to state the impact of the other's actions without assigning blame for the intent.- Emily might say: "When plans get cancelled at the last minute, I feel hurt and it makes me feel insecure about my place in Mark's life."
- Sarah might say: "When the schedule becomes very rigid, I feel constrained and it makes it hard to manage our family life."
This creates an understanding of the unintended consequences.
-
Develop Mechanisms to Avoid Accidents:
This is the most critical structural change. They need to replace their independent decision-making with a coordinated process. A practical solution would be to implement a shared calendar for Mark's time.- All three can see the schedule.
- Weekends and date nights are planned collaboratively a few weeks in advance.
- This creates transparency and forces negotiation before actions are taken, preventing "accidents." The limited resource (Mark's time) is now managed as a commons, rather than fought over.
-
Identify and Challenge Mental Models:
The conversation must surface the underlying assumptions.- Sarah's mental model: "My relationship is primary, so my need for spontaneity should take precedence."
- Emily's mental model: "I am seen as secondary, so I must fight for rigid rules to be respected."
By stating these aloud, they can be seen as perspectives rather than facts, and the group can work to find a new model that respects everyone.
-
Reaffirm the Intent and Benefit of the Partnership:
Finally, they must explicitly return to their shared goal. Mark could lead this by saying, "We all want this to work, and for everyone to feel secure and happy. We are partners in this. Let's solve this scheduling problem together as a team." This reframes the dynamic from "Sarah vs. Emily" to "The Team vs. the Problem." The problem is the faulty, uncoordinated system—not the people within it.
Conclusion
Today, we've dissected the 'Accidental Adversaries' archetype, a subtle but powerful dynamic that turns allies into opponents. By applying it to a vee relationship, we saw how rational, independent actions to ensure personal security can unintentionally create a vicious cycle of conflict and mistrust between metamours.
Key Takeaways:
- 'Accidental Adversaries' is a systemic archetype where partners with a shared goal unintentionally undermine each other through uncoordinated "local" fixes.
- Diagnosis involves not only mapping the external actions and their consequences (the causal loop diagram) but also the internal thoughts and feelings that perpetuate the negative cycle.
- Resolution is a structural process. It requires creating mechanisms for communication, coordination, and feedback (like a shared calendar) to prevent "accidents" and explicitly reaffirming the shared goal to shift the group from an adversarial to a collaborative frame.
Next Lesson Preview:
In our next lesson, we will move to the next archetype in your FLATS GEDS framework: 'Shifting the Burden'. We will explore how relying on easy, symptomatic solutions can prevent us from addressing the true, underlying problem, often making it worse in the long run.