Ecosystem Mismatch¶

Explain why a technically sound innovation stalls on deployment not by a flaw in the artifact but by the absence of one specific complementary asset its operating context tacitly required — leaving it complete-but-functionally-blocked.

Core Idea¶

Ecosystem mismatch is the innovation-diffusion failure mode in which an innovation works in isolation but fails on deployment because the surrounding institutions, partners, infrastructure, suppliers, regulators, customer routines, and complementary technologies that the innovation tacitly requires are not present, not ready, or not aligned at the deployment site. The product or programme is technically sound; the context-of-use is missing one or more complementary elements without which technical soundness cannot convert to value. The structural diagnosis has three components: an innovation that embeds tacit assumptions about its operating context (what partners, what infrastructure, what regulatory framework, what customer behaviours are available); an operating context at the deployment site that differs from those assumptions along at least one necessary dimension; and a complementary asset — supplier capacity, charging infrastructure, certified operators, billing-system compatibility, cold-chain logistics, professional-society endorsement, interoperability standards — whose absence is the binding constraint on value delivery. The intervention family follows from this diagnosis: the unit of analysis is the innovation plus its required ecosystem, not the innovation alone, so the relevant moves are to map the innovation's tacit context-assumptions, audit the deployment context for gaps, and then either build the missing complement, recruit a partner who holds it, or relocate initial deployment to a context where the complement is already present. Electric vehicles requiring charging infrastructure and a grid able to support them, clinical-decision-support tools requiring EHR integration and billing-code recognition, and vaccines requiring vaccinator workforce and community-health-worker route maps are canonical instances. Adner's wide-lens framework and Teece's complementary-assets theory supply the formal apparatus.

Structural Signature¶

Sig role-phrases:

the technically sound innovation — a product or programme that works in isolation and embeds tacit assumptions about its operating context (what partners, infrastructure, regulation, and customer routines are available)
the deployment context — the actual operating environment at the rollout site, which differs from those assumptions along at least one necessary dimension
the required complementary asset — the specific external element (supplier capacity, charging infrastructure, certified operators, billing-code recognition, cold-chain logistics, professional-society endorsement, interoperability standard) on which value delivery depends
the binding-constraint absence — the one missing complement that halts value delivery, the load-bearing gap among possibly several
the unit of analysis shift — the relevant object is innovation plus its required ecosystem, not the innovation alone
the complete-but-functionally-blocked state — every part of the innovation sound, value delivery stopped by the absent external complement, not by any defect in the artifact
the deployment-step surfacing — the gap is invisible in development and demo (the innovation passes every isolated test) and appears only when deployment meets the complement-poor context; the partial-pilot pattern (sites holding a complement succeed, others stall) confirms it
the close/recruit/relocate intervention — build the missing complement, recruit a partner who holds it, or stage initial deployment where it already exists, attacking the binding complement first rather than re-engineering the artifact

What It Is Not¶

Not a flaw in the innovation. The artifact is technically sound and works in isolation; the binding constraint sits outside it, in an absent or unaligned complementary asset the innovation tacitly assumed. The diagnostic signature is complete-but-functionally-blocked — every part works, yet value delivery halts on deployment — so reading the stall as "they built the wrong thing" misattributes a context gap to the merit of the thing.
Not a reason to re-engineer the product. Because the missing element is external, polishing the (already sound) innovation is wasted motion; the corrective is to build the complement, recruit a partner who holds it, or relocate initial deployment where it already exists. Another redesign round leaves the rollout just as blocked, because the artifact was never the problem.
Not cultural friction. A deployment can fail on norm incompatibility even where every infrastructural complement is present — that is a different regime, not ecosystem mismatch. The concept names the absence of a functional complement (charging infrastructure, a billing code, a vaccinator workforce), not a clash between the artifact and the receiving culture's norms.
Not generic scarcity. It is the absence of a specific functional complement whose presence is necessary for value, not merely a finite resource in short supply. "The thing is under-resourced" is not the diagnosis; the diagnosis is that one identifiable assumed complement is missing, and supplying that one converts the blocked innovation to value where general resourcing would not.
Not historical lock-in. Ecosystem mismatch can occur in a fresh deployment with no prior path dependence — the gap is a present absence of a required complement, not the residue of an earlier trajectory that constrains the current one. A brand-new rollout into a complement-poor context exhibits the mismatch without any lock-in at all.

Scope of Application¶

Ecosystem mismatch lives within innovation management and diffusion; its reach is within that domain, across every deployment context where a technically sound artifact stalls because one assumed complementary asset is absent. The genuinely distant cousins (ecological mutualism failure, supply-chain bottlenecks) belong to the broader missing-complement / complete-but-blocked pattern, not to "ecosystem mismatch" by name.

Hardware and physical-product launches — a device depending on a software ecosystem, accessory makers, app developers, or carrier partnerships that are not in place at launch.
Health-tech adoption — clinical-decision-support tools needing EHR integration, billing-code recognition, professional-society endorsement, and clinician training the deploying institutions lack.
Energy and transport transitions — electric vehicles needing charging networks, grid capacity, a repair workforce, and standards harmonisation, where the sound vehicle cannot deliver value without them.
Global health and vaccine deployment — heat-stable vaccines blocked not by the formulation but by an absent vaccinator workforce, community-health-worker route maps, and registration infrastructure.
Public-sector service redesign — a service assuming inter-agency data sharing, statutory authority, partner capacity, and citizen digital literacy the local context has not built.
Education reform — a curriculum innovation assuming teacher training, textbook supply, assessment alignment, and parental support the deploying district lacks.
Two-sided platform launches — the chicken-and-egg failure of one market side to reach critical mass while the other is present.

Clarity¶

Naming ecosystem mismatch reframes a deployment failure from a quality-of-the-innovation problem into a context-fit problem. When a technically sound product or programme stalls on rollout, the default reading is that the team built the wrong thing, inviting another round of redesign. The label makes legible a different diagnosis: they may have built the right thing for a context that does not yet exist at the deployment site, and the binding constraint is a missing complementary asset — charging infrastructure, billing-code recognition, a vaccinator workforce — not a flaw in the innovation itself. That separates two questions practitioners routinely fuse: is the innovation good? and is the surrounding ecosystem ready to let it deliver value? — and points the correction away from re-engineering the artifact and toward building, recruiting, or relocating to the missing complement.

It also sharpens the unit of analysis. The bare innovation invites the question "does it work?"; ecosystem mismatch makes legible that the relevant object is the innovation plus its required ecosystem, so the sharper question becomes "what does this tacitly assume about its operating context, and which of those assumptions fails here?" That distinction tells the innovator something a quality audit cannot: the system may be complete-but-functionally-blocked rather than broken — every part of the innovation sound, value delivery halted by one absent external complement. Localizing the breakdown to a specific missing element (rather than to the innovation's merit) is what makes the intervention space — map the tacit context-assumptions, audit the deployment site for the gap, then close it or stage deployment where the complement already exists — visible and actionable, where "it failed to catch on" would only have prompted more polishing of a thing that already worked.

Manages Complexity¶

Deployment failures arrive as a heterogeneous catalogue of causes — a supplier not ready, a regulator not aligned, a billing code unrecognised, charging infrastructure absent, a vaccinator workforce missing, a customer routine that never formed — each looking like its own distinct problem demanding its own explanation. Ecosystem mismatch compresses that catalogue into a single diagnosis: somewhere in the innovation's required ecosystem, one complementary asset is the binding constraint on value delivery, and its absence is what halts an otherwise sound artifact. That collapses an open-ended search over everything that might have gone wrong into a bounded procedure — map the innovation's tacit context-assumptions, audit the deployment site against them, and find the one assumption that fails — and it fixes the unit of analysis at innovation plus required ecosystem so the question is no longer the unbounded "does it work?" but the locatable "which assumed complement is missing here?" Once that one element is identified, the qualitative situation (complete-but-functionally-blocked, not broken) and the intervention (build the complement, recruit a partner who holds it, or stage deployment where it already exists) follow directly. The innovator reasons over a short list of context-assumptions and their gaps rather than over the full causal sprawl of why a rollout stalled.

Abstract Reasoning¶

Ecosystem mismatch licenses inference moves that all turn on the unit of analysis the compression fixes: the innovation plus its required ecosystem, with a missing complementary asset as the binding constraint on value.

Diagnostic — when a sound innovation stalls, infer a missing external complement, not a flawed artifact. The characteristic move is to take a deployment that fails despite a technically sound product or programme and infer that the binding constraint sits outside the innovation — in an absent or unaligned complementary asset (charging infrastructure, billing-code recognition, a vaccinator workforce, an interoperability standard) that the innovation tacitly assumed. The diagnostic signature that distinguishes ecosystem mismatch from a genuine quality problem is complete-but-functionally-blocked: every part of the innovation works in isolation, yet value delivery halts on deployment — which points not at the artifact but at the context. A second, sharper diagnostic tell is the partial-pilot pattern: deployment partners who happen to hold one or two of the missing complements run small successful pilots while scale-out stalls everywhere the complement is absent — confirming that the variable governing success is an external asset, not the innovation's merit. From "it works in the demo and in two sites but dies on rollout," the move is to map the innovation's tacit context-assumptions and audit the deployment site against them until the one failing assumption is found.

Interventionist — close, recruit, or route around the missing complement; do not re-engineer the artifact. Because the binding constraint is an absent external element, the licensed interventions act on the ecosystem, and re-engineering the (already sound) innovation is predicted to be wasted motion. The move has three branches, selected by the nature of the gap: build the missing complement (stand up the infrastructure, train the workforce), recruit a partner who already holds it (a complementor, a distributor, an endorsing professional society), or relocate initial deployment to a context where the complement is already present and stage outward from there. Each is a prediction: supply the one missing complement and the otherwise-blocked innovation is predicted to convert to value; leave it absent and no amount of product polish will. The interventionist reading also predicts sequencing — when several complements are missing, the binding one must be closed first, because relieving a non-binding gap leaves value delivery still halted by the binding one — so the move is to attack the complement whose absence is currently load-bearing, in parallel with deployment rather than before it.

Boundary-drawing — is this a missing-complement problem at all, and which neighbor is it not? The concept draws lines that keep the diagnosis honest. It applies precisely when the artifact is sound and a specific external element is absent; it does not apply when the innovation itself is the problem (a real quality or fit defect), and the move is to confirm completeness-in-isolation before reaching for an ecosystem explanation, lest "the ecosystem wasn't ready" excuse a genuinely weak product. It also bounds the concept against its neighbors: a deployment can fail on cultural incompatibility (norm friction) even where every infrastructural complement is present — that is not ecosystem mismatch; and a generic resource shortage is not ecosystem mismatch either, because the concept names the absence of a specific functional complement whose presence is necessary for value, not merely a finite resource in short supply. The move is to ask which specific assumed complement is missing here? — and if the answer is "none specific; the thing is just under-resourced or culturally rejected," the regime is a different one.

Order-of-events / predictive — the gap surfaces at deployment, not in isolation, and timing confirms the diagnosis. The concept predicts a fixed temporal signature: the innovation passes every isolated test (it is technically sound) and the mismatch becomes visible only at the deployment step, when the artifact meets a context missing the assumed complement. The move reads that timing as confirmation — a failure that was invisible in development and the demo but appeared the moment real deployment required the external complement is the order-of-events fingerprint of ecosystem mismatch, distinguishing it from a defect that would have shown up in isolation. Read forward, it licenses a forecast: an innovation about to deploy into a context whose required complements have not been audited is predicted to stall on rollout despite clean isolated performance — so the predictive payoff is to run the context-gap audit before deployment, when building or recruiting the complement is still cheap, rather than after, when the stalled rollout has already exposed it.

Knowledge Transfer¶

Within innovation management and diffusion the diagnosis transfers as mechanism across every deployment context, because the unit of analysis it fixes — innovation plus its required ecosystem, with one missing complementary asset as the binding constraint — is the same regardless of the artifact. The diagnostics (confirm completeness-in-isolation; read the complete-but-functionally-blocked and partial-pilot signatures; map tacit context-assumptions and audit the deployment site against them), the three-branch intervention (build the complement, recruit a partner who holds it, or relocate initial deployment to a complement-rich context), and the sequencing rule (close the binding complement first) carry intact from hardware product launches awaiting a software/accessory/carrier ecosystem, to health-tech (clinical-decision-support tools needing EHR integration, billing-code recognition, and professional-society endorsement), to public-sector service redesign (assuming inter-agency data sharing, statutory authority, and citizen digital literacy), to education reform (a curriculum assuming teacher training, textbook supply, and assessment alignment), to energy and transport transitions (EVs needing charging networks, grid capacity, and a repair workforce), to two-sided platform launches (the failure of one side to reach critical mass). These are not analogies between separate problems; they are flavours of one innovation-management substrate with the artifact and its required complements swapped — the candidate's four-domain transfer sketch sits entirely inside it — so a wide-lens context-gap audit proven for vaccines transfers to EVs essentially unchanged. The formal apparatus travels with the diagnosis: Teece's complementary-assets framework, Adner and Kapoor's ecosystem-as-structure / wide-lens framework, the innovation-systems literature, and the platform-economics chicken-and-egg/seeding toolkit all apply across these contexts.

The reach of the named concept stops at the edge of that substrate, and honesty requires marking why its apparent breadth is one substrate replayed rather than cross-domain travel. "Ecosystem mismatch," "co-innovation risk," "complementary-asset gap," and "adoption-context misfit" are innovation-management idiom, mostly traceable to Teece and Adner, and the varied contexts above transfer because they share the management-of-innovation substrate, not because each independently re-instantiates a substrate-independent prime.

What genuinely travels to distinct substrates is the pattern underneath ecosystem mismatch, and that — not the named concept — is what should carry any cross-domain lesson (case B). Strip the innovation-management vocabulary and the residue is a general missing-complement pattern: a function-bearing element depends on the presence of one or more complementary elements without which it cannot deliver its function, and the binding failure is the absence of a complement. That pattern recurs as genuine co-instances far outside innovation — ecological mutualism failure (the pollinator is absent and the plant cannot set seed; the nitrogen-fixing symbiont is absent and the host starves), supply-chain bottlenecks where one missing input idles an entire chain, two-sided markets where one side never materialises, complementary skills whose absence breaks a team, complementary regulations whose absence neutralises a policy, even complementary cognitive primitives whose absence breaks comprehension — and across all of them the structurally interesting sub-property is the same one this entry isolates: the system is complete-but-functionally-blocked, not broken. The cross-domain insight therefore belongs to the general missing-complement pattern (and its neighbours — it is distinct from cultural_friction, which is norm incompatibility even where every infrastructural complement is present, and from generic scarcity, which is a finite resource in short supply rather than a specific functional complement). The honest report is: across innovation management's deployment contexts the diagnosis transfers as mechanism with only vocabulary changed; for genuinely distant systems, carry the general missing-complement / complete-but-blocked pattern, while the complementary-assets-and-ecosystem apparatus and the "ecosystem mismatch" name stay home as the domain accent. (See Structural Core vs. Domain Accent.)

Examples¶

Canonical¶

Ron Adner's The Wide Lens (2012) uses Michelin's PAX run-flat tire system as the defining case. Michelin's PAX was technically excellent: it let a car keep driving at reduced speed after a puncture, integrating a reinforced tire with a supporting insert. The tire worked. But delivering value on the road required a co-innovation ecosystem Michelin did not control — auto manufacturers to fit it as standard, and above all a network of tire-repair shops equipped with the special machinery and trained to service PAX rather than send a stranded driver to a competitor. That repair-and-service network never materialised at scale, so a driver with a PAX puncture often could not get it serviced. Michelin eventually withdrew the system after large investment, defeated not by the artifact but by an absent complement.

Mapped back: PAX is the technically sound innovation, embedding a tacit assumption about its operating context; the world of ordinary tire shops is the deployment context that differs on one necessary dimension. Trained, equipped PAX-servicing shops are the required complementary asset whose absence is the binding-constraint absence, leaving PAX complete-but-functionally-blocked. Adner's insight is precisely the unit-of-analysis shift — evaluate the tire plus its required service ecosystem, not the tire alone.

Applied / In Practice¶

Global-health vaccine deployment shows the diagnosis doing clinical work. The heat-stable formulations and Vaccine Vial Monitors developed to reach remote populations solved the cold-chain constraint at the vial itself, yet coverage still stalled in many districts because a different complement was binding: a sufficient trained vaccinator workforce, community-health-worker route maps to actually reach households, and functioning registration and supply logistics. A thermostable vaccine sitting in a clinic delivers no immunity without the people and routes to administer it. Programmes such as WHO/UNICEF's Reaching Every District strategy responded by auditing which specific complement was missing at each site and building or recruiting it — microplanning routes, training and deploying health workers — rather than reformulating the (already sound) vaccine.

Mapped back: The heat-stable vaccine is the technically sound innovation; a district lacking vaccinators is the deployment context short one required complementary asset — the workforce and route maps — which is the binding-constraint absence. The vaccine is complete-but-functionally-blocked, and the mismatch surfaces at the deployment step (fine in the lab, stalled in the field). Reaching Every District is the close/recruit/relocate intervention: build the missing workforce complement rather than re-engineer the artifact.

Structural Tensions¶

T1: Redirecting diagnosis versus laundering a weak product (the alibi risk). The concept's whole value is to pull a stalled rollout away from "we built the wrong thing" and toward "one external complement is missing" — but that same redirection is exactly what a genuinely weak innovation would want said about it. "The ecosystem wasn't ready" is available as an honest diagnosis and as an excuse, and from the outside the two are hard to tell apart. The safeguard the concept itself demands — confirm completeness-in-isolation before reaching for an ecosystem explanation — is a real burden, because a team invested in its artifact will read partial demo success as proof of soundness. The tension is that the more powerful the reframing is at exonerating the artifact, the more readily it can exonerate one that deserved to fail. Diagnostic: Does the innovation demonstrably deliver its function wherever the named complement is present — or is "the ecosystem" carrying a defect the artifact would show under fair test?

T2: Right unit of analysis versus locus of control (you must own what you cannot command). Fixing the unit at innovation plus required ecosystem is the diagnostic breakthrough, but the ecosystem is by definition the part the innovator does not control — Michelin could build a flawless tire and still not conjure a network of trained repair shops. The concept therefore hands the innovator responsibility for assets outside its authority: to escape the mismatch it must build, recruit, or relocate around a complement it cannot simply order into existence. The tension cuts both ways: narrowing the unit to the artifact keeps the problem controllable but blinds the team to the binding constraint; widening it to the ecosystem finds the real constraint but places the fix in territory the innovator can only influence, not command. Diagnostic: Is the binding complement something this actor can build, buy, or partner into within its horizon — or does escaping the mismatch require moving an ecosystem it does not control?

T3: Build versus recruit versus relocate (the three escapes trade against each other). Once the binding complement is identified, the three interventions are not interchangeable. Building it yields full control but is the slowest and most capital-intensive, and may require standing up an entire industry (chargers, repair workforces). Recruiting a partner who already holds it is fast and cheap but makes value delivery hostage to a complementor's incentives and timeline. Relocating initial deployment to a complement-rich context de-risks the launch but shrinks the beachhead market and can strand the innovation in a niche it never escapes. The sequencing rule — attack the binding complement first — governs which gap to close, but not which branch to take, and choosing wrong wastes the scarce runway a stalled rollout has left. Diagnostic: For the binding complement, does the situation favour the control of building, the speed of recruiting, or the de-risking of relocating — and what does each cost in time, capital, and market reach?

T4: Tacit assumptions versus the pre-deployment audit (the gap that hides until it bites). The concept predicts a fixed order of events — the innovation passes every isolated test and the mismatch surfaces only at deployment — and then urges the innovator to run the context-gap audit before deploying, while the complement is still cheap to build. But the assumptions the audit must surface are, by the concept's own account, tacit: they are the context conditions the innovation embeds without stating, which is precisely why they went unnoticed through development and demo. The tension is that the very property that makes the audit valuable — the assumptions are hidden — is what makes it incomplete, since one cannot reliably enumerate in advance what one has assumed without noticing. Deployment remains the most honest revealer even as the concept counsels not to wait for it. Diagnostic: Has the team actually externalised its tacit context-assumptions into a checkable list, or is it trusting an audit that can only find the gaps it already thought to look for?

T5: Specific functional complement versus generic shortfall (the boundary that keeps the diagnosis honest). Ecosystem mismatch names the absence of one specific function-bearing complement whose presence is necessary for value — not a generic resource shortage and not a clash with the receiving culture's norms. The boundary matters because the corrective differs: supplying the one identified complement converts a blocked innovation to value, whereas general resourcing or norm-negotiation would not, and vice versa. The tension is that in a messy rollout all three are usually present at once — the deployment is under-resourced and culturally resisted and short a specific complement — so isolating the binding one requires resisting the pull to call every external difficulty "ecosystem mismatch." Over-extend the label and it becomes a catch-all for "deployment was hard," losing the locating power that made it useful. Diagnostic: Can you name the single specific complement whose supply would unblock value — or is the answer "it's just under-resourced / the culture rejected it," a different regime?

T6: Autonomy versus reduction (innovation-management idiom or the instance of the missing-complement pattern). "Ecosystem mismatch," with its complementary-assets and wide-lens apparatus (Teece, Adner), is a named diagnosis with real currency inside innovation management, and across that domain's deployment contexts it transfers as mechanism with only the artifact swapped. But strip the vocabulary and the residue is a substrate-general shape — a function-bearing element cannot deliver its function because one complementary element it depends on is absent, leaving the system complete-but-functionally-blocked — which recurs as genuine co-instances in ecological mutualism failure, supply-chain bottlenecks, two-sided markets, and broken team skill-sets, none of which is "ecosystem mismatch" by name. The tension is between a domain concept that earns its own formal apparatus and the recognition that its cross-domain cargo belongs to the broader missing-complement pattern (itself distinct from generic scarcity and from cultural friction). Diagnostic: Resolve toward the general missing-complement / complete-but-blocked pattern when carrying the lesson to mutualisms, supply chains, or teams; toward named ecosystem mismatch when diagnosing a stalled innovation rollout in situ.

Structural–Framed Character¶

Ecosystem mismatch sits on the framed side of the spectrum — best read as framed-leaning: a real diagnostic mechanism, but one constituted by and stated within the practice of innovation management rather than floating free of it. On human_practice_bound it scores high: the concept's very objects — a technically sound innovation, a deployment context, a required complementary asset, the unit-of-analysis shift to innovation-plus-ecosystem — are all defined relative to the human activity of taking an artifact to market. Strip away the innovator, the rollout, and the value-delivery goal and there is no "mismatch," only a system missing an input; the diagnosis dissolves when the deployment practice is removed. Institutional_origin is likewise pronounced: "ecosystem mismatch," "co-innovation risk," "complementary-asset gap," and "adoption-context misfit" are furniture of a specific tradition — Teece's complementary-assets framework and Adner's wide-lens / ecosystem-as-structure apparatus — distinctions drawn inside the management-of-innovation literature, not substrate-neutral form. On vocab_travels it scores low: the operative vocabulary (co-innovation, complementor, wide-lens audit, adoption context, billing-code recognition, professional-society endorsement) is innovation-management idiom that renames its every component off the deployment substrate. Its evaluative weight is the one criterion that pulls the other way and keeps it off the framed pole — the concept is scrupulously non-verdictive: its signature move is to refuse the conviction "they built the wrong thing," insisting the artifact is sound and the constraint external, so unlike a fallacy label it acquits rather than convicts and names a locatable causal gap rather than rendering a normative finding. And import_vs_recognize is mixed: within innovation management the diagnosis transfers as mechanism (hardware, health-tech, EVs, vaccines, platforms are one substrate with the artifact swapped, recognized intact), but beyond it the reach is import-by-analogy onto co-instances in other substrates.

The one portable structural skeleton is complement-dependence with a binding absence: a function-bearing element cannot deliver its function because one complementary element it depends on is absent, leaving the system complete-but-functionally-blocked rather than broken. That skeleton is genuinely substrate-independent and recurs observer-free — ecological mutualism failure, supply-chain bottlenecks, two-sided-market cold starts, broken team skill-sets — which is exactly what tempts a structural reading. But it does not pull "ecosystem mismatch" off the framed pole, because that portable pattern is precisely what the entry instantiates from the umbrella: the cross-domain reach belongs to the general missing-complement / complete-but-blocked pattern (distinct from cultural_friction, which is norm incompatibility even with every functional complement present, and from generic scarcity, a finite resource in short supply rather than a specific assumed complement), while the complementary-assets-and-wide-lens apparatus and the "ecosystem mismatch" name are exactly the parts that stay home. Its character: a non-verdictive but practice-constituted innovation-management diagnosis whose distinctive content is Teece/Adner apparatus, structural only in the missing-complement / complete-but-functionally-blocked skeleton it borrows from its umbrella and dresses in deployment vocabulary.

Structural Core vs. Domain Accent¶

This section settles why ecosystem mismatch belongs in the catalog as a domain-specific abstraction while falling short of prime status — the two verdicts rest on the same analysis of what survives extraction and what does not.

What is skeletal (could lift toward a cross-domain prime). Peel off the innovation-management wrapping and a thin relational structure remains: a function-bearing element cannot deliver its function because one complementary element it depends on is absent — every part of it sound in isolation, yet the whole rendered complete-but-functionally-blocked, with the missing complement as the single binding constraint. The portable pieces are abstract — a functional unit, a set of tacitly-required complements, a specific absent one that is load-bearing, and the diagnostic signature that distinguishes "blocked by a missing external dependency" from "internally defective." That skeleton is genuinely substrate-portable: it recurs observer-free in ecological mutualism failure (pollinator absent, plant cannot set seed), supply-chain bottlenecks (one idle input stalls the chain), two-sided-market cold starts, and broken team skill-sets. That recurrence is exactly why the entry reads as an instance of a general missing-complement / complete-but-blocked pattern — but that is the core it shares, not what makes it ecosystem mismatch.

What is domain-bound. Almost all the worked content is management-of-innovation furniture that does not survive extraction: the technically sound innovation taken to market, the deployment context it rolls out into, the unit-of-analysis shift to innovation-plus-required-ecosystem, and the concrete complements the discipline catalogs — charging infrastructure and grid capacity, EHR integration and billing-code recognition, professional-society endorsement, vaccinator workforce and community-health-worker route maps, interoperability standards. The intervention grammar (build / recruit / relocate, close the binding complement first) and the formal apparatus (Teece's complementary assets, Adner's wide-lens ecosystem-as-structure, the platform chicken-and-egg toolkit) are equally home-bound. The decisive test: remove the value-delivery practice — an innovator taking an artifact to market and needing it to convert soundness into value — and there is no "mismatch," only a system missing an input; the diagnosis dissolves the moment the deployment practice is stripped away. The naming vocabulary (co-innovation risk, complementor, adoption-context misfit) renames every component off that substrate.

Why this does not clear the prime bar. A prime's vocabulary travels and its cross-domain transfer is recognition of the same mechanism, not analogy. Ecosystem mismatch's transfer is bimodal. Within innovation management — hardware launches, health-tech, energy and transport transitions, vaccine deployment, public-service redesign, education reform, platform launches — the diagnosis travels intact: it is one substrate with the artifact and its complements swapped, recognized as the same mechanism, so a wide-lens context-gap audit proven for vaccines ports to EVs essentially unchanged. Beyond it — mutualisms, supply chains, teams — "ecosystem mismatch" reaches only by analogy: those are co-instances of the underlying missing-complement pattern, not independent re-instantiations of a specifically ecosystem-mismatch-shaped structure, and carrying the name there means renaming complementor as pollinator or teammate. And when the bare structural lesson is needed cross-domain — a sound unit blocked by one absent dependency, complete-but-functionally-blocked rather than broken, fixed by supplying the binding complement — it is already carried, in more general form, by the missing-complement / complete-but-blocked pattern the entry instantiates (itself kept distinct from cultural_friction, which is norm incompatibility even where every functional complement is present, and from generic scarcity, a finite resource in short supply rather than one specific assumed complement). The cross-domain reach belongs to that umbrella; "ecosystem mismatch," as named, carries the complementary-assets-and-wide-lens apparatus that should stay home.

Relationships to Other Abstractions¶

Current abstraction Ecosystem Mismatch Domain-specific

Parents (3) — more general patterns this builds on

Ecosystem Mismatch is a kind of Interface Mismatch Prime

Ecosystem Mismatch is the deployment-context species of Interface Mismatch, where an artifact's operating contract is not met by its surrounding complement system.
Ecosystem Mismatch is part of Complementarity Prime

A pair of non-overlapping but jointly necessary roles—the artifact and its missing complementary asset—is internal to Ecosystem Mismatch.
Ecosystem Mismatch is part of Dependency Prime

A directed reliance of the innovation's deployed function on the absent contextual asset is an internal constituent of Ecosystem Mismatch.

Hierarchy paths (3) — routes to 3 parentless roots

Ecosystem Mismatch → Interface Mismatch → Interface → Boundary

Show alternative paths (2)

Not to Be Confused With¶

Poor product-market fit / a genuinely flawed innovation. The case where the stall traces to the artifact itself — it does not do what users need, or does it badly. Ecosystem mismatch is the opposite locus: the innovation is technically sound and works in isolation (complete-but-functionally-blocked), the binding constraint sitting in an absent external complement. The safeguard is to confirm completeness-in-isolation before invoking the ecosystem, lest "the ecosystem wasn't ready" launder a weak product. Tell: does the innovation deliver its function wherever the named complement is present (ecosystem mismatch), or does it underperform even where every complement exists (product-market-fit failure)?
Cultural friction. A deployment failing on norm incompatibility — the receiving culture's values, habits, or identity clash with the artifact — even where every infrastructural complement is present. Ecosystem mismatch names the absence of a functional complement (a billing code, a charging network, a vaccinator workforce), not a values clash. Tell: is the obstacle a missing functional element the artifact needs to work (ecosystem mismatch), or resistance from the receiving culture's norms with all functional pieces in place (cultural friction)?
Generic scarcity / under-resourcing. A deployment simply short of money, staff, or time across the board. Ecosystem mismatch is the absence of one specific function-bearing complement whose supply would unblock value — not a finite resource in general short supply. Supplying that complement converts the blocked innovation; general resourcing would not. Tell: can you name the single specific complement whose presence unblocks value (ecosystem mismatch), or is it "the whole thing is under-resourced" (generic scarcity)?
Path dependence / lock-in. A present situation constrained by the residue of an earlier trajectory — sunk investments, installed base, prior standards that foreclose options now. Ecosystem mismatch can strike a brand-new rollout with no prior history: the gap is a present absence of a required complement, not the inheritance of a past path. Tell: is the constraint a legacy of prior choices that box in the present (lock-in), or a here-and-now missing complement that would block even a fresh, history-free deployment (ecosystem mismatch)?
Chicken-and-egg / two-sided-market cold start. The specific launch failure where one side of a platform cannot reach critical mass because the other side is absent (and vice versa). This is best read as a special case of ecosystem mismatch in which the missing complement is the other market side and the dependence is mutual/circular. Tell: is the missing complement a distinct external asset (general ecosystem mismatch), or specifically the reciprocal user side of a platform, each waiting on the other (chicken-and-egg)?
The missing-complement / complete-but-blocked pattern (the parent) and its cousins. The substrate-neutral skeleton — a function-bearing element cannot deliver its function because one complementary element it depends on is absent, leaving the whole complete-but-functionally-blocked rather than broken — is the general pattern, recurring as ecological mutualism failure (pollinator absent → no seed set), supply-chain bottlenecks, and broken team skill-sets. Ecosystem mismatch is the innovation-management instance. Tell: carrying the lesson to mutualisms, supply chains, or teams, use the general missing-complement pattern; reserve "ecosystem mismatch" for a stalled innovation rollout with its complementary-assets apparatus. (Treated fully in earlier sections.)

Neighborhood in Abstraction Space¶

Ecosystem Mismatch sits in a crowded region of the domain-specific corpus (29^th percentile for distinctiveness): several abstractions share nearly its structure, so a description that fits it tends to fit its neighbors too.

Family — Unclustered & Miscellaneous (309 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12