Skip to content

Locution Illocution Perlocution Decomposition

When a statement is being misread, separate what it literally says, what action it performs, and what effect it produces.

The Diagnostic Story

Symptom: A dispute about a statement refuses to resolve because the parties are arguing past each other: one is defending the literal wording, another is citing the effect it produced, and a third is insisting on what was clearly meant. Repair attempts rewrite the words when the problem was the act they performed, or vice versa, so the same breakdown recurs in a different sentence.

Pivot: Treat the utterance as three distinct layers that must be assessed separately: what the words literally said, what social or institutional act the speaker attempted or was authorized to perform by saying them, and what effect they had on the receiver or situation. Then match the repair to the layer where the actual breakdown occurred.

Resolution: Accountability decisions become fairer because intent, force, and effect are no longer conflated. Repairs are more precise: a wording problem gets a wording fix, an authority problem gets a role clarification, a perlocutionary harm gets mitigation. False equivalences between what was said, what was done, and what happened disappear.

Reach for this when you hear…

[legal interpretation] “The notice says all the right words but it never actually gave notice because it arrived after the deadline — you have to test the wording, the act, and the effect separately.”

[management] “The manager called it a suggestion, but in this power structure everyone in the room heard an order — what was said and what was performed are not the same thing.”

[mediation] “The apology had apologetic wording but it took no responsibility and the other party felt worse afterward — an apology that does not perform the act of apologizing is not an apology.”

Mechanisms / Implementations

  • Context-Condition Testing: Tests whether the conditions a convention requires before participation may count as acceptance are actually met here — and, when one fails, names the layer where the coupling breaks.
  • Effect-Chain Tracing
  • Force Classification: Classifies what kind of act a message actually performs — notice, question, demand, offer, or ruling — so the response it genuinely compels can be told apart from the assent it merely implies.
  • Layer Separation Reframing
  • Literal Content Parsing: Splits a message into what it literally asserts or asks and what it merely presupposes, so the presupposition surfaces as a claim in its own right instead of riding in unexamined.
  • Repair Target Selection
  • Uptake Confirmation: Verifies that a supplied input actually arrived and was taken up in usable form at the point of action, rather than trusting that dispatch equals receipt.

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

Built directly on (2)

Also references 18 related abstractions

Variants

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

Legal Statement Force Analysis

Consent and Refusal Uptake Mapping

Apology / Commitment Effect Diagnosis

Instruction-Following Pragmatic Parse

Public Message Impact Decomposition