Cooperative Communication Repair¶
Repair communication breakdowns by restoring shared expectations of clarity, grounding, relevance, and sufficient information.
Essence¶
Cooperative Communication Repair is the pattern for fixing exchanges that stop working because people no longer experience the message as cooperative. A message may be confusing, unsupported, irrelevant, too thin, too long, or evasive. The archetype does not simply say “communicate better.” It asks which expectation failed and repairs that expectation directly.
The core move is diagnostic: identify whether the breakdown is about clarity, evidence, relevance, sufficiency, economy, or intent. Then supply the repair content that would let participants coordinate again, and check whether the repair actually restored shared understanding.
Compression statement¶
When people cannot coordinate because a message appears unclear, unsupported, irrelevant, incomplete, excessive, or misleading, diagnose which cooperative expectation failed, supply the specific repair content, and confirm shared understanding before continuing.
Canonical formula: perceived_breakdown + violated_expectation_diagnosis → targeted_repair_content + shared_understanding_check → restored_coordination
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.
Applicability expression7 distinct conditions
′ context guard? connective not recorded∅ no catalog witness yet
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.
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.
This condition preserves a load-bearing part of the diagnostic problem that was not captured by a source-condition atom. It remains explicit because omitting it would weaken the sufficient condition set.
6At least one of theselettered A–F
Any single one of these completes the pattern.
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.
Use this archetype when a conversation, document, support exchange, meeting, incident update, policy memo, or learning interaction has enough shared purpose to be repaired, but the current message is blocking coordination. The narrower requirement in this condition set is: 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.
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.
This is a load-bearing situation condition in the diagnostic expression. The condition is: A speaker or writer provides information that is accurate in isolation but not connected to the current decision, question, or user need. If it does not hold, this particular condition set is incomplete.
domainIrrelevant conclusion— Prove a sound argument for a proposition that is not the one at issue, then treat it as settling the contested claim — a relevance failure caught by restating the question before grading the answer.
context guardThe substituted proposition is accurate when considered in isolation.
suppliesThe information is accurate when considered in isolation.
How this was matched — 3 shared + 3 branches
accurate information is disconnected from the current communicative need
All of
- roleA speaker or writer provides information to an audience.
- polarityThe information is accurate when considered in isolation.
- relationThe information is not connected or relevant to the selected current target.
…and any one of
- branchThe current target is a decision.
- branchThe current target is a question.
- branchThe current target is a user need.
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.
This is a load-bearing situation condition in the diagnostic expression. The condition is: Claims, numbers, recommendations, or accusations are made without enough basis for participants to evaluate or act on them. If it does not hold, this particular condition set is incomplete.
domainGuilt by Association— Discredit a claim by the disreputable company it keeps — treating shared supporters, origins, or venues as a verdict on content — a relevance failure that lets no truth-value flow along co-occurrence edges without an independent causal or evidential link.
domainComplex Question— Expose a question that smuggles a contested claim in as its presupposition, so every direct answer silently ratifies the claim and the only sound reply is to refuse the frame.
domainSlippery Slope— Flag a consequence-chain argument as fallacious when its inter-step links are held together only by conceivability rather than a demonstrated mechanism, so it blocks a proposal by gesturing at a speculative terminus.
How this was matched — 3 shared + 2 branches
insufficiently supported communicated content prevents either evaluation or action
All of
- roleA claim, number, recommendation, accusation, or comparable assertion is communicated to participants.
- relationThe communicated content lacks enough evidentiary or justificatory basis.
- causalityThe inadequate basis causes the selected participant-use failure.
…and any one of
- branchParticipants cannot adequately evaluate the communicated content on the basis provided.
- branchParticipants cannot responsibly act on the communicated content on the basis provided.
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.
It is especially useful when people are asking questions such as “what do you mean?”, “why does this matter?”, “what supports that?”, “what should I do next?”, or “can you give me the right level of detail?” The narrower requirement in this condition set is: The audience asks repeated follow-up questions because a message gives too little detail, too much detail, or the wrong detail for the situation.
Eroding speaker trust · open
Participants begin treating the speaker as evasive, careless, manipulative, or irrelevant even when the underlying intent may be cooperative.
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. The narrower requirement in this condition set is: Participants begin treating the speaker as evasive, careless, manipulative, or irrelevant even when the underlying intent may be cooperative.
Missing norm repair · open
A recurring communication norm exists but has no repair path when it is violated.
Those neighboring archetypes may be used alongside it, but Cooperative Communication Repair remains focused on restoring cooperative expectations inside an exchange. The narrower requirement in this condition set is: A recurring communication norm exists but has no repair path when it is violated.
Coverage
2 of 7 conditions grounded · 5 open.
When to Use This Archetype¶
Use this archetype when a conversation, document, support exchange, meeting, incident update, policy memo, or learning interaction has enough shared purpose to be repaired, but the current message is blocking coordination. It is especially useful when people are asking questions such as “what do you mean?”, “why does this matter?”, “what supports that?”, “what should I do next?”, or “can you give me the right level of detail?”
It is not the right first pattern when the real problem is a multi-meaning term, a missing context anchor, a speech act whose authority is unclear, or a face-risk tradeoff. Those neighboring archetypes may be used alongside it, but Cooperative Communication Repair remains focused on restoring cooperative expectations inside an exchange.
Structural Problem¶
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.
Intervention Logic¶
The intervention starts by naming the breakdown without turning it into a personal accusation. Then the repairer asks which cooperative expectation is failing. Clarity repair asks for clearer distinctions or scope. Evidence repair asks for basis, source, confidence, or assumptions. Relevance repair links the message to the current question or decision. Sufficiency repair adjusts the amount and granularity of information.
The repair is complete only when participants check shared understanding. A repair that merely adds words can leave the breakdown intact. A successful repair lets people distinguish communicative misunderstanding from substantive disagreement.
Key Components¶
Cooperative Communication Repair is built around diagnosis rather than generic advice to "communicate better." The starting frame is the Cooperative Expectation, which makes explicit the Gricean assumption that contributors are trying to be clear, grounded, relevant, and appropriately informative for the shared purpose. When that assumption breaks, the Communication Breakdown appears as observable trouble: looping questions, accusations of irrelevance, unsupported claims, or inability to identify the next action. The Violated Expectation Diagnosis is the pivotal move, identifying which specific expectation has failed — clarity, evidence, relevance, sufficiency, economy, or intent transparency — because the right repair depends on which expectation is in trouble.
The repair itself proceeds through targeted requests and content, then closes with a check. A Clarification Request asks the smallest useful question that locates the missing distinction, basis, link, or action implication without becoming hostile interrogation. The Repair Content supplies the specific material that resolves the diagnosed failure, drawing on three substantive components matched to the diagnosis: the Relevance Link explains why a message matters for the current task or decision, Evidence Grounding supplies the basis behind claims and recommendations, and the Sufficiency Boundary tunes how much information is enough for the audience, urgency, and reversibility at hand. The cycle ends with a Shared Understanding Check — a read-back, summary, decision restatement, or next-action confirmation — that distinguishes genuine repair from "more words, same breakdown" and helps separate communicative misunderstanding from substantive disagreement.
| Component | Description |
|---|---|
| Cooperative Expectation ↗ | This is the expectation that the message will be clear, grounded, relevant, and sufficient for the purpose. The component turns Gricean maxims into practical design criteria for meetings, support, documentation, governance, and education. |
| Communication Breakdown ↗ | The breakdown is the observed failure that makes coordination unreliable. It may appear as confusion, repeated follow-up questions, accusations of irrelevance, unsupported claims, excessive background, or inability to identify the next action. |
| Violated Expectation Diagnosis ↗ | This component prevents generic repair. It asks whether the failure is primarily about clarity, evidence, relevance, sufficiency, economy, or intent transparency. The diagnosis determines the repair. |
| Clarification Request ↗ | A clarification request asks for the missing distinction, scope, evidence, relevance link, or action implication. It should be precise enough to guide repair and restrained enough not to become a hostile interrogation. |
| Repair Content ↗ | Repair content is the specific material that resolves the diagnosed failure. It may be clearer wording, a source, a confidence statement, a relevance explanation, a concise summary, added context, or a next-action statement. |
| Relevance Link ↗ | The relevance link explains why the message matters for the current task, decision, risk, stakeholder need, or next step. It is the antidote to accurate but unusable information. |
| Evidence Grounding ↗ | Evidence grounding supplies the basis for claims, recommendations, numbers, diagnoses, or status statements. It supports the exchange without turning the archetype into a full evidence-evaluation or provenance pattern. |
| Sufficiency Boundary ↗ | The sufficiency boundary defines how much information is enough. The right level depends on the audience, urgency, risk, expertise, and reversibility of the decision. |
| Shared Understanding Check ↗ | The shared understanding check closes the loop. It can be a read-back, summary, teach-back, decision restatement, or explicit next-action confirmation. |
Common Mechanisms¶
Clarification protocols and clarification scripts implement the archetype by giving people safe, repeatable ways to ask what is missing. Read-back and teach-back mechanisms test whether the repair worked. Evidence linking repairs unsupported or mistrusted claims. Relevance reframing reconnects information to the current purpose. Sufficiency checklists tune the level of detail. Meeting repair moves help facilitators pause and redirect live exchanges. Documentation reviews apply the same logic before a reader encounters the breakdown. Support triage question sets implement the pattern in customer or operational support.
These mechanisms are not the archetype itself. A script, checklist, template, meeting move, or support workflow is only an implementation vehicle. The archetype is the transferable repair logic: diagnose the violated cooperative expectation, supply targeted repair content, and confirm shared understanding.
9 documented mechanisms across 4 implementation forms.
The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.
Assessment, Review & Assurance · 2 mechanisms
- 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.
- 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.
Communication, Facilitation & Learning · 5 mechanisms
- 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.
- 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.'
Decision, Gate & Allocation · 1 mechanism
- 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.
Representation, Specification & Plan · 1 mechanism
- 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.
Parameter / Tuning Dimensions¶
Important tuning dimensions include the stakes of misunderstanding, the urgency of the exchange, the expertise distance between participants, the amount of shared context, the acceptable evidence standard, the granularity of detail needed, the power relationship between participants, and the channel of communication.
High-risk domains need stronger evidence grounding and shared-understanding checks. Low-risk exchanges may need only a quick clarification. Asynchronous documents need anticipatory repair through review, headings, examples, and sufficiency checks. Live meetings often need facilitation moves and explicit relevance framing.
Invariants to Preserve¶
The repair must remain linked to the diagnosed expectation. It must preserve the shared task rather than become a generic demand for more explanation. It must distinguish misunderstanding from substantive disagreement. It must be specific, proportional, and answerable. It must avoid turning clarity or evidence standards into tools for domination. It must leave room for legitimate uncertainty, confidentiality, privacy, and dissent.
Target Outcomes¶
The target outcomes are restored coordination, fewer looping conversations, more actionable documents, better support triage, less escalation from perceived evasiveness, and clearer distinction between communication failure and real disagreement. A successful repair lets participants continue with a shared understanding of what was meant, why it matters, what supports it, and what happens next.
Tradeoffs¶
The archetype adds friction because it pauses communication to repair it. That friction is valuable when ambiguity is costly, but wasteful when the issue is trivial. Evidence grounding improves reliability, but overuse can burden ordinary conversation. Relevance repair keeps focus, but may suppress exploration if applied too aggressively. Sufficiency repair prevents overload, but can hide needed caveats if brevity is overvalued.
The main design challenge is proportionality: enough repair to restore coordination, not so much repair that communication becomes bureaucratic or adversarial.
Failure Modes¶
A common failure mode is repairing the wrong expectation: adding detail when the real issue is relevance, or demanding clarity when the real issue is missing evidence. Another is the “more words, same breakdown” failure, where participants explain at length without addressing what is actually missing. Weaponized clarification occurs when requests for clarity or evidence are used to stall, exhaust, or dominate. False agreement occurs when people say they understand but no read-back or next-action confirmation tests it. Etiquette drift occurs when the pattern becomes politeness advice rather than structural repair.
Neighbor Distinctions¶
Sign–Meaning Alignment concerns the relation between a sign form and intended interpretation. Cooperative Communication Repair concerns an exchange whose cooperative expectations have failed. Speech-Act Clarification asks what action an utterance performs; this archetype asks what communicative expectation needs repair. Polysemy Disambiguation selects the active sense of a multi-meaning term. Context Anchor Design restores missing speaker, time, place, role, or scope context. Face-Saving Directness Calibration balances directness and relationship preservation. Psychological Safety Enablement creates conditions for speaking up; Cooperative Communication Repair uses those conditions to repair a specific exchange.
Cross-Domain Examples¶
In meeting facilitation, a facilitator pauses a looping discussion and asks whether the problem is evidence, relevance, or decision scope. In support, a vague ticket is repaired with targeted questions about environment, reproduction, expected behavior, actual result, and impact. In incident response, a vague reassurance is repaired with metrics, time window, affected region, and uncertainty. In documentation, a runbook replaces “restart it if needed” with a trigger, command, owner, expected result, and escalation condition. In policy work, a memo links evidence sections directly to the decision they support.
Non-Examples¶
A button label that implies the wrong action is not this archetype; it is Sign–Meaning Alignment. A statement whose authority or binding force is unclear is Speech-Act Clarification. A phrase whose referent depends on time, speaker, or place is Context Anchor Design. A hard refusal that must be delivered without humiliating someone is Face-Saving Directness Calibration. A substantive disagreement after everyone understands the evidence and options is not a communication-repair problem.
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.
- Distinct from parent: The parent covers multiple cooperative expectations; this variant targets failures of clarity and interpretability.
- Use when: Participants cannot tell what term, scope, referent, condition, or action is intended; The message may be true and relevant but is too unclear to support coordination.
- Typical domains: meetings, support, education, documentation
- Common mechanisms: clarification script, readback or teachback
Evidence Grounding Repair · implementation variant · recognized
Repairs perceived unsupported, misleading, or unreliable claims by supplying the basis, source, assumption, confidence level, or reasoning trail.
- Distinct from parent: The parent includes evidence repair as one family; this variant foregrounds the basis of claims.
- Use when: A claim is disputed because participants cannot see why it should be trusted; The exchange is blocked by missing evidence, hidden assumptions, or an unsupported recommendation.
- Typical domains: policy, incident response, science communication, management
- Common mechanisms: evidence linking, documentation review for cooperative expectations
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.
- Distinct from parent: The parent covers all cooperative expectations; this variant focuses on restoring the why-this-matters link.
- Use when: People perceive a contribution as off-topic, tangential, or disconnected from the decision at hand; A message needs to be reframed around the current question, risk, stakeholder, or next action.
- Typical domains: governance, meetings, education, customer support
- Common mechanisms: relevance reframing, meeting repair move
Sufficiency Repair · communication variant · recognized
Repairs communication that gives either too little or too much information for the audience, risk, and decision.
- Distinct from parent: The parent includes sufficiency as one cooperative expectation; this variant names the quantity-calibration case.
- Use when: The receiver cannot act because critical detail is missing; The receiver cannot identify the actionable point because the message includes excessive or poorly prioritized detail.
- Typical domains: documentation, executive communication, support, training
- Common mechanisms: sufficiency calibration checklist, documentation review for cooperative expectations
Near names: Gricean Repair, Conversational Maxim Repair, Shared Understanding Repair, Clarification Protocol, Communication Breakdown Repair.
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.