Network Intervention Pilot¶
Experimental change process — instantiates Relation Rewiring
Tests a limited relation change before full rollout, using local monitoring to detect unwanted bottlenecks, exclusions, or dependency transfers.
A Network Intervention Pilot implements a relation change at deliberately limited scope — a real but bounded edge change in one site, segment, or population — instrumented locally so that new bottlenecks, exclusions, and dependency transfers surface before anyone commits to full rollout. Its defining property is that it does make a real rewire, just a small one, and treats it as an experiment: the change itself is the manipulated variable, and the go/no-go for scaling rests on observed second-order effects, not on the design's promise. This is what separates it from a workshop that only plans and from a full rollout that only executes — a pilot is a scoped, monitored, harm-checked live change whose whole purpose is to learn.
Example¶
A hospital system wants direct referral relationships between emergency-department crisis responders and community follow-up providers, bypassing a slow central intake that currently loses patients between the ED and aftercare. Rather than switch system-wide, it runs a Network Intervention Pilot in one region for a quarter. The new direct-referral edge is stood up for real — but only in that region (a scoped edge change). Referral completion rates and time-to-follow-up are monitored; so are the second-order effects the archetype warns about: are any patient types now excluded from the fast path, is any single follow-up provider being overloaded, has the dependency simply moved from central intake to one clinic? The setup is a live rewire confined to one region; the outcome is evidence — on whether the direct referral helps and on whom it quietly harms — that a system-wide rollout can then rest on or be stopped by.
How it works¶
- Scope the edge change — implement the real relation change, but bound it to one site, segment, or population.
- Instrument the intended effect — measure whether the rewire produces the behavior it was meant to.
- Instrument the second-order effects — watch specifically for new bottlenecks, excluded groups, and dependency that has merely transferred rather than reduced.
- Decide on the evidence — scale, adjust, or abort based on what the pilot observed, not on the original design's promise.
Tuning parameters¶
- Pilot scope — how large a site or segment; bigger pilots are more representative but riskier and costlier to reverse.
- Duration — how long it runs; longer reveals slow-building effects but delays the decision.
- Success and harm thresholds — pre-registered pass/stop lines; setting them in advance prevents rationalizing a marginal result after the fact.
- Blast radius — how reversible the scoped change is; a smaller, more reversible pilot lowers the cost of a bad result but may not stress the system realistically.
When it helps, and when it misleads¶
Its strength is that it converts an uncertain, hard-to-reverse rewire into a bounded experiment — you learn the second-order effects for the price of one region instead of the whole system. Treating the relation change as the manipulated variable is exactly the logic of a network intervention.[n1]
Its honest failure mode is weak external validity: a rewire that succeeds in a friendly, unrepresentative pilot site fails at scale because the pilot site was not typical. The classic misuse is piloting only where success is likely — a hand-picked motivated region — and then generalizing the rosy result. The guarding discipline is to choose a representative site and pre-register the harm thresholds, so the pilot can genuinely fail and the decision is made against evidence rather than hope.
How it implements the components¶
edge_change_set— the pilot implements a real, scope-limited relation change (the region's direct-referral edge).post_rewiring_monitoring— local instrumentation tracks both the intended effect and the second-order fallout.externality_and_harm_check— it watches specifically for excluded groups, overloaded providers, and transferred dependency.
It does NOT implement baseline_relation_map, rewiring_objective, or relation_change_authority — those belong to Stakeholder Realignment Workshop, which produces the negotiated design, objective, and mandate; a pilot consumes that design and tests a scoped version of it.
Related¶
- Instantiates: Relation Rewiring — Network Intervention Pilot is the mechanism that tests a relation change at limited scope before full rollout.
- Consumes: Stakeholder Realignment Workshop supplies the design, objective, and mandate the pilot puts to the test.
- Sibling mechanisms: Organizational Redesign · Workflow Rerouting · Stakeholder Realignment Workshop · Communication Channel Redesign · Partnership Restructuring · Dependency Injection or Adapter Substitution · Routing Table or Rule Update
Editorial Notes¶
Form Classification¶
Form family: Experiment, Test & Rehearsal
Rationale: Network Intervention Pilot operates as an active test, trial, simulation, drill, or rehearsal that generates evidence through a deliberate attempt or perturbation because it tests a limited relation change before full rollout, using local monitoring to detect unwanted bottlenecks, exclusions, or dependency transfers.
Independent corroboration: The frozen evidence defines Network Intervention Pilot as 'Tests a limited relation change before full rollout, using local monitoring to detect unwanted bottlenecks, exclusions, or dependency transfers', so its operative form is Experiment, Test & Rehearsal.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Sociology & Anthropology
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Social-network intervention research developed deliberate tie, segment, and structural changes as treatments rather than merely descriptions.
Related originating lineages:
- Organizational & Management Science — Organization-network redesign contributes attention to bottlenecks, exclusion, and dependency transfer.
- Statistics & Experimental Design — Pilot and field-experiment design contributed limited rollout, matched comparison, monitoring, and causal validation.
Review resolution: Both independent reviews agree on primary origin sociology_anthropology; reconciliation resolves reported_ambiguity, alternate_origin_disagreement. Formative alternate lineages retained: statistics_experimental_design, organizational_management. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages. Confidence is conservatively reconciled to medium, and encyclopedia_synthesis=true preserves the reviewers' boundary judgment.
Attribution caveat: Network interventions occur in public health, organizations, and sociology; the shared formative object is relational social structure.
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.
Notes¶
[n1] Network interventions (Thomas Valente) — a typology for deliberately changing a network's structure or behavior by targeting individuals, segments, ties (induction), or the pattern itself (alteration). It frames the relation change as the manipulated variable to be tested, which is the logic a pilot operationalizes at limited scope. ↩