Cooperative Communication Repair

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

Solution archetype #

254

Problem family

Communication, Meaning & Context Breakdown

Problem subfamily

Pragmatic Force & Relational Delivery Failure

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

When This Archetype Applies

Partial catalog groundingSome structural conditions are represented by existing abstractions, but no sufficient condition set is fully represented.

Diagnostic problem

Participants in an exchange cannot reliably coordinate because at least one party experiences the message as too vague, unsupported, irrelevant, misleading, incomplete, overlong, evasive, or otherwise uncooperative relative to the shared task.

What this problem means

The structural problem is that participants rely on expectations that are usually implicit. They expect contributors to be clear enough, grounded enough, relevant enough, and informative enough for the shared purpose. When one of those expectations breaks, the exchange becomes unreliable even if everyone is nominally using the same words.

A team may have plenty of information but no relevance link. A document may be truthful but unusable because it buries the answer. A support ticket may express urgency but omit reproducible details. A status update may sound reassuring but fail to say what evidence supports the reassurance. In each case, coordination breaks because the communicative structure is no longer cooperative enough for action.

Show the applicability expression

Applicability expression7 distinct conditions

Typed divergence repairandany oneStalled shared understandingorDecision-irrelevant informationorUnsupported actionable claimsorMiscalibrated message detailorEroding speaker trustorMissing norm repair

Algebraic1∧(A∨B∨C∨D∨E∨F)

groundedpartly groundedopen

Equivalent to the 6 condition sets it replaces, with 5 duplicate condition cards removed.

1Required in every casenumbered 1–1

These hold no matter which pattern applies.

1

Typed divergence repair · open

Agents sharing state over an unreliable channel detect divergence and require a typed meta-channel act before the primary exchange can resume. more

and also

6At least one of theselettered A–F

Any single one of these completes the pattern.

A

Stalled shared understanding · open

A meeting, document, support exchange, incident report, policy discussion, or learning interaction stalls because people cannot tell what is meant, why it matters, whether it is grounded, or what to do next. more

or — any one satisfies this slot

B

Decision-irrelevant information · grounded

A speaker or writer provides information that is accurate in isolation but not connected to the current decision, question, or user need. more

or — any one satisfies this slot

C

Unsupported actionable claims · grounded · any one of 3

Claims, numbers, recommendations, or accusations are made without enough basis for participants to evaluate or act on them. more

or — any one satisfies this slot

D

Miscalibrated message detail · open

The audience asks repeated follow-up questions because a message gives too little detail, too much detail, or the wrong detail for the situation. more

or — any one satisfies this slot

E

Eroding speaker trust · open

Participants begin treating the speaker as evasive, careless, manipulative, or irrelevant even when the underlying intent may be cooperative. more

or — any one satisfies this slot

F

Missing norm repair · open

A recurring communication norm exists but has no repair path when it is violated. more

Coverage

2 of 7 conditions grounded · 5 open.

Read the methodology · Download the trigger-logic data

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: A pre-worded, reusable bank of clarifying questions that lets anyone ask what a message is missing without sounding hostile — turning 'I'm confused' into a specific, answerable, cooperative request.
• Documentation Review for Cooperative Expectations: Audits a document against the cooperative expectations — clarity, grounding, relevance, sufficiency — before any reader hits the breakdown, and bakes the fixes back into the template.
• Evidence Linking: Attaches the basis — source, data, confidence, or assumption — to each claim so a mistrusted or unsupported statement becomes something participants can actually evaluate.
• Meeting Repair Move: A facilitator's in-the-moment move that pauses a stalling exchange, names the breakdown without blame, and redirects the room to the one expectation that actually failed.
• Readback / Teach-Back: Closes the loop by having the receiver restate the message in their own words, so a silent misunderstanding surfaces and gets corrected before anyone acts on it.
• Relevance Reframing: Reconnects accurate-but-unusable information to the listener's actual question or decision, so 'why are you telling me this?' becomes 'here's why this matters to you.'
• Sufficiency Calibration Checklist: A checklist that calibrates how much detail is enough for this audience and stake — pruning overload and filling gaps so a message is neither too thin nor too bloated to act on.
• Support Triage Question Set: A structured set of triage questions that pulls the specific missing facts out of a vague request and routes it to an owner, so support exchanges become actionable instead of looping.

Related Abstractions

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

Built directly on (1)

• Cooperative Principle and Gricean Maxims: Cooperative communication.

Also references 8 related abstractions

• Accountability: Responsibility for actions.
• Deixis: Context-dependent meaning.
• Feedback: Outputs influence inputs.
• Framing: Presentation shapes perception.
• Polysemy: Multiple meanings.
• Pragmatic Politeness Strategies: Maintain harmony.
• Psychological Safety: Safe environment for risk-taking.
• Speech Act Theory (Illocution, Perlocution): Language as action.

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.

Editorial Notes

Problem Classification

Classification: Communication, Meaning & Context Breakdown → Pragmatic Force & Relational Delivery Failure

Problem kernel: exchange content is received as uncooperative

Rationale: Messages may be technically present but feel vague, evasive, irrelevant, overlong, or unsupported relative to the parties' shared conversational task.

Independent corroboration: The earliest necessary condition in the frozen evidence is: Participants in an exchange cannot reliably coordinate because at least one party experiences the message as too vague, unsupported, irrelevant, misleading, incomplete, overlong, evasive, or otherwise uncooperative relative to the shared task. That is a pragmatic force and relational delivery failure problem because Literal wording does not reliably communicate the action, authority, relevance, cooperation, or relational stance that recipients must infer from an exchange.

Review outcome: Independent reviewer agreement; high confidence.