Lock-In Map¶
Model — instantiates Structural Constraint Identification and Lock-In
Catalogs the self-reinforcing mechanisms — network effects, infrastructure dependencies, and feedback loops — that make a system reproduce its current path, showing why the arrangement holds even when a better alternative exists.
The puzzle at the center of lock-in is that a demonstrably worse arrangement can persist against a demonstrably better one. Lock-In Map explains that by cataloging the self-reinforcing mechanisms that make the current path reproduce itself — the loops through which staying on the path makes the path stronger. Its distinguishing focus is causal and mechanistic: not what would it cost to leave and not who can block the change, but what forces actively pull the system back onto its current track. It names each reinforcing loop — a network effect where more adopters make the incumbent more valuable, an infrastructure dependency where surrounding systems have been built to assume the incumbent, a feedback where success funds the entrenchment of success — and shows how they compound. A single weak reinforcer is a friction; three compounding ones are a trap.
Example¶
A mobile developer platform has clearly better competitors on raw capability, yet developers and users stay. A Lock-In Map lays out why by cataloging the reinforcing loops rather than the exit costs. The dominant loop is a two-sided network effect: users go where the apps are, developers build where the users are, and each new user makes the platform more valuable to developers and vice versa — a loop that strengthens with every join. Layered on it is an infrastructure dependency: a decade of proprietary SDKs, build pipelines, payment plumbing, and CI tooling that the whole third-party ecosystem now assumes, so the platform is embedded in tools no one would rebuild casually. A third loop is data gravity — the more usage accrues, the more the platform's analytics and defaults improve, funding further entrenchment.
Drawn together, the map shows the platform is not held by any single force but by three loops that reinforce each other: the network effect makes the infrastructure worth building, the infrastructure raises the cost of the network defecting, and both feed the data advantage. That compounding is the diagnosis — it explains why a better competitor does not simply win, and it identifies which loop, if broken, would weaken the others most.
How it works¶
The map's method is to trace reinforcing feedback loops rather than list disadvantages. For each candidate mechanism it draws the loop explicitly: what grows, what that growth strengthens, and how the strengthening feeds back to more growth.[n1] Three loop families get their own registers. Network effects are logged with their type (direct, indirect/two-sided, data) and rough strength — how much each additional participant raises the incumbent's value. Infrastructure dependencies are mapped as the surrounding systems that have been built assuming the incumbent, and that would break or need rework if it were swapped. Other feedbacks (learning-by-doing, complementary-asset accumulation) are noted as they appear. The key analytical output is not the list but the interaction: which loops feed which, so the analysis can identify a keystone loop whose disruption would cascade.
Tuning parameters¶
- Loop-inclusion threshold — how strong a reinforcing effect must be to make the map. A low bar captures every faint feedback and clutters the picture; a high bar risks missing a loop that only matters in combination.
- Network-effect typing depth — whether effects are lumped as "network effects" or split into direct, two-sided, and data effects. Finer typing reveals which side of the market to attack but costs analysis.
- Infrastructure horizon — how far into the surrounding ecosystem to trace dependencies (immediate integrations only, or the whole tooling stack). Deeper tracing finds hidden entrenchment but expands the map.
- Interaction modeling — whether loops are listed independently or their reinforcement of each other is drawn. Modeling interactions is what surfaces the keystone loop, but it is the most effortful and speculative step.
When it helps, and when it misleads¶
Its strength is explanatory: it answers why the worse thing wins and keeps winning, which no cost tally or org chart can, and it points to leverage — a keystone loop whose disruption unravels the others is where an escape intervention should aim. It is the archetype's core account of why a path reproduces itself.
Its failure mode is lock-in inflation: naming reinforcing loops everywhere until every arrangement looks permanently trapped, which slides from diagnosis into fatalism. It also tends to overstate durability by mapping loops statically, missing that network effects can tip the other way once a rival crosses its own threshold, or that infrastructure can be abstracted behind a compatibility layer. The guarding discipline is to grade each loop's real strength rather than merely noting it exists, and to pair the map with an explicit check for what would reverse each loop — so the map shows where the trap is genuinely tight versus merely assumed.
How it implements the components¶
lock_in_mechanism_map— its central output: the catalog of self-reinforcing loops and how they interact to reproduce the current path.network_effect_register— logs each network effect by type and strength, since these are usually the dominant reinforcers in platform and standard lock-in.infrastructure_dependency_map— records the surrounding systems built to assume the incumbent, whose entrenchment raises the practical cost of any switch.
It does not quantify the dollar-and-effort cost of leaving (switching_cost_profile and sunk_commitment_ledger, from Switching-Cost Audit, its nearest twin — that audit prices exit; this map explains the reinforcing forces regardless of price), nor does it map the procedural institutional_rule_map of who can block change (see Institutional Veto-Point Review). Unlike a general Dependency Graph, which renders any depends-on relation, this map admits only relations that form a self-reinforcing loop.
Related¶
- Instantiates: Structural Constraint Identification and Lock-In — supplies the lock-in-mechanism layer: the reinforcing loops that answer why the path reproduces itself.
- Consumes: Switching-Cost Audit — the audited exit cost is one quantity the map cites when grading how tight the infrastructure loop is.
- Sibling mechanisms: Comparative Case Constraint Check · Counterfactual Breakpoint Analysis · Feasibility Envelope Diagram · Institutional Veto-Point Review · Switching-Cost Audit · Threshold and Hysteresis Assessment · Dependency Graph
Editorial Notes¶
Form Classification¶
Form family: Analysis, Modeling & Optimization
Rationale: Lock-In Map operates as a computation, comparison, model, or analytic representation used to infer, estimate, or choose because it catalogs the self-reinforcing mechanisms — network effects, infrastructure dependencies, and feedback loops — that make a system reproduce its current path, showing why the arrangement holds even when a better alternative exists.
Independent corroboration: The frozen evidence defines Lock-In Map as 'Catalogs the self-reinforcing mechanisms — network effects, infrastructure dependencies, and feedback loops — that make a system reproduce its current path, showing why the arrangement holds even when a better alternative exists', so its operative form is Analysis, Modeling & Optimization.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Economics & Finance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Lock-in, increasing returns, switching costs, and path dependence were canonically developed in economics of technology and institutions.
Related originating lineages:
- Innovation & Entrepreneurship — Technology diffusion and platform strategy materially shape practical mapping of network and learning effects.
- Political Science — Institutional path-dependence research contributes power, rule, and infrastructure mechanisms that preserve an arrangement.
- Systems Thinking & Cybernetics — Reinforcing feedback loops materially explain the self-amplifying structure of lock-in.
Review resolution: Both independent reviews assign primary provenance to economics_finance. The queued secondary differences (alternate_origin_disagreement, encyclopedia_synthesis_disagreement) are reconciled by retaining political_science, systems_cybernetics, innovation_entrepreneurship only as formative or independently established lineage(s), not merely as application domains. origin_mode=cross_disciplinary_synthesis records the provenance relationship, while domain_reach=multi_domain separately records applicability breadth. confidence=high preserves the more cautious assessment, and encyclopedia_synthesis=true records whether either reviewer identified a corpus-specific synthesis.
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] Increasing returns (self-reinforcement): mechanisms by which adopting an option raises the payoff to adopting it further — network effects, learning effects, coordination effects, and adaptive expectations. They are the engine of technological and institutional lock-in, and the reason an early lead can compound into durable dominance even without superiority; naming them without grading their strength is how the same lens tips into fatalism. ↩