Script-Revision Workshop¶
Governance process — instantiates Event-Script Structuring
A periodic governance session where a standing body weighs accumulated evidence, re-scopes the situation boundary, ratifies changes to the canonical script, and records who changed what and why.
A Script-Revision Workshop is the legislature for a script. Its defining move is ratification across accumulated evidence: rather than reacting to a single incident, a standing body convenes on a cadence, looks across many reviews and flagged patterns at once, decides which proposed changes become the new canon, re-draws the situation's boundary where reality has shifted, and records the change with its rationale. It is where a script is authoritatively changed — a deliberate, governed act, distinct from noticing a problem or diagnosing one. Its outputs are an updated canonical script and a provenance entry; nobody leaves the room having merely observed.
Example¶
A city's 311 service center governs the scripts its agents use to handle resident requests. Each quarter a revision workshop convenes: the operations lead, two senior agents, an accessibility advocate, and a records owner. They arrive with a packet — three months of flagged breaches, several violation reviews, and complaint themes. This quarter the pattern is clear: the "report a pothole" script keeps failing when residents report hazards that aren't potholes but downed limbs, which have a different responsible department. The body decides to re-scope the boundary, splitting "road hazard" into two situation classes with distinct routing, and applies its update rule (a change needs evidence from at least two independent sources — here, breach logs and complaint data both point the same way). They ratify the split, and the records owner writes the provenance entry: what changed, the evidence behind it, who approved it, effective date, and the version it supersedes. The workshop's product is a governed, traceable change to the canonical script — not a diagnosis, and not a suggestion.
How it works¶
The workshop applies an explicit script-update rule: a stated threshold for what evidence justifies a change (how many independent signals, how strong) so revisions aren't driven by the last loud incident. It examines and, where warranted, redraws the situation-class boundary — splitting an overloaded class, merging redundant ones, or narrowing scope where the script was over-applied. Every ratified change lands in the script-provenance record: the what, why, who, and when, plus the prior version it replaces, so the script's history is auditable and reversible. The body is standing and cross-functional by design, so changes carry the authority — and the diverse scrutiny — that a single reviewer's patch cannot.
Tuning parameters¶
- Revision cadence — how often the body meets. Frequent revision keeps scripts current but risks churn and change-fatigue; rare revision is stable but lets drift accumulate.
- Evidence threshold — how much converging evidence the update rule demands before a change is accepted. A high bar prevents overreacting to anomalies but delays needed fixes.
- Boundary-change latitude — how freely the body may re-scope situation classes versus only editing within them. Wide latitude adapts to structural shifts but can destabilize downstream artifacts.
- Quorum and representation — who must be present for a change to be valid. Broad representation legitimizes changes but slows the process and can deadlock.
When it helps, and when it misleads¶
Its strength is keeping a script alive without letting it thrash — the governed middle path between a frozen procedure and a script quietly rewritten by whoever touched it last. At its best it is double-loop learning: the body doesn't just tune actions within the current script, it questions and revises the governing script itself.[n1]
Its failure mode is capture and inertia in either direction — a body that rubber-stamps every proposal churns the field with constant change, while one that demands unattainable consensus lets the script rot as agents route around it. A subtler misuse is treating the workshop as a venue to relitigate single incidents, importing the vividness of one case in place of the evidence threshold. The discipline is to hold the update rule honestly (evidence, not anecdote), to keep the provenance record complete so changes are reversible, and to protect the cadence so revision is routine rather than a crisis response.
How it implements the components¶
script_update_rule— it applies the explicit evidence threshold that governs when and how the canonical script changes.situation_class_boundary— it re-scopes classes, splitting, merging, or narrowing them as reality shifts.script_provenance_record— it records every ratified change with rationale, authorship, date, and the version superseded.
It ratifies and legislates but does not generate the raw material: the counter_script_library of rival readings comes from Counter-Script Review, and the causal_link_map of any single incident comes from Expectation-Violation Review. Those siblings surface and diagnose; the workshop decides.
Related¶
- Instantiates: Event-Script Structuring — supplies the governed way a script is authoritatively changed over time.
- Consumes: Expectation-Violation Review and Counter-Script Review — the accumulated diagnoses and rival readings that become its evidence packet.
- Sibling mechanisms: Breach Checklist · Case-Intake Script · Counter-Script Review · Expectation-Violation Review · Interface-Flow Script · Role-Play Rehearsal · Scenario Walkthrough · Script-Card Template · Service-Blueprint Script
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Script Revision Workshop operates by convenes participants to examine evidence, negotiate boundary changes, and revise shared scripts. That concrete deployed or enacted form is Communication, Facilitation & Learning under the frozen taxonomy.
Nearest alternative: Organization, Role & Governance — Although Organization, Role & Governance can support this mechanism, the frozen evidence makes its operative form the act that convenes participants to examine evidence, negotiate boundary changes, and revise shared scripts; the alternative is therefore secondary rather than defining.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Periodic evidence-based governance of standing procedures is organizational change control.
Related originating lineages:
- Ethnography & Qualitative Methods — Accumulated lived evidence independently reveals situation-boundary mismatch.
- Law & Governance — Ratification and recorded authority materially legitimize canonical-script changes.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a periodic governance session where a standing body weighs accumulated evidence, re-scopes the situation boundary, ratifies changes to the canonical script, and records who changed….
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, domain reach disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined record shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance, and encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Double-loop learning — Chris Argyris and Donald Schön's term for learning that questions and revises the governing assumptions and rules behind action, rather than merely adjusting actions to better satisfy the existing rules (single-loop learning). ↩