Infrastructure Plus Incentive Package¶
Method — instantiates Catalytic Pairing
Pairs a capability-enabling infrastructure change with an incentive that makes the new capability worth using.
An Infrastructure Plus Incentive Package is the design method that names an ability–motivation pair — a capability-enabling infrastructure change as the focal factor and an incentive as the potentiating factor — and then earns the pairing by comparing it against each half deployed alone. Its defining move is the asymmetry it insists on making explicit: infrastructure makes an action possible but not attractive; an incentive makes it attractive but, without the infrastructure, impossible. Deciding which element is the focal capability and which is the motivating potentiator, and demanding a baseline comparison against infrastructure-only and incentive-only, is the whole of the method. What makes it this mechanism: it is about identifying and validating the ability-plus-motivation relationship — not scheduling it, packaging it, or piloting it.
Example¶
A region wants residents to switch to electric vehicles. Two levers are on the table. Public fast-charging stations are the focal factor — the infrastructure that makes owning an EV feasible for people without a garage. A purchase rebate is the potentiating factor — it makes buying one worth the money now, before the long-run savings arrive. The method's discipline is to name the pair directionally (the rebate potentiates uptake of a capability the chargers make possible) and then run an independent baseline comparison across regions: places that built chargers but offered no rebate see modest adoption (ability without enough motivation); places that offered rebates but had sparse charging also stall (motivation blocked by range anxiety); only places with both cross the adoption threshold.
Setup to outcome: that three-way read — infrastructure-alone, incentive-alone, and both — is what proves the effect is genuine potentiation and not either factor quietly doing the work by itself.[n1] It also tells the designers where to push: if the incentive-only arm is nearly flat, the binding constraint is infrastructure, and more rebate money would be wasted.
How it works¶
- Name the focal capability. State the infrastructure or ability whose use is to be increased — the thing that is currently possible-in-principle but unused.
- Name the potentiating incentive. State the motivation directionally: it exists to make the focal capability worth using, not as a standalone good.
- Run the independent baseline. Compare the pair against capability-alone and incentive-alone so the lift is attributed to the pairing rather than to either factor.
- Size each to its threshold. Sub-threshold on either side (too few chargers, too small a rebate) and the pair never lights up; the method sets each factor at the level where benefit appears.
Tuning parameters¶
- Directionality and emphasis — infrastructure-led (build first, incentivize adoption) versus incentive-led (reward first, let demand pull infrastructure). Which leads depends on which constraint currently binds.
- Incentive form and decay — subsidy, rebate, access, or recognition, and whether it is a temporary kick-start or a standing payment. Temporary is cheaper and avoids dependence but risks a cliff; standing sustains use but never tests self-sufficiency.
- Threshold sizing — how much infrastructure and how large an incentive before the pair produces benefit. Under-sizing wastes both; over-sizing wastes budget past the point of saturation.
- Baseline rigor — a natural experiment across comparable regions versus a modeled counterfactual. More rigor buys a cleaner attribution at the cost of time and design effort.
When it helps, and when it misleads¶
Its strength is that it prevents the two symmetric wastes of one-sided design: building infrastructure nobody uses, and dangling incentives for something people cannot actually do. By demanding the alone-arms, it forces a team to locate the binding constraint instead of spending on both out of caution.
Its failure mode is incentive dependence — usage collapses the moment the incentive ends, because the infrastructure never became self-sustaining and the "adoption" was really a subsidy in disguise. A quieter failure is a confounded baseline: the regions that got both also happen to be wealthier, so income, not the pairing, drives the result. The classic misuse is declaring victory from the both-arms number alone, mislabeling ordinary addition as potentiation. The guarding discipline is to always carry the alone-arms and to watch what happens when the incentive sunsets — a pairing is only catalytic if the capability keeps being used after the motivation is withdrawn.
How it implements the components¶
focal_factor— names the capability-enabling infrastructure whose use is the target, keeping the design anchored to a concrete ability rather than a vague "package."potentiating_factor— names the incentive as the element that makes the focal capability worth using, stated directionally so the potentiation is explicit.independent_baseline_comparison— compares the pair against infrastructure-alone and incentive-alone, so the observed lift is attributable to the pairing and not to either factor working solo.
This method identifies and validates the pair; it does not operate it. It does not implement coupling_or_sequencing_rule — the timing and order at which the factors must meet is Combination Therapy Protocol's and Integrated Care Bundle's work — nor saturation_and_interference_monitor, the watch for diminishing returns, which is Complementary Product Bundle's.
Related¶
- Instantiates: Catalytic Pairing — supplies the ability-plus-motivation naming and the baseline proof that the pair beats each half alone.
- Sibling mechanisms: Combination Therapy Protocol · Complementary Product Bundle · Integrated Care Bundle · Paired Rollout Pilot · Tool Plus Process Redesign · Factorial Experiment · Catalyst-Cofactor System · Training Plus Feedback Loop
Editorial Notes¶
Form Classification¶
Form family: Intervention, Treatment & Transformation
Rationale: The package directly changes capability and motivation by installing enabling infrastructure and pairing it with an incentive to use it.
Nearest alternative: Experiment, Test & Rehearsal — Use may be piloted, but the intended success is adoption and changed capacity rather than evidence generation.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Behavioral Economics
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Pairing capability with motivation is most directly rooted in behavioral intervention and incentive-design traditions.
Related originating lineages:
- Engineering & Design — The enabling substrate materially comes from engineered infrastructure rather than persuasion alone.
- Psychology — Behavior models linking motivation, ability, and prompts materially shape the package logic.
- Public Administration & Policy — Policy packages materially established combining structural provision with adoption incentives.
Review resolution: Both independent reviews place the primary lineage in behavioral_economics. The queued differences (alternate_origin_disagreement) concern secondary metadata rather than primary provenance. The final retains engineering_design, public_administration_policy, psychology only where a reviewer supplied a formative-lineage rationale; this does not convert downstream applicability into origin. origin_mode=cross_disciplinary_synthesis because the entry's present form deliberately composes methods from the documented lineages. domain_reach=multi_domain records application breadth separately from provenance.
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] B. J. Fogg's Behavior Model holds that a behavior occurs only when motivation, ability, and a trigger converge at the same moment — no amount of motivation produces the behavior if ability is absent, and vice versa. Infrastructure supplies ability and an incentive supplies motivation, which is why pairing them (rather than maximizing either alone) is the natural intervention, and why the alone-arms of the baseline comparison tend to underperform. ↩