Escalate from behavior description to pattern-naming…
When someone repeatedly violates a clearly stated boundary, escalate from describing the behavior to naming the pattern ('I've mentioned several times that...') before consequences, as pattern-naming often produces adjustment where single-instance feedback did not.
Why This Is a Rule
Single-instance feedback addresses the behavior: "The meeting ran 30 minutes over today." Pattern-naming addresses the system: "This is the fourth time in two weeks our meetings have run over significantly." The shift from behavior to pattern changes the conversation from "this one thing happened" to "this keeps happening" — which communicates that the issue isn't a one-off but a recurring problem requiring structural change.
Pattern-naming is psychologically distinct from repetition. Saying the same behavior feedback five times produces desensitization: the person habituates to the same message and discounts it. Naming the pattern — explicitly referencing the recurrence — escalates the severity without escalating the emotion. "I've mentioned several times that..." signals: this has moved from an isolated request to a documented pattern, and the next step is consequences.
This creates an escalation sequence with three levels: behavior description (first occurrence), pattern-naming (repeated occurrences), consequences (persistent despite pattern-naming). The intermediate step — pattern-naming — often produces the adjustment that individual behavior feedback couldn't, because it frames the issue as a pattern the person needs to own rather than an event they can dismiss.
When This Fires
- When single-instance boundary feedback has been given 2-3 times without change
- Before escalating to consequences (Enforce boundaries consistently — inconsistent…) — pattern-naming is the intermediate step
- When the boundary violation seems unintentional but persistent
- Complements Graduate your refusals (graduated refusal) with the specific escalation technique
Common Failure Mode
Repeating behavior-level feedback without naming the pattern: "Please don't interrupt during deep work." (said for the fifth time). Each instance sounds like the first to the person — they treat it as a one-off request each time. Pattern-naming: "I've asked five times now about interruptions during deep work. This is becoming a pattern that I need you to address." This changes the frame from "another request" to "a pattern you need to take seriously."
The Protocol
(1) When a boundary has been violated despite 2-3 instances of behavior-level feedback → escalate to pattern-naming. (2) Name the pattern explicitly: "I've mentioned [number] times over [period] that [boundary]. This is a pattern, not a one-time thing." (3) Ask for systemic change: "What can we do to make sure this doesn't keep happening?" This shifts responsibility from you (repeatedly requesting) to them (solving the pattern). (4) If pattern-naming produces change → the escalation worked. Return to normal monitoring. (5) If the pattern continues after being named → proceed to consequences (Enforce boundaries consistently — inconsistent…). The person was given behavior feedback (level 1), pattern awareness (level 2), and now faces consequences (level 3).