Skip to content

Interaction Script Revision

A practice redesign — instantiates Self-Fulfilling Prophecy Interruption

Rewrites the recurring lines, prompts, and moves of everyday interactions so low expectations stop riding into behavior through ordinary conversational habit.

Many prophecy loops are not written into policy at all — they live in the ordinary scripts people repeat: the standard opener, the recurring question, the handoff phrase, the meeting move. Interaction Script Revision rewrites those concrete micro-behaviors so the low expectation stops traveling through habit. Its defining move is that it operates at the level of the actual words and moves of a recurring exchange, not the surrounding system: it finds the loaded line that carries distrust or a lowered bar into every repetition, and replaces it with one that carries equal trust, challenge, and warmth. The counter-pattern is thereby embedded in what people literally say, so it fires automatically the next hundred times the script runs.

Example

A bank's collections calls open from a script: "Our records show you've missed payments — when can you pay?" The framing presumes bad faith, and the presumption provokes exactly the defensiveness that gets logged as "evasive customer," confirming the expectation and hardening the next call. The revision rewrites the opener as a diagnostic, problem-solving prompt: "Let's find an arrangement that works for you — what changed?" The changed opening changes the customer's response; on genuinely struggling accounts, recovery improves, because the interaction no longer manufactures the evasion it went in expecting. Nothing about the policy changed — only the recurring line.

How it works

What distinguishes it is that it edits embodied conversational habit, not structure or allocation:

  • Find the loaded script — the recurring prompt, opener, handoff phrase, or meeting move that carries a lowered expectation.
  • Rewrite the line to carry equal expectation — same purpose, but phrased with the trust, challenge, and warmth the target had been denied.
  • Standardize and embed — make the revised script the default (a card, a template, a trained habit) so the counter-pattern repeats without effort.

Tuning parameters

  • Which scripts — openers, diagnostic questions, handoff lines, coaching prompts, meeting moves; the ones repeated most carry the most loop.
  • Prescriptiveness — verbatim script versus guideline; tighter wording ensures consistency but risks sounding robotic.
  • Warmth/challenge balance — how much the new line raises the bar versus signals support; both must rise together to counter a low-expectation loop.
  • Rollout — trained habit, pocket card, or embedded system prompt; how the revised script actually reaches the moment of use.

When it helps, and when it misleads

Its strength is reaching loops that policy cannot touch, because they are lodged in speech habits no rule addresses. It is a direct counter to behavioral confirmation[1] — the way an expectation, expressed in how we talk to someone, elicits the very behavior we expected.

It misleads when the new script is delivered robotically or insincerely (people detect a memorized line and read it as manipulation), and it fails when the wording changes but the underlying attitude, allocation, or consequence does not — new words over the same withheld opportunity. The classic misuse is theater: a friendlier opener bolted onto an unchanged system. The discipline is to pair script revision with a genuine treatment change and to check that the revised interaction is delivered as meant, not merely recited.

How it implements the components

  • interaction_pattern_change — it rewrites the recurring interpersonal behavior so the target stops receiving systematically lower trust, challenge, or warmth in ordinary exchanges.
  • counterexpectation_intervention — the revised script is the deliberate counter-pattern, embedded directly in speech so it fires automatically.

It does not redesign the feedback system's structure (expectation_feedback_loop, Feedback-Loop Redesign), redistribute opportunity (agency_support, Balanced Opportunity Assignment), or monitor outcomes (outcome_monitor, Outcome Monitoring Review).

Notes

It sits between two siblings. Neutral Treatment Protocol sets a standardized rule for treatment; this changes the words through which treatment is enacted — a protocol says what everyone must get, a script rewrites how it is said. And where Feedback-Loop Redesign restructures the feedback system, this edits the recurring line. Reach for it when the loop is embodied in habit, not policy.

References

[1] Behavioral confirmation — the well-documented pattern in which one person's expectation about another shapes their interaction in a way that leads the other to behave consistently with the expectation. Rewriting the recurring script is a direct intervention on the interaction through which that confirmation travels. ↩