Expectation-Violation Review¶
Review protocol — instantiates Event-Script Structuring
A structured after-the-fact review that reconstructs a single encounter where the script was violated, tracing the causal chain and gathering each participant's account to explain what actually happened.
An Expectation-Violation Review is the retrospective inquest into one broken encounter. It starts after the fact, from a specific case in which the script's expected sequence did not hold, and its entire object is understanding: reconstructing the causal chain that produced the deviation and collecting the accounts of everyone who was there, so the organization learns why the situation diverged from its template. It is not a live alarm and it is not a legislative act. It deliberately stops short of rewriting anything — it produces an explained case and a recommendation, and hands that upstream.
Example¶
At a retail bank branch, a wire transfer that should have followed the routine "customer-initiated outbound wire" script instead sent funds to an account the customer later disputed. An expectation-violation review convenes on that single incident. It reconstructs the causal link map step by step: the customer arrived flustered and time-pressured, the teller skipped the callback-verification step because the "customer is a known regular" sub-script felt reassuring, a supervisor override that should have gated the amount was pre-approved in a batch that morning, and the fraudster's story exploited exactly that gap. It then gathers perspectives — the teller's account of the pressure, the supervisor's account of the batch approval, the customer's account of the phone call that set them up. The output is a causally explained narrative — "verification was skipped under time pressure because the override gate had been pre-cleared" — plus a recommendation to the revision body. The review does not itself change the wire script; it explains this breach well enough that someone can.
How it works¶
The protocol reconstructs the encounter as a causal link map, not a blame timeline: each event is connected to the conditions that made the next one likely, so the review can see where the real fork was rather than where the last human touched it. It layers in participant perspectives, taking each actor's own account of what they saw and expected, because a violation usually looks different from each seat and the discrepancies are diagnostic. It classifies the finding — was this a one-off, a latent flaw in the script, or a legitimate case the script never anticipated — and forwards a recommendation. Throughout, it holds to interpretation: naming causes and framing options, never enacting the change.
Tuning parameters¶
- Depth of causal reconstruction — how many links back the map is traced. Deep tracing finds root conditions but costs time and can over-fit a single case.
- Perspective completeness — how many of the involved parties are actually interviewed. Full coverage exposes discrepancies; partial coverage is faster but inherits the loudest voice's framing.
- Blame stance — how firmly the protocol separates what the system made likely from who acted. A strong separation surfaces honest accounts; a weak one drives them underground.
- Recommendation firmness — whether the output is a diagnosis only or a diagnosis with a proposed fix. Firmer recommendations speed change but can pre-empt the deliberating body's judgment.
When it helps, and when it misleads¶
Its strength is turning a single painful surprise into transferable understanding — the difference between "the teller messed up" and "the override gate created a skippable verification under time pressure." Held well, it embodies a just culture, which treats a violation as data about the system rather than an occasion to punish an individual, and so keeps future accounts truthful.[n1]
Its failure mode is hindsight-driven distortion: reviewing an event whose outcome is already known, the chain looks more obvious and more avoidable than it was, and the analysis converges on the nearest person. Its classic misuse is quietly sliding from review into rewrite, patching the script in the same meeting on the strength of one vivid case. The discipline is to reconstruct causes before assigning fault, to weigh whether one incident warrants any change at all, and to route confirmed patterns to the body that governs the script rather than editing it in the room.
How it implements the components¶
causal_link_map— its core artifact: the reconstructed chain of conditions and events that produced the deviation.participant_perspective_layer— it collects each actor's own account, using the discrepancies between them diagnostically.
It reconstructs a breach after the fact but does not catch one as it happens — the breach_detector and the live expected_event_sequence checks belong to its nearest twin, Breach Checklist — and it does not enact the fix: the script_update_rule is the province of Script-Revision Workshop. This review only explains and recommends.
Related¶
- Instantiates: Event-Script Structuring — supplies the after-action inquiry that converts breaches into understanding.
- Consumes: Breach Checklist — the flagged breaches that become the cases this review investigates.
- Sibling mechanisms: Breach Checklist · Case-Intake Script · Counter-Script Review · Interface-Flow Script · Role-Play Rehearsal · Scenario Walkthrough · Script-Card Template · Script-Revision Workshop · Service-Blueprint Script
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Expectation-Violation Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a structured after-the-fact review that reconstructs a single encounter where the script was violated, tracing the causal chain and gathering each participant's account to explain what actually happened.
Independent corroboration: The frozen evidence defines Expectation-Violation Review as 'A structured after-the-fact review that reconstructs a single encounter where the script was violated, tracing the causal chain and gathering each participant's account to explain what actually happened', so its operative form is Assessment, Review & Assurance.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Reconstructing a violated interaction script derives from sociological and anthropological accounts of roles, norms, and event scripts.
Related originating lineages:
- Ethnography & Qualitative Methods — Multi-participant accounts and contextual reconstruction materially shape the review method.
- Psychology — Expectancy-violation and social-cognitive research materially contribute causal interpretation of surprise.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Independent reviewer agreement; medium confidence.
Notes¶
[n1] Just culture — a principle prominent in safety science (associated with James Reason and Sidney Dekker) that responds to error by asking what in the system made it likely, distinguishing honest mistakes from reckless conduct rather than defaulting to individual blame, so that people keep reporting what actually happened. ↩