Reversible Rollout Plan¶
A rollout governance plan — instantiates Cultural Friction Mediation Design
Stages adoption so any phase can be paused or rolled back on pre-declared criteria, keeping cultural misfit correctable and un-blamed instead of locked in.
Reversible Rollout Plan is a governance document that sequences adoption into reversible phases and, before launch, fixes the pause criteria, the rollback authority (who can stop it, and how fast), the repair responsibilities, and the value trip-wires that force a halt. Its distinguishing idea is that it engineers reversibility and pre-commitment into the rollout, so that discovering cultural misfit triggers a defined, low-drama correction rather than a fight — the plan's whole value is that stopping is cheap, authorized, and blameless because it was decided in advance. Unlike a pilot, which tests one variant in one place, this governs the entire staged adoption and its exits.
Example¶
A national tax authority must mandate electronic invoicing. A big-bang switch-on risks paralyzing small traders whose bookkeeping norms and connectivity differ sharply by region. The Reversible Rollout Plan sequences it into gated phases — voluntary, then large firms, then region-by-region for small businesses. Before launch it pre-declares the criteria that pause the next wave (say, if more than a set share of a region's invoices fail to file, or the support backlog exceeds a set number of days); it names who can pull the trigger — a specific official, within 24 hours, without needing sign-off from the sponsors who want it to proceed; it keeps the paper filing path legally valid as a genuine rollback; and it writes one nonnegotiable line: no penalties on traders during a paused wave. When a rural region's first month shows mass filing failures tied to intermittent connectivity, the pause fires on schedule, the paper path absorbs the gap, penalties stay suspended, and the fix — an offline-submission mode — is built before the wave resumes. No emergency, no blame.
How it works¶
- Sequence into survivable phases. Slice adoption so a bad phase is contained, not catastrophic.
- Pre-declare the stop conditions. Set pause and rollback criteria before launch, so halting is not a judgment call made under pressure.
- Vest the stop button independently. Give rollback authority to someone insulated from the sponsors most invested in proceeding.
- Keep the fallback alive. Maintain a real prior path so rollback is genuine, not nominal.
- Name repair owners, frame it no-blame. Assign who fixes misfit and treat a pause as designed, not as failure, so signals stay honest.
Tuning parameters¶
- Phase granularity — how finely adoption is sliced. Finer phases are more reversible but slower to complete.
- Pause-criteria strictness — how easily a halt trips. A hair-trigger protects the host but stalls momentum; a loose trigger lets misfit accumulate.
- Rollback-authority placement — who holds the stop button and how independent they are of the sponsor. That independence is what makes reversibility credible.
- Fallback durability — how long the old path stays alive as a real exit. Retiring it early saves cost but quietly converts "reversible" into "committed."
- Repair ownership and blame frame — who fixes misfit and whether stopping reads as failure or as design. A no-blame frame is what keeps friction signals honest.
When it helps, and when it misleads¶
Its strength is that it makes cultural misfit correctable: it turns "we've already announced it, we can't stop now" into a pre-authorized, low-drama pause, and it keeps adoption honest because problems surface instead of being buried by people who fear blame.
Its failure mode is that reversibility can be nominal — a plan that says rollback but has quietly retired the fallback, or that vests the stop button in the very sponsors driving the rollout, so escalation of commitment takes over and the pause never fires.[n1] The classic misuse is to adopt reversible-rollout language for legitimacy while engineering the thing to be effectively irreversible. The discipline is to keep a live fallback, place the stop authority outside the sponsor, and rehearse a rollback once so it is known to actually work.
How it implements the components¶
Reversible Rollout Plan fills the governance-and-exit slice of the archetype's machinery — the standing rules a rollout document sets:
reversible_rollout_and_repair_path— it is this: the phased, pausable, rollback-able sequence with named repair owners and a live fallback.nonnegotiable_value_boundary— it operationalizes the value limits as hard trip-wires and no-harm guarantees that force a halt the moment they are crossed.
It operationalizes — but does not itself decide — the nonnegotiable value boundaries; those are established and audited up front by the Trust and Legitimacy Checklist. It does not verify legitimacy or consent (that is the Trust and Legitimacy Checklist), nor generate the friction signals its pause criteria consume (those come from the Pilot Localization Trial and the Workaround Observation Walkthrough).
Related¶
- Instantiates: Cultural Friction Mediation Design — the governance that keeps a cultural adaptation correctable at scale.
- Consumes: Trust and Legitimacy Checklist supplies the value boundaries it enforces; the Pilot Localization Trial supplies friction thresholds and a proven adaptation to scale.
- Sibling mechanisms: Pilot Localization Trial · Trust and Legitimacy Checklist · Workaround Observation Walkthrough · Community Review Panel
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Reversible Rollout Plan operates as a static representation, map, specification, schema, or prospective plan that externalizes information because it stages adoption so any phase can be paused or rolled back on pre-declared criteria, keeping cultural misfit correctable and un-blamed instead of locked in.
Independent corroboration: The frozen evidence defines Reversible Rollout Plan as 'Stages adoption so any phase can be paused or rolled back on pre-declared criteria, keeping cultural misfit correctable and un-blamed instead of locked in', so its operative form is Representation, Specification & Plan.
Nearest alternative: Rule, Policy & Commitment — Reversible Rollout Plan includes features of a standing rule, threshold, contractual commitment, or policy constraint governing future conduct, but its defining operation is a static representation, map, specification, schema, or prospective plan that externalizes information.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Phased adoption with pause and rollback criteria is organizational change-management practice.
Related originating lineages:
- Computer Science & Software Engineering — Incremental software rollout materially shaped explicit rollback at each phase.
- Sociology & Anthropology — Cultural-fit and non-blaming interpretation contribute sensitivity to local practice.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: stages adoption so any phase can be paused or rolled back on pre-declared criteria, keeping cultural misfit correctable and un-blamed instead of locked in.
Review resolution: Both blind reviewers agree that organizational_management is the primary historical origin. Explicit reconciliation of alternate origin disagreement, origin mode disagreement starts from reviewer_a’s mechanism-specific evidence: Phased adoption with pause and rollback criteria is organizational change-management practice. Reviewer A proposed alternates=computer_science, sociology_anthropology, origin_mode=cross_disciplinary_synthesis, domain_reach=multi_domain, and encyclopedia_synthesis=true; reviewer B proposed alternates=systems_cybernetics, origin_mode=single_lineage, domain_reach=multi_domain, and encyclopedia_synthesis=true. The final record retains every independently supported alternate from either review (computer_science, sociology_anthropology, systems_cybernetics) without an arbitrary cap, selects origin_mode=cross_disciplinary_synthesis to represent the combined lineage evidence, and keeps domain_reach=multi_domain and encyclopedia_synthesis=true from the more mechanism-specific assessment. Present-day transfer is recorded as reach and is not treated as proof of historical origin.
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¶
Reversibility is only as real as the fallback and the independence of the stop authority. A Reversible Rollout Plan whose fallback has been retired, or whose stop button sits with the sponsor, is reversible in name only — and worse than none, because it lends the credibility of "we can always roll back" to a decision that in practice cannot be undone.
[n1] Escalation of commitment — the tendency to keep investing in a failing course of action because of what has already been sunk into it (studied by Barry Staw and others). It is the force a reversible rollout is built to resist: a pause fires only if the authority to stop is insulated from the people most committed to going on, which is why placement of the stop button is the load-bearing design choice. ↩