Pattern Red-Team: Identify Failure Modes, Install Counter-Moves

You don't rise to the occasion. You fall to your defaults.

High performers don't fail at relationships from lack of intelligence. They fail from predictable behavioural defaults that activate under stress—the same defaults that would corrode any partnership, regardless of how smart both parties are.

This post gives you a systematic process: collect recent breakdown moments, classify the failure move, install a protocol-level fix, and track leading indicators to verify the change is working.

Frame: Trust corrosion is usually behavioural, not ideological. Most partnerships don't implode from one event—they erode from repeated micro-defaults. The fix isn't a conversation. It's a protocol change.

The Evidence Principle: Not All Negatives Are Equal

Relationship research consistently shows that certain behaviours predict deterioration far more strongly than others. You can have heated debates. You can disagree intensely. What you can't do is let these four patterns run unchecked.

Additionally, stable partnerships maintain a strong positive-to-negative ratio even during conflict. This isn't about being nice—it's about culture maintenance under load.

The Four Failure Moves

Failure Move	What It Looks Like	Why It's Corrosive
Identity Attack	"You're unreliable." "You never think about anyone but yourself."	Triggers threat response. Collaboration collapses.
Counterattack	"That's not true. What about when YOU..." Refusing any responsibility.	Blocks repair. Creates two prosecutors, no resolution.
Disrespect Signals	Eye-roll, sarcasm, mockery, superiority tone.	Destroys psychological safety. Erodes respect foundation.
Shutdown	Going silent, walking away, checking out mentally.	Triggers pursuit/escalation. Feels like abandonment.

The Counter-Moves

Identity Attack → Behaviour + Impact + Request
Replace: "You're unreliable"
With: "When the deadline was missed, I had to handle the client call alone. Can we agree on a handoff protocol?"

Counterattack → Own One Slice
Replace: "That's not what happened! You're the one who—"
With: "You're right that I was terse. I could have flagged my stress earlier."

Disrespect Signals → Respect Protocol + Clean Boundaries
Replace: Sarcastic jab about their approach
With: Direct disagreement + acknowledgment of their constraint. "I disagree with the timeline. I can see you're balancing multiple priorities."

Shutdown → Pause SOP + Return Time
Replace: Walking away mid-conversation
With: "I'm hitting my threshold. Continuing will degrade outcomes. I'll be back in 30 minutes." (Then actually return. See Hard Conversation SOP.)

Executive Context

Scenario: Two high achievers, both under deadline pressure. One gives feedback that lands as identity attack ("You're being short-sighted"). The other counterattacks. Sarcasm appears. One shuts down.

The fix: Not a better argument—a protocol intervention at each stage. Reframe feedback as behaviour + impact. Take one slice. Remove contempt markers. Use pause SOP before shutdown becomes abandonment.

Install as Protocols, Not Intentions

Leaders respect systems. "I'll try to be nicer" is not a system. "When I notice X, I will do Y" is a system.

The question isn't "Are we good people?" The question is: "What do we do when pattern X appears?"

Red-Team the First 90 Seconds

Most conflict damage is early. Research shows that a harsh opening predicts a harsh conversation. The leverage point is the first 90 seconds.

Practice drill: Take your last three breakdown moments. Identify the opening line in each. Rewrite each into a clean opener. That's where you get the highest return on effort.

Pattern Red-Team + Antidote Playbook

Step 1: Collect 3 recent breakdown moments. Brief description each.

Step 2: Tag the failure move(s) for each:

Identity attack
Counterattack / responsibility refusal
Disrespect signals
Shutdown

Step 3: For each failure type you use, write your counter-move script. Standard language you'll actually use.

Step 4: Create "Stop Rules"—when pause is mandatory (e.g., raised voice, sarcasm detected, either person says "I'm hitting threshold").

Step 5: Choose 2 leading indicators to track for 30 days:

% of hard conversations that start clean (no identity attack in first 90 seconds)
Repair latency (time from breakdown to restored collaboration)
Pause protocol compliance (when triggered, was it followed?)
Disrespect count (sarcasm/eye-roll instances per week)

Leading Indicators: What to Track

Choose two. Track weekly. Look for trend, not perfection.

Indicator	What It Measures	Target Direction
Clean start rate	% of hard conversations without identity attack in first 90 seconds	Increasing
Repair latency	Time from breakdown to restored collaboration	Decreasing
Pause compliance	When threshold hit, was pause protocol followed?	Increasing
Contempt count	Sarcasm, eye-roll, mockery instances per week	Decreasing

Failure modes to avoid:

Using labels as weapons ("You're being contemptuous right now")
Installing rules without practising the scripts
Over-metricising instead of actually changing behaviour
Treating this as one partner's problem rather than a system issue

What Comes Next

Even with better protocols, breakdowns will happen. Systems need recovery loops. The next post covers repair mechanisms—how stable partnerships recover fast and prevent trust debt from compounding.

→ Post 4: Repair Loops—The Recovery System High-Performing Partnerships Need

Want a structured pattern analysis?

If default patterns are entrenched and creating churn, a partnership performance review can identify specific intervention points and install the right protocols.

Book an Assessment

Educational content. This material is for informational purposes and does not constitute professional advice. For persistent conflict patterns or safety concerns, seek appropriate professional support.