Adoption Bottleneck Mapping¶
Method — instantiates Horizon-Calibrated Impact Forecasting
Enumerates and sequences the concrete integration, training, procurement, trust, standards, and regulatory frictions that gate near-term impact — and attaches a watch-trigger to each.
When a promising capability fails to transform anything in its first year, the reason is almost never the capability — it is the queue of unglamorous prerequisites standing between the demo and the workflow. Adoption Bottleneck Mapping turns "it just isn't scaling yet" into a named, ordered inventory of the specific frictions that must be cleared before near-term impact can begin: system integration, operator retraining, procurement cycles, user trust, missing standards, regulatory sign-off. It is strictly a present-tense instrument — it catalogues the obstacles that exist now and sequences their dependencies. It does not predict how impact will accelerate once they fall; that forward projection belongs to a different sibling. Its whole job is to explain, concretely, why the near-horizon impact claim should be smaller and slower than the headline suggests.
Example¶
A mid-size aerospace-parts manufacturer buys a bank of metal 3D printers expecting an immediate collapse in lead times. Adoption Bottleneck Mapping is the step that says not yet, and here is exactly why. It lists the frictions gating near-term impact: qualifying each printed alloy against aerospace material standards, retraining machinists who have never designed for additive processes, redesigning legacy parts for printability inside the existing CAD toolchain, procuring certified feedstock through a supplier base that doesn't exist yet, and getting quality-assurance to sign off a process with no track record.
Each friction is rated gating (blocks the use case entirely — material certification) or merely slowing (drags but doesn't stop — operator ramp-up), then sequenced by dependency: no certification, no production part, no matter how fast the printer runs. The output is a map showing which bottleneck blocks which use case, with a watch-trigger on each — "first alloy certified," "twenty parts redesigned," "second feedstock supplier onboarded." That map is what converts a breathless "cuts lead times 80% this quarter" into "one non-critical bracket family this year; the rest gated on certification that historically takes eighteen months."
How it works¶
- Categorize the frictions. Sort every obstacle into technical, organizational, procurement, trust, standards, and regulatory buckets so none is silently omitted — near-term overestimation almost always comes from forgetting a whole category.
- Grade gating vs. slowing. Separate the frictions that stop impact from those that merely tax it; only the gating ones cap the near-horizon claim.
- Sequence the dependencies. Order the bottlenecks so that prerequisites-of-prerequisites are visible; the binding constraint is whichever gating friction is furthest upstream.
- Attach a resolution signal. Give every bottleneck an observable trigger for when it clears, so the near-term forecast is revised as reality moves rather than on a calendar.
Tuning parameters¶
- Friction taxonomy granularity — a coarse six-bucket sweep or a fine sub-itemized list. Finer catches hidden complements but risks paralysis and false precision.
- Gating threshold — how severe a friction must be to count as gating rather than slowing. Set it strict and the near-term claim looks achievable; set it loose and everything looks blocked.
- Adopter scope — whose friction you map (the pilot team, the median user, the laggard segment). The bottleneck that gates the enthusiast is not the one that gates the mainstream.
- Watch-trigger sensitivity — how strong a resolution signal must be before you reforecast. Twitchy triggers churn the forecast; sluggish ones let it drift.
When it helps, and when it misleads¶
Its strength is that it makes near-term overestimation concrete and actionable: instead of a vague discount on the hype, you get a sequenced list of the exact things that must happen first, which doubles as a work plan. It is the mechanism that keeps a spectacular demo from being budgeted as a deployment.
Its honest failure mode is that a friction inventory can be weaponized. Because every real transition has a long list of obstacles, an unsympathetic mapper can pile them up to make any disruptive innovation look hopeless — the archetype's warning about suppressing genuine change by overemphasizing near-term friction. It also tends to miss that many bottlenecks dissolve not by being cleared one-by-one but by the arrival of a complementary asset that reroutes around them.[n1] The guarding discipline is to pair every bottleneck with a plausible resolution path and to retire a friction from the map the moment it clears — the map is an input to a horizon-indexed forecast, never a veto.
How it implements the components¶
adoption_friction_and_complement_map— this is the mechanism's product: the categorized, sequenced inventory of the social, technical, procurement, standards, and regulatory prerequisites near-term impact waits on.update_trigger_and_revision_cadence— each mapped bottleneck carries an observable resolution signal, so clearing a friction is precisely the event that fires a scoped near-term reforecast.
It does not model how those frictions eventually resolve and reinforce one another into long-run acceleration — that projection is compounding_pathway_map and nonlinear_realization_curve_model, built by Compounding Trajectory Modeling, its nearest twin; nor does it build the external base_rate_and_reference_class_anchor of Technology Impact Base-Rate Review.
Related¶
- Instantiates: Horizon-Calibrated Impact Forecasting — Adoption Bottleneck Mapping supplies the near-horizon friction that keeps early impact claims honest.
- Sibling mechanisms: Compounding Trajectory Modeling · Technology Impact Base-Rate Review · Three-Horizons Impact Review · Horizon-Split Forecast Canvas · Hype Deflation Checklist · Impact Signal Dashboard · Staged Option Investment Plan · Near-Term De-escalation / Long-Term Sustain Gate · Forecast Backtesting Cadence
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: The mechanism enumerates and sequences the concrete integration, training, procurement, trust, standards, and regulatory frictions that gate near-term impact — and attaches a watch-trigger to each, so its operative form is offline analysis, modeling, or optimization.
Independent corroboration: The frozen evidence defines Adoption Bottleneck Mapping as 'Enumerates and sequences the concrete integration, training, procurement, trust, standards, and regulatory frictions that gate near-term impact — and attaches a watch-trigger to each', so its operative form is Analysis, Modeling & Optimization.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Innovation & Entrepreneurship
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Mapping integration, procurement, trust, training, standards, and regulatory barriers between a capability and scaled impact is a technology-adoption and innovation-diffusion practice.
Related originating lineages:
- Futurism & Strategic Foresight — Watch indicators and horizon-calibrated impact claims contribute the anticipatory use.
- Organizational & Management Science — Dependency mapping and implementation planning contribute the sequenced bottleneck map.
- Public Administration & Policy — Procurement, regulation, standards, and institutional capacity supply major adoption gates.
Review resolution: Mapping the integration, procurement, trust, standards, and regulatory constraints that gate diffusion is rooted in innovation and entrepreneurship. Foresight, organizational implementation, and public policy materially combine in the page's horizon-calibrated procedure, supporting the synthesis classification.
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] The idea that an innovation's payoff often depends on complementary assets — distribution, standards, skills, adjacent infrastructure — as much as on the core capability itself, from David Teece's work on profiting from innovation. It is why a bottleneck map must track complements, not just obstacles: some frictions are cleared by a complement arriving, not by direct effort. ↩