Technology Push¶

The innovation posture in which a technical capability is developed first and a search for problems it can address follows — the inverse of demand pull, fixing the technology and ranging over problem spaces, with the multi-year match step as the load-bearing risk.

Core Idea¶

Technology push is the strategic posture in innovation management in which a new technical capability is developed first and a search for problems, applications, or markets it can address is conducted afterward — the inverse of demand pull, where a market need or specified problem precedes and directs the capability search. The structural commitment is supply-side search direction: the developed technology constitutes the affordance, and the search problem becomes "which problems is this capability adequate to?" rather than "which technology can solve this known problem?" The contrast is sharp and analytically important: in demand pull, the problem is fixed and the search ranges over technologies; in technology push, the technology is fixed and the search ranges over problem spaces, with the match step — identifying a problem the capability is adequate to address — the load-bearing and often multi-year activity.

Canonical cases are post-war US basic-research programmes (the transistor, GPS, ARPANET) developed in the absence of a specified civilian application; corporate central labs (Bell Labs, Xerox PARC) funded to develop general capabilities without product mandates; and platform-substrate technologies (CRISPR, deep-learning toolkits, the laser) that arrived with vague or no application targets and were subsequently matched to specific use cases over years or decades. Maiman's 1960 laser demonstration — coherent monochromatic light without a clear application, subsequently matched to barcode readers, fiber-optic communication, surgery, manufacturing, and weapons targeting — is the paradigmatic example of a supply-led capability search with a long, multi-decade match phase. The characteristic failure mode is the solution in search of a problem: a capability for which no sufficiently valuable application is found before the investment runway ends.

Structural Signature¶

Sig role-phrases:

the developed capability — the technology that exists prior to its application target, constituting the affordance to be matched
the application search — the directed exploration ranging over problem spaces with the technology held fixed
the supply-led search direction — the defining commitment: technology fixed, problem varying — the inverse of demand pull's fixed-problem, varying-technology
the match step — the load-bearing, often multi-year activity of finding a problem the capability is adequate to, where the risk concentrates
the long supply-led feedback loop — the stretched interval between capability development and demonstrated value, because the application is found, not specified
the which-term-is-fixed classifier — the single diagnostic bit that places a programme as push or pull and locates its risk
the solution-in-search-of-a-problem failure — the push failure mode: a capability stranded when no valuable application is found before the runway ends (mirrored by the pull side's problem-locked organisation)
the temporal-separability scope — the distinction is meaningful only in organised innovation where capability precedes application; in co-determined everyday search it blurs
the posture-not-mechanism status — a labelled direction in a search loop carried at higher generality by explore-vs-exploit; its policy cargo (valley of death, R&D budgeting) is innovation-domain furniture that does not travel

What It Is Not¶

Not a synonym for "being innovative" or "starting from what you have." The concept names a precise feature — the direction of search, with the technology fixed and the problem space varying — not innovativeness in general. Used loosely for any capability-first instinct, it thins into metaphor; its analytic content is the search-direction asymmetry, held against demand pull's fixed-problem, varying-technology.
Not an inferior alternative to demand pull, or a mistake. Technology push is a valid posture, not a failure; basic-research and substrate technologies (the transistor, the laser, CRISPR) arrive this way by necessity. Demand pull has its own mirror failure — the problem-locked organisation that funds only pre-specified demand and never builds enabling capability — so the pair is a portfolio choice, not a good-versus-bad ranking.
Not failure just because no application has appeared yet. A long application-less interval is the expected shape of a supply-led search — the match step is the longest feedback loop — not evidence the effort has failed. The diagnostic is whether someone owns the match step and on what evidence the loop is closing; a slow-but-live match is structurally different from a genuine solution-in-search-of-a-problem dead end, and applying a demand-pull timeline misreads the former as the latter.
Not applicable wherever there is invention. The push/pull distinction is meaningful only in organised innovation where a distinguishable capability is developed prior to its application search. In everyday co-determined search, where need and capability evolve together, the distinction blurs; applying it there either just names literal R&D in another sector or thins into metaphor.
Not the explore-versus-exploit trade-off itself. Technology push is a specific species of explore — search initiated from the capability side rather than the problem side — carried at higher generality by ambidexterity_exploit_vs_explore. It is one labelled direction in a search loop, not the general exploration trade-off, and the cross-domain lesson belongs to that prime.
Not an affordance, nor the analogy/transfer by which a capability reaches a new domain. An affordance is what a capability offers; technology push is the organised, resource-bearing search for affordances. And it describes developing the capability first — the strategic posture — not the analogy or transfer mechanics by which the capability is eventually matched to a use. The posture is distinct from both the thing sought and the application machinery.

Scope of Application¶

Technology push lives across the R&D-strategy and innovation-management subfields of innovation studies and entrepreneurship — anywhere a distinguishable capability is under development prior to its application search, so that the supply-led push/pull diagnostic genuinely applies. Its reach stops at temporal separability: in everyday co-determined search, where need and capability evolve together, the distinction blurs, and the cleaner cross-substrate notion of capability-led search belongs to the exploration trade-off, not here.

Corporate central R&D labs — the home turf. General-capability charters without product mandates (Bell Labs, Xerox PARC) develop technologies first and match them to applications afterward, with the multi-year match step as the load-bearing risk.
Military and government R&D. Defence labs develop capabilities (radar, stealth, hypersonics) ahead of any specified operational requirement, then search for the missions they serve.
Platform and substrate technologies. General-purpose capabilities (the laser, CRISPR, deep-learning toolkits, LLMs) arrive with vague or no application targets and are matched to specific use cases over years or decades.
Materials science. New materials (graphene, perovskite cells, shape-memory alloys) are developed as capabilities in search of the problems they are adequate to.
Pharmaceutical screening. Compound libraries are searched for indications, and drug repurposing runs the same supply-led match in reverse time — an existing molecule seeking a new problem.
Academic basic research. Long-horizon discovery proceeds with no specified application target, its downstream applications negotiated by others on a stretched feedback loop.

Clarity¶

Holding technology push against its sibling demand pull makes one otherwise-invisible feature of an innovation programme explicit: the direction of search. The same R&D activity can be narrated either way, and the muddle the pair dissolves is the assumption that capability development and application discovery are one undifferentiated effort. The sharp question becomes which term is fixed while the other varies — in demand pull the problem is fixed and the search ranges over technologies; in technology push the technology is fixed and the search ranges over problem spaces. Naming that asymmetry tells an analyst where the load-bearing work sits: in a push programme it is the match step, the often multi-year activity of finding a problem the capability is adequate to, which a problem-first framing would never foreground as the central risk.

The distinction also makes two opposite failure modes legible and nameable. On the push side, the solution in search of a problem — a capability for which no sufficiently valuable application is found before the investment runway ends — is now a recognized category rather than a post-hoc disappointment, and the practitioner can ask up front who owns the match step and on what evidence the loop will close. On the pull side, the problem-locked organisation that funds only capabilities with pre-specified demand becomes equally visible, exposing why it never builds the substrate technologies that later demand-pull innovation depends on. The pair thus reframes "what kind of programme is this?" into a question with a portfolio consequence: which search direction dominates here, and is the long, supply-led feedback loop being managed as such or mistaken for a stalled demand-pull effort.

Manages Complexity¶

Innovation programmes resist comparison: each carries its own technical substance, organisational form, funding horizon, and history, so judging where a programme's real risk sits, or comparing a lab's many bets, looks like a case-by-case narration of incommensurable efforts. Technology push, held against demand pull, compresses that judgement to a single diagnostic — which term, technology or problem, is fixed while the search ranges over the other. That one bit, read off a programme, determines the rest. Fix the problem and search over technologies and the programme is demand pull; fix the technology and search over problem spaces and it is push, with the multi-year match step as its load-bearing activity and longest feedback loop. The analyst stops tracking the programme's full particulars and tracks just the search direction, then reads off where the risk concentrates and which characteristic failure to monitor: a push programme is watched for the solution in search of a problem — capability stranded when no valuable application is found before the runway ends — and a pull programme for the problem-locked failure of funding only pre-specified demand and so never building substrate technologies. The same one-bit classifier scales to a portfolio: a lab's heterogeneous bets collapse to a push/pull mix, and the failure-mode map attaches per branch, so the question "is this set of programmes healthy?" reduces to whether both search directions are represented and whether each long, supply-led loop is being managed as such rather than mistaken for a stalled demand-pull effort. So an open-ended "what kind of innovation effort is this and how will it fail?" compresses to one binary read of search direction, from which the location of risk and the named failure mode follow.

Abstract Reasoning¶

Technology push licenses a set of reasoning moves built on one structural fact — that the direction of search is supply-led, with the technology fixed and the problem space varying — held always against its sibling demand pull, where the fixed and varying terms are reversed.

Diagnostic — classify a programme by which term is fixed, and read the location of risk off that one bit. The characteristic inference asks not what a programme is about but which term it holds fixed while searching over the other. If the problem is fixed and the search ranges over technologies, the programme is demand pull; if the technology is fixed and the search ranges over problem spaces, it is technology push. From that single classification the rest follows without re-narrating the programme's particulars: a push programme's load-bearing activity and longest feedback loop is the match step — the often multi-year work of finding a problem the capability is adequate to — so the analyst infers that the risk concentrates there, where a problem-first framing would never have foregrounded it. The move is from "what kind of innovation effort is this?" to a binary read of search direction, and from that read directly to where the effort is most likely to fail.

Diagnostic of failure mode — attach the characteristic failure to the search direction, and distinguish a stalled match from a genuine dead end. Because each search direction has its own failure mode, the classification predicts which failure to monitor. A push programme is watched for the solution in search of a problem — a capability for which no sufficiently valuable application is found before the investment runway ends — and the move is to read a long application-less interval not automatically as failure but as the expected long feedback loop of a supply-led search, asking whether the match step is progressing or truly stranded. A pull programme is watched for the opposite, the problem-locked organisation that funds only capabilities with pre-specified demand and so never builds the substrate technologies later demand-pull innovation depends on. The crucial discriminating move on the push side is to not mistake a slow-but-live match for a dead end: the diagnostic is whether someone owns the match step and on what evidence the capability-application loop is closing, since a push effort's silence is structurally different from a pull effort's stall.

Interventionist — manage the long supply-led loop as such, and assign ownership of the match step up front. Because the load-bearing risk in a push programme is the match step rather than the capability development, the corrective levers act there. Name who owns closing the capability-application loop and on what evidence, predicting that an unowned match step is where a valuable capability becomes stranded; budget for a long feedback horizon, predicting that applying a demand-pull timeline to a push programme misreads a normal long loop as failure and kills it prematurely; and, at the portfolio level, ensure both search directions are represented, predicting that an all-pull portfolio will lack the substrate technologies that future pull innovation requires. Each lever follows from the search-direction classification, and a push programme managed on pull assumptions is diagnosed in advance as mismatched to its own risk structure.

Boundary-drawing — apply the push/pull distinction only where capability and application are temporally separable, and separate the posture from the mechanisms it deploys. Two lines the concept draws. First, the diagnostic is meaningful only in organised innovation where a distinguishable capability is under development prior to its application search; in everyday co-determined search, where need and capability evolve together, the push/pull distinction blurs, so the move is to withhold the classification where there is no temporally separable capability and to apply it where one exists. Second, technology push is a strategic posture — a labelled direction in a search loop — distinct from the mechanisms it employs: it is a species of explore (search initiated from the capability side rather than the problem side), not the general explore-versus-exploit trade-off; it is the organised, resource-bearing search for affordances, not an affordance itself; and it describes developing the capability first, not the analogy or transfer by which a capability later reaches a new domain. The move is to scope the analysis to the search-direction asymmetry and not conflate the posture with the exploration trade-off, the affordances it seeks, or the application mechanics it eventually uses.

Knowledge Transfer¶

Within innovation management, R&D strategy, and entrepreneurship the push/pull diagnostic transfers as mechanism, intact. The single-bit classification (which term is fixed while the search ranges over the other), the location-of-risk read (the multi-year match step as a push programme's load-bearing activity and longest loop), the failure-mode attachment (solution-in-search-of-a-problem on the push side, problem-locked organisation on the pull side), and the portfolio rule (represent both search directions) carry without translation across every setting that is literal organised innovation: military and government R&D (capabilities like radar, stealth, or hypersonics developed ahead of specified operational requirements), materials science (graphene, perovskite cells, shape-memory alloys seeking applications), pharmaceutical screening (compound libraries searching for indications; drug repurposing as push in reverse time), platform-substrate technologies (LLMs, blockchain, CRISPR matched to use cases over years), and academic basic research (long-horizon discovery whose applications are negotiated downstream by others). The vocabulary (capability-led search, the match step, the long supply-led feedback loop, supply-led versus demand-led) travels with the diagnosis, and the management levers (assign ownership of the match step, budget a long feedback horizon, balance the portfolio) follow from the same classification — because all of these are the same substrate: organised innovation in which a distinguishable capability is under development prior to its application search. So within the domain the transfer is genuine.

Beyond organised innovation the honest account is the third category shading into analogy. The structural residue, stripped of innovation-management vocabulary, is a search-direction asymmetry — an actor searching over problem space from a fixed capability rather than over technologies from a fixed need — which is a labelled direction in a search loop rather than a free-standing mechanism, and which is already carried at higher generality by ambidexterity_exploit_vs_explore: technology push is a specific species of explore, search initiated from the capability side rather than the problem side, paired with demand pull as its inverse. Where the genuine cross-domain lesson is wanted it should be carried by that exploration prime (and, for the cognitive cousin, by backward inference — start from a solution, find a problem — of which technology push is the organised, resource-bearing version), not by "technology push" as named, whose distinctive cargo (basic-research funding, the valley of death, R&D budgeting, absorptive capacity, the innovation-policy connotations of the phrase) is innovation-domain furniture. And the boundary is sharp: the push/pull distinction is meaningful only where capability and application are temporally separable; in everyday co-determined search, where need and capability evolve together, the distinction blurs, so applying "technology push" outside organised innovation either (a) just names literal R&D in another sector — inheriting the substrate, not transferring beyond it — or (b) thins into a metaphor for "starting from what you have." The cleanest substrate-independent description is "capability-led search," which is the explore prime's content; "technology push" is its innovation-strategy instance, with policy cargo that does not travel — exactly the split drawn in Structural Core vs. Domain Accent.

Examples¶

Canonical¶

The laser is the paradigmatic case. Theodore Maiman built the first working laser at Hughes Research Laboratories in 1960, producing coherent, monochromatic light — a genuinely new physical capability with no particular application in view. It was famously characterized in its early years as "a solution looking for a problem." Only over the following decades was that capability matched, one application at a time, to barcode scanners at supermarket checkouts, fiber-optic telecommunications, corrective and cataract eye surgery, industrial cutting and welding, optical-disc players, and precision weapons targeting. The technology came first; the problems it was adequate to were discovered afterward, across a multi-decade search.

Mapped back: Coherent light is the developed capability that existed prior to any target, and the decades of finding uses is the application search running the supply-led search direction — technology fixed, problems varying. Each use (barcodes, fiber, surgery) is a closure of the match step, and the long gap from 1960 demonstration to widespread value is the long supply-led feedback loop.

Applied / In Practice¶

The Global Positioning System shows the posture at national scale. The U.S. Department of Defense designed and launched GPS in the 1970s and 1980s as a military positioning-and-timing capability, built well ahead of any specified civilian demand. After the deliberate degradation called Selective Availability was switched off in 2000, the full-precision capability was progressively matched to civilian problems it was never originally aimed at: turn-by-turn car navigation, ride-hailing, precision agriculture, aircraft approaches, and the high-accuracy timestamping that synchronizes financial and telecommunications networks. The capability was supplied first; the applications accreted for years afterward.

Mapped back: The military positioning system is the developed capability created before civilian need; the years of civilian uptake are the application search with the supply-led search direction. Navigation, agriculture, and financial timing each mark closure of the match step, and the long span from 1970s deployment to pervasive civilian value is the characteristic long supply-led feedback loop.

Structural Tensions¶

T1: Push versus pull (each posture's mirror failure — substrate-building against de-risking). The push/pull pair is a portfolio choice, not a good-versus-bad ranking, because each search direction buys one virtue by risking one failure. Demand pull is de-risked — the problem is fixed, so demand is known — but it is problem-locked: it funds only capabilities with pre-specified demand and therefore never builds the substrate technologies (the transistor, the laser, CRISPR) that later pull innovation depends on, because no one specifies demand for a capability that does not yet exist. Technology push builds exactly those substrate capabilities, but risks the solution in search of a problem — capability stranded when no valuable application is found before the runway ends. The tension is that the safety of pull is the same feature that starves the future of enabling capability, and the generativity of push is the same feature that courts the stranded-capability failure. Neither posture dominates; a portfolio needs both. Diagnostic: Is this programme's search direction chosen for de-risking against known demand (pull, risking problem-lock) or for building enabling capability ahead of demand (push, risking stranding) — and does the surrounding portfolio hold the other direction?

T2: Long loop as normal versus long loop as failure (not-yet against never, on identical surfaces). A long application-less interval is the expected shape of a supply-led search — the match step is structurally the longest feedback loop, and the laser sat idle for years before barcodes and fiber. So silence is not evidence of failure. But a genuine solution-in-search-of-a-problem dead end produces exactly the same surface: no application, no value, runway draining. The tension is that "a live match still closing" and "a capability that will never find a valuable problem" are indistinguishable from the outside, both showing the same long quiet, so the analyst cannot read failure off the interval itself. The only discriminator is internal — whether someone owns the match step and on what evidence the loop is closing — and that evidence is soft and contestable exactly when the runway pressure is highest. Diagnostic: Is the application-less interval here a normal long supply-led loop with a match step demonstrably progressing, or a genuine dead end wearing the same silence — and what evidence distinguishes "not yet" from "never"?

T3: Capability's seductiveness versus the unowned match step (the impressive tech masks where the risk lives). In a push programme the load-bearing risk is not developing the capability but the match step — the multi-year work of finding a problem the capability is adequate to. Yet the capability itself is the glamorous, fundable, demonstrable part, and its very impressiveness draws attention and investment toward the technology and away from the unglamorous application search where the effort actually fails. The tension is that the better and more striking the capability, the more it can coast on its own promise, and the easier it is to leave the match step unowned — no one is forced to confront the application question while the demos still awe. A programme can pour resources into an ever-more-capable technology precisely as the real risk (an unowned, non-closing match loop) silently matures. Diagnostic: Is investment and ownership here concentrated on advancing the capability (the visible, seductive part) or on closing the capability-application match (the unglamorous part where push programmes actually strand)?

T4: Patience versus runway (manage-as-push against cut-the-dead-end). Correctly managing a push programme means budgeting a long feedback horizon and refusing to apply a demand-pull timeline, because a pull timeline misreads the normal long loop as failure and kills a live match prematurely. But unlimited patience is exactly how a genuine solution-in-search-of-a-problem drains its runway to zero while everyone waits for a match that will never come. The tension is that the two errors are opposite and both fatal: pull-style impatience kills good push programmes early, while push-style patience funds dead ones indefinitely — and the concept supplies the direction to manage (long loop, match ownership) without a bright line for when patience becomes denial. The same discipline that rescues a slow-but-live match is the one that lets a dead end persist. Diagnostic: Is the long horizon being extended here because the match step shows evidence of closing, or because a pull timeline is being (rightly) refused in a way that has quietly become indefinite tolerance of a dead end?

T5: Temporal separability versus co-determined search (a classifier that needs a separation many programmes lack). The push/pull diagnostic is a clean single bit — which term is fixed while the search ranges over the other — but it is meaningful only where capability and application are temporally separable, a distinguishable capability developed prior to its application search. In much real innovation, need and capability co-evolve: the problem sharpens the technology which reshapes the problem, with no clean "technology first" or "problem first" to read. The tension is that the concept's crisp, portfolio-organizing classification depends on a temporal separation that a large fraction of actual innovation does not exhibit, so forcing the push/pull label onto co-determined search either misreads it or thins into metaphor. The diagnostic is sharp exactly where it applies and blurs exactly where innovation is most entangled. Diagnostic: Is there a distinguishable capability here developed before its application search (push/pull applies), or do need and capability co-evolve (where the classification blurs and should be withheld)?

T6: Autonomy versus reduction (a strategic posture or the instance of its explore parent). Technology push is a specific, named innovation-strategy posture with real home-bound cargo — basic-research funding, the valley of death, R&D budgeting, absorptive capacity, and the policy connotations of the phrase — and it transfers as mechanism across organised innovation (corporate labs, defence R&D, platform technologies, pharma screening). But its structural residue, stripped of that furniture, is a search-direction asymmetry — capability-led search, a labelled direction in a search loop — carried at higher generality by ambidexterity_exploit_vs_explore (push is a species of explore, initiated from the capability side) and, for the cognitive cousin, backward inference (start from a solution, find a problem). The cleanest substrate-independent description is simply "capability-led search," which is the explore prime's content. The tension is between a posture concrete enough to carry innovation-policy analysis and the recognition that its portable lesson belongs to the exploration trade-off. Diagnostic: Resolve toward ambidexterity_exploit_vs_explore (capability-led search) when carrying the direction-of-search lesson beyond organised innovation; toward technology push itself when basic-research funding, the match step, and the valley-of-death runway are the concrete objects.

Structural–Framed Character¶

Technology push sits at framed-leaning on the structural–framed spectrum — a strategic posture whose portable core is a genuine search-direction asymmetry but whose identity is innovation-management furniture. One criterion offers structural pull: evaluative_weight is low — the entry insists push is "a valid posture, not a failure or a mistake," the mirror of demand pull in a portfolio, so the label classifies a direction of search rather than praising or condemning it. The other four criteria pull toward framed. Human_practice_bound is high: the construct is constituted by organised innovation — R&D labs, funding runways, portfolios, the temporal separability of capability from application — and the entry is explicit that it dissolves in everyday co-determined search where need and capability co-evolve; there is no technology push without an organisation that develops a capability before searching for its use. Institutional_origin is pronounced: it is an R&D-strategy construct laden with innovation-policy cargo (the valley of death, R&D budgeting, absorptive capacity, basic-research funding). Vocab_travels is low: the match step, supply-led search direction, and the developed-capability/application-search framing are innovation-domain terms. And on import_vs_recognize the entry's own signature is decisive — technology push is flagged as a posture, not a mechanism, "a labelled direction in a search loop," so off-substrate it either just names literal R&D in another sector or thins into metaphor.

The portable structural skeleton is a single one: capability-led search — a search-direction asymmetry in which the actor ranges over problem space from a fixed capability rather than over technologies from a fixed need. That skeleton genuinely generalizes, which is exactly why it does not lift "technology push" off the framed-leaning position: the cross-domain reach belongs to the umbrella prime it instantiates — ambidexterity_exploit_vs_explore, of which push is a specific species of explore (with backward inference as the cognitive cousin) — and not to the named posture, while its distinctive content (the match step, the valley-of-death runway, the R&D-budgeting and basic-research-funding apparatus) is precisely the innovation-strategy accent that stays home. Its character: a low-valence but thoroughly practice-bound strategic posture, structural in the capability-led-search skeleton it borrows from its explore parent but framed by the organised-innovation substrate and policy vocabulary that make it specifically technology push.

Structural Core vs. Domain Accent¶

This section decides why technology push is a domain-specific abstraction and not a prime, and it carries the case for its domain-specificity — so it is worth being exact about which part could lift and which part stays home.

What is skeletal (could lift toward a cross-domain prime). Strip the R&D lab and a thin relational structure survives: a directed search runs from a fixed capability outward over the space of problems it might address, rather than from a fixed need inward over the capabilities that might meet it — capability-led search, the inverse of need-led search. The portable pieces are abstract — a held-fixed resource, a varying search space, and a single classifying bit for which term is fixed while the other ranges. That skeleton is genuinely substrate-portable — it is a species of explore, search initiated from the supply side rather than the demand side — which is exactly why it is already carried at higher generality by the parent prime ambidexterity_exploit_vs_explore (with backward inference — start from a solution, find a problem — as the cognitive cousin). But it is the core it shares, not what makes technology push distinctive; the cleanest substrate-independent name for it is simply "capability-led search," which is the explore prime's content.

What is domain-bound. Almost everything that makes the posture technology push in particular is innovation-management furniture that does not survive extraction. The developed capability is a technology; the match step is a multi-year R&D activity with its own runway; and the surrounding apparatus — basic-research funding, the valley of death, R&D budgeting, absorptive capacity, the innovation-policy connotations of the phrase itself, the solution-in-search-of-a-problem failure and its problem-locked mirror — is all R&D-strategy vocabulary. The decisive test is temporal separability: the push/pull distinction is meaningful only where a distinguishable capability is developed prior to its application search. Remove that separation — in everyday co-determined search, where need and capability co-evolve — and there is no "technology first" or "problem first" to read, and the classifier dissolves. Applying "technology push" off its substrate therefore either just names literal R&D in another sector (inheriting the substrate rather than transferring beyond it) or thins into a metaphor for "starting from what you have."

Why this does not clear the prime bar. A prime is a relational structure whose vocabulary travels and whose cross-domain transfer is recognition of the same mechanism, not analogy. Technology push's transfer is bimodal. Within organised innovation it travels as mechanism — the single-bit classifier, the location-of-risk read (the match step as load-bearing), the failure-mode attachment, and the portfolio rule carry intact across corporate labs, defence R&D, materials science, pharmaceutical screening, platform-substrate technologies, and academic basic research, because all share the substrate of a capability developed before its application search. Beyond it, what actually generalizes is not "technology push" but the search-direction asymmetry it instantiates, already carried at higher generality by ambidexterity_exploit_vs_explore. The entry's own signature makes the placement unambiguous: technology push is flagged as a posture, not a mechanism — a labelled direction in a search loop — so its cross-domain lesson is the explore prime's, and its distinctive cargo (the match step, the valley-of-death runway, the R&D-budgeting apparatus) is innovation-domain furniture that stays home. When the bare structural lesson is needed cross-substrate, it is already carried, in more general form, by the parent; the cross-domain reach belongs to ambidexterity_exploit_vs_explore, and "technology push," as named, is its organised-innovation instance.

Relationships to Other Abstractions¶

Current abstraction Technology Push Domain-specific

Parents (1) — more general patterns this builds on

Technology Push is a decomposition of Ambidexterity (Exploit vs. Explore) Prime

Removing R&D-policy vocabulary leaves capability-led exploration: hold a capability fixed and search over possible problem spaces.

Hierarchy path (1) — routes to 1 parentless root

Technology Push → Ambidexterity (Exploit vs. Explore) → Adaptive Capacity

Not to Be Confused With¶

Demand pull. The inverse posture the whole distinction is drawn against: a market need or specified problem precedes and directs the capability search, so the problem is fixed and the search ranges over technologies. Technology push fixes the technology and ranges over problem spaces. They are a portfolio pair, not a good-versus-bad ranking, each with its own mirror failure (solution-in-search-of-a-problem versus the problem-locked organisation). Tell: which term is fixed while the search ranges over the other — the problem (demand pull) or the capability (technology push)?
Affordance. What a capability offers — the use it makes possible. Technology push is the organised, resource-bearing search for affordances, not an affordance itself; it names the strategic posture of developing the capability first, not the thing sought. Tell: is the referent what the technology can do (affordance), or the directed programme of hunting for problems it can address (technology push)?
Effectuation / backward inference. The cognitive cousin — reasoning that starts from available means (or a solution) and works toward ends (or a problem) it can serve, rather than from a fixed goal backward to means. Technology push is the organised, resource-bearing institutional version of this means-first move within R&D; effectuation is the general entrepreneurial-cognition principle. Tell: is it a funded R&D programme with a capability and a match step (technology push), or the general means-first reasoning heuristic (effectuation / backward inference)?
A stalled match versus a solution in search of a problem. A long application-less interval is the expected shape of a supply-led search (the match step is the longest loop), not proof of failure — whereas a genuine solution in search of a problem is a capability that will never find a valuable application before the runway ends. They look identical from outside (the same long quiet); the discriminator is internal ownership and evidence of the loop closing. Tell: does someone own the match step with evidence it is progressing (a live long loop), or is the capability stranded with no path to a valuable problem (the dead-end failure mode)?
The parent it instances (ambidexterity_exploit_vs_explore). The substrate-neutral search-direction asymmetry — capability-led search is a species of explore, initiated from the supply side rather than the demand side — that carries the cross-domain lesson. Technology push is its organised-innovation instance. Tell: is there a distinguishable capability developed before its application search, with match-step, valley-of-death, and R&D-budgeting cargo (technology push), or just capability-led search in general? If the latter, the content is the explore parent, not the innovation posture. (Treated more fully in a later section.)

Neighborhood in Abstraction Space¶

Technology Push sits in a moderately populated region (55^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Lean Validation & Startup Signal Theater (8 abstractions)

Nearest neighbors

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