Coordination Artifact Kill Switch¶
Governance rule — instantiates Coordination Scaffold Load Control
A standing rule that lets a named owner unilaterally and reversibly pause or remove any coordination artifact that can no longer name the decision it improves — putting the burden of proof on keeping it, not killing it.
A Coordination Artifact Kill Switch is a standing governance rule granting a designated owner the authority to unilaterally and reversibly pause or remove any single coordination artifact — a recurring report, a standing meeting, a dashboard, a form, an approval step — the moment no one can name the decision it improves. Its defining idea is a reversal of the default. Ordinarily a coordination artifact persists until someone builds a case to remove it, and "removing coordination feels risky" keeps dead scaffolding alive indefinitely. The kill switch flips the burden of proof onto retention, and it makes removal cheap and reversible precisely so that flipping the default is safe rather than reckless.
Example¶
A national retail chain's analytics team maintains roughly 140 scheduled reports, accreted over a decade. One is a weekly regional-margin summary auto-emailed to sixty managers every Monday. Nobody remembers commissioning it, and no one can point to a decision it drives. Under the kill-switch rule, the reporting owner simply pauses it and watches. Over three quiet weeks, two managers write in asking where it went; fifty-eight say nothing. The report is rebuilt as an on-demand query for the two who used it, and fifty-eight inboxes — plus the pipeline job that generated it — are freed. Because the pause was reversible, the cost of being wrong was three weeks and one email, not a data outage.
The point of the example is the asymmetry it exposes: the report had been protected for years by the feeling that deleting a report might break something, even though no one could say what. The kill switch converts that vague dread into a cheap, reversible test.
How it works¶
A named owner holds the switch for a defined class of artifacts, and can act without convening a committee — low ceremony is the whole point. Removal is staged as pause, then observe, then retire, with a restore window so anything genuinely load-bearing announces itself before deletion becomes permanent. The retention test is explicit: to keep an artifact, someone must name the decision it improves or the constraint it satisfies; silence is a vote to remove. Artifacts under external mandate (legal, audit, contractual) are exempt and flagged as such. The distinguishing move against its siblings is that it is reactive and single-target: it fires on demand, on one artifact at a time, not on a schedule and not by merging bodies.
Tuning parameters¶
- Switch holder — how senior and how broadly scoped the owner is. A senior, broad holder acts fast but can overreach; a narrow one is safer but slower to reach the sprawl.
- Restore window — how long a paused artifact can be revived before deletion is permanent. Longer windows protect against Chesterton's-Fence errors; shorter ones realize the savings sooner.
- Scope per pull — whether the switch removes one artifact or a bundle. Bundling clears more at once but multiplies the blast radius of a mistake.
- Quiet-period length — how long silence must persist before a pause becomes a retirement. Longer periods catch rarely-used-but-real artifacts; shorter ones move faster.
- Appeal path — how a stakeholder reinstates a killed artifact. A clear appeal keeps the switch legitimate; no appeal invites resistance and workarounds.
When it helps, and when it misleads¶
Its strength is breaking the freeze in which removing coordination always feels riskier than keeping it: by making removal cheap and reversible, it turns "should we kill this?" into a three-week experiment instead of a fight. It is the fastest way to clear obviously dead scaffolding.
Its failure mode is Chesterton's Fence.[1] An artifact whose purpose is non-obvious — a compliance log that looks idle until an audit, a report one downstream team quietly depends on — can be killed by someone who never understood why it was there. A related misuse is killing artifacts that protect low-power actors, shifting the coordination burden downward where it is less visible rather than removing it. The guarding discipline is the reversible pause-and-observe step, the mandatory exemption for externally required artifacts, and a habit of asking who relied on this before permanence.
How it implements the components¶
pruning_or_consolidation_rule— the removal rule itself, applied to individual artifacts on demand with a reversed burden of proof.coordination_burden_owner— designates the specific person accountable for pulling the switch and for answering for what was removed.
It removes on demand but neither schedules expiry nor finds what to merge: the support_sunset_rule clock belongs to support_layer_sunset_review, and the coordination_recursion_detector that spots redundant forums worth fusing belongs to governance_forum_consolidation. Its nearest twin is the sunset review — which removes on a calendar where this removes on demand.
Related¶
- Instantiates: Coordination Scaffold Load Control — supplies the fast, reversible removal path for individual coordination artifacts.
- Consumes: coordination_load_audit — the audit surfaces the zero-value artifacts the switch is then aimed at.
- Sibling mechanisms: async_decision_log · coordination_load_audit · delegation_authority_matrix · exception_based_oversight · governance_forum_consolidation · handoff_path_pruning · meeting_budget · support_layer_sunset_review · work_before_metawork_ratio_dashboard
Editorial Notes¶
Form Classification¶
Form family: Rule, Policy & Commitment
Rationale: Coordination Artifact Kill Switch operates as a standing rule, threshold, contractual commitment, or policy constraint governing future conduct because it a standing rule that lets a named owner unilaterally and reversibly pause or remove any coordination artifact that can no longer name the decision it improves — putting the burden of proof on keeping it, not killing it.
Independent corroboration: The frozen evidence defines Coordination Artifact Kill Switch as 'A standing rule that lets a named owner unilaterally and reversibly pause or remove any coordination artifact that can no longer name the decision it improves — putting the burden of proof on keeping it, not killing it', so its operative form is Rule, Policy & Commitment.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Lean organizational design cohered removal of non-value-adding meetings, reports, and controls, with explicit ownership of process simplification.
Related originating lineages:
- Engineering & Design — Engineered shutdown and reversibility patterns supply the kill-switch structure used to retire a coordination artifact safely.
Review resolution: The mechanism governs organizational process artifacts, while engineering contributes the explicit kill-switch and reversibility model. Both reviewers identify synthesis; retaining the engineering lineage explains the named form.
Attribution caveat: The rule combines lean process pruning with an engineered reversible-shutdown concept.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
References¶
[1] Chesterton's Fence — G.K. Chesterton's dictum (in The Thing, 1929) that you should not remove a fence until you understand why it was put there. The reversible pause-and-observe step is the kill switch's deliberate concession to it: remove first, but cheaply and reversibly, so a hidden purpose can announce itself before deletion is final. registry ↩