Skip to content

Cooperative Communication Repair

Repair communication breakdowns by restoring shared expectations of clarity, grounding, relevance, and sufficient information.

The Diagnostic Story

Symptom: The exchange keeps stalling. People ask the same clarifying questions in different words — what do you mean, why does this matter, what are you basing that on, what should I do next. Documents are long and accurate but leave out the decision, the owner, or the action, and support tickets arrive with every detail except the one needed to act. Participants start treating the other side as evasive or incompetent before the substantive issue is even reached.

Pivot: Convert the frustration into a specific diagnosis: which cooperative expectation was violated — clarity, grounding, relevance, or sufficient detail? Then repair that expectation with targeted content or process, not by adding more information in all directions.

Resolution: Participants share enough understanding to proceed. Stalled conversations, looping threads, and ambiguous meeting outcomes drop because the repair is precise rather than generic, and communication norms become diagnosable and correctable without turning every breakdown into a personal conflict.

Reach for this when you hear…

[engineering team] “The incident report was six pages of timeline and zero sentences about what we're changing so it doesn't happen again.”

[customer support] “The ticket came in with the error message and nothing else — I have no idea what they were doing, what they expected, or what environment they're running.”

[policy briefing] “The minister asked for the bottom line and got three slides of background that everyone in the room already knew — nobody said what the decision was.”

Mechanisms / Implementations

  • Clarification Protocol: A response move that asks the sender to state the buried premise before answering, so the receiver can engage the real question without accepting it — and without escalating to a challenge.
  • Clarification Script
  • Documentation Review for Cooperative Expectations
  • Evidence Linking
  • Meeting Repair Move
  • Readback / Teach-Back
  • Relevance Reframing
  • Sufficiency Calibration Checklist
  • Support Triage Question Set

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

Also references 8 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Clarity Repair · communication variant · recognized

Repairs communication breakdowns caused by vagueness, ambiguous wording, missing distinction, or unclear action implication.

Evidence Grounding Repair · implementation variant · recognized

Repairs perceived unsupported, misleading, or unreliable claims by supplying the basis, source, assumption, confidence level, or reasoning trail.

Relevance Repair · communication variant · recognized

Repairs an exchange when information may be true and clear but participants cannot see how it connects to the current purpose.

Sufficiency Repair · communication variant · recognized

Repairs communication that gives either too little or too much information for the audience, risk, and decision.