RESHUFFLE An interactive companion to the book
Cascade ▸ from industry-bottleneck-shift

What happens when the industry bottleneck migrates?

Jacobides' core: bottleneck migration drives orchestrator emergence and margin pool restructuring.

visited
30
edges
36
hops
3
chains
4 / 4
failure modes
5
industry-bottleneck-shift dimension-shift

Industry Bottleneck Location Shift (Jacobides)

Industry I3+I5
Where the bottleneck sits within an industry value-chain determines who captures value. As AI dissolves task-level bottlenecks, the binding bottleneck migrates - from production to design, from execution to coordination, from human-judgment to data-aggregation. Jacobides' core industry-architecture insight: industry structure follows bottleneck location. Specializes D-layer bottleneck dynamics at industry scale.
lineage industry-architecture:jacobides + bottleneck-theory:goldratt + value-chain:porter

Reading the cascade

Jacobides' core proposition: where the bottleneck sits in a value chain determines who captures the surplus. When AI dissolves an existing bottleneck - task-execution, judgment, expertise - the binding bottleneck migrates. New positions become defensible; old positions become wrapper traps. The cascade reads outside-in because the bottleneck shift is itself an industry-scale structural event.

Figure. Where the cascade fires. Cells colored by activity intensity (none / light / medium / heavy). Status flags mark cells containing failure modes (🔴), counter-strategies (🟢), gates (), or dimension shifts (). The arrow shows the reading direction.
outside-in
hop 1 immediate
hop 2 2nd hop
hop 3 3rd hop
1st-order Competitive Ecosystem
3
6 🔴
9 🔴
2nd-order Organizations
1
2 🔴
4 🔴
3rd-order Workflows
4 🔴
5 🔴
4th-order Jobs (workers)
3 🔴
9
inside-out
hop 1 immediate
hop 2 2nd hop
hop 3 3rd hop
1st-order Jobs (workers)
3 🔴
9
2nd-order Workflows
4 🔴
5 🔴
3rd-order Organizations
1
2 🔴
4 🔴
4th-order Competitive Ecosystem
3
6 🔴
9 🔴

How it plays out, mechanism by mechanism

The cascade's load-bearing causal links, in order of how they fire. Each link names the actual mechanism - the carrier, the channel, the why - not just the relationship.

Hop 1 immediate · 4 mechanisms
  • Industry Bottleneck Location Shift (Jacobides) industry-bottleneck-shift cross layer driver Clockspeed clockspeed 🔀 industry→org

    Clockspeed advantage matters only where the binding bottleneck is. The book's framing of Yahoo is the warning case at industry scale: Yahoo was fast, but fast in editorial curation when the bottleneck had moved to algorithmic discovery. Clockspeed in the wrong bottleneck location does not win. Industry-level bottleneck migration redefines what counts as advantage for firms.

  • Industry Bottleneck Location Shift (Jacobides) industry-bottleneck-shift causes Industry Margin Pool industry-margin-pool [I3→I5]

    The book leans on Jacobides explicitly: bottleneck location determines value capture, so migration of the bottleneck causes migration of the industry margin pool. Walmart's barcode adoption moved the bottleneck from supplier reporting to retailer data, and 'Walmart captured an outsized share' of the growing pie. The same dynamic runs through AI-era industries - wherever the new bottleneck lands, the margin pool follows.

  • Industry Bottleneck Location Shift (Jacobides) industry-bottleneck-shift enables Orchestrator Emergence Mechanism orchestrator-emergence-mechanism [I3→I4]

    Whoever holds the new bottleneck can orchestrate from it. The book's Climate Corp case captures this: once Climate built the digital representation of the farm, 'seed suppliers, insurers, and equipment providers increasingly started building to Climate's standards.' Holding the bottleneck - the data, the decision, the standard - is how a new orchestrator emerges. The bottleneck is the position; orchestration is what gets exercised from it.

  • Industry Bottleneck Location Shift (Jacobides) industry-bottleneck-shift enables Value-Chain Position Strategy value-chain-position-strategy [I3→I5]

    Once the binding bottleneck has migrated, the strategic question for firms becomes positional: which slice of the new chain is worth holding? The book's mining case lays this out as four factors - viable business model, ecosystem response, regulatory exposure, operational cost of owning outcomes - that determine how far up the stack a player should climb. Bottleneck-shift creates the where-to-play question; value-chain position strategy is the firm-level answer.

Hop 2 2nd hop · 5 mechanisms
  • Clockspeed clockspeed cross layer driver Vertical Encroachment vertical-encroachment 🔀 org→industry

    The book is explicit: clockspeed differential is one of three drivers of tool-provider leverage. 'Tool providers often innovate faster than solution providers.' When firms move at radically different speeds, the faster-clockspeed firm encroaches upward - its iteration loop outpaces the slower firm's ability to defend its position. Clockspeed at the firm scale is what drives the industry-scale pattern of vertical encroachment.

  • Clockspeed clockspeed cross layer driver Labor Market Clearing under New Task Economics labor-market-clearing 🔀 org→jobs

    Fast-clockspeed firms hire ahead of slow ones, bidding for AI-native talent and shifting industry-wide labor demand. The book's framing on industry clockspeed reset is that 'once AI enters the system, learning faster and releasing new capabilities every few weeks, it resets the clockspeed for everyone else.' Firm clockspeed drives labor market clearing by determining which firms can pay the premium for new skill stacks first.

  • Orchestrator Emergence Mechanism orchestrator-emergence-mechanism produces Platform Tax Fees platform-tax-fees [I4→I5]

    Once an orchestrator emerges, it charges for access - to customers, to data, to coordination. The book's Best Buy case is the playbook: with brands like Apple and Samsung dependent on its in-store advisory infrastructure, Best Buy could 'tax its partners, through premium placement fees, revenue sharing, and training subsidies.' Platform-tax fees are the natural revenue mode of an orchestrator that others must work through.

  • Industry Margin Pool industry-margin-pool enables Industry-as-Platform Model industry-as-platform [I5→I6]

    Once margin consolidates around orchestrators, the industry starts to behave like a platform. The book's Climate Corp / John Deere / Sephora cases each show the move: the orchestrator stops being a participant in the industry and becomes the substrate the industry runs on. 'Platforms now decide what gets seen and who gets paid.' Margin consolidation is what makes the industry-as-platform form structurally viable.

  • Value-Chain Position Strategy value-chain-position-strategy enables Vertical-AI Specialist (industry archetype) vertical-ai-specialist [I5→I6]

    The book's mining-industry case is the most explicit on this. Earth AI doesn't sell predictive tools and wait - it integrates 'AI-based geological insight, drilling, rapid verification, and ownership of validated mineral deposits' into a single position. Position strategy is what defines the vertical AI specialist: not the model, but the slice of the value chain where vertical integration of AI plus domain plus delivery captures the migrating margin.

Hop 3 3rd hop · 9 mechanisms
  • Labor Market Clearing under New Task Economics labor-market-clearing cross layer driver AI Commoditization ai-commoditization 🔀 jobs→industry

    The book's case on the collapse of the skill premium is that AI doesn't just reduce specific wages - it changes the input cost curve of entire industries. The Harvard Business School consulting study, the chainsaw/logging case, the GPS/taxi case all show the pattern: 'AI augmentation makes high-skilled knowledge workers less scarce.' Once labor reprices industry-wide, the industry's cost structure shifts and commoditization at industry scale follows.

  • Industry-as-Platform Model industry-as-platform cross layer driver AI-Driven Rebundling ai-driven-rebundling 🔀 industry→workflow

    Once an industry runs on platform logic, the set of workflows that can be built is constrained by platform interop. The book's Alexa case is the inverse - without coordination, Alexa couldn't host the workflows partners needed. CCC, by contrast, defines the platform within which insurer/repair-shop/parts-supplier workflows must coordinate. Industry-as-platform reshapes which workflow patterns are viable, by setting the interop layer all workflows have to conform to.

  • Industry-as-Platform Model industry-as-platform cross layer driver The Coordinated Organization the-coordinated-organization 🔀 industry→org

    When an industry becomes platform-shaped, only certain firm forms can participate. The book's framing of the Coordinated Organization - AI managing internal knowledge, decisions, execution - is what platform participation requires. Firms without that internal coordination cannot meet the per-step measurement, governance, and interop demands of a platform-shaped industry. Platform industries select for coordinated firms, and against fragmented ones.

  • Vertical-AI Specialist (industry archetype) vertical-ai-specialist cross layer driver Rebundled Role rebundled-role 🔀 industry→jobs

    Vertical AI specialist firms - Earth AI in mining, Climate Corp in agriculture, vertical-AI legal/medical tools - demand new vertical-specialized human roles: drilling-aware AI engineers, agronomy-aware data scientists, clinically-trained AI auditors. Vertical-AI doesn't replace human roles in its vertical so much as it creates new ones whose rebundling is shaped by the specific industry's substrate.

  • AI Commoditization ai-commoditization causes Vertical Encroachment vertical-encroachment

    The book's professional-services argument is direct: 'if AI performs more of the underlying work, but the firm continues to carry the full burden of accountability, the economics and operating model of professional services will come under pressure.' Once AI commoditizes the underlying expertise, the tool provider - having learned from cross-customer use - moves into the solution layer. Commoditization is the gating condition that makes vertical encroachment economically viable.

  • Vertical Encroachment vertical-encroachment causes Tool Integration Trap tool-integration-trap

    Vertical encroachment is what springs the trap. As the tool provider goes deeper - 'continuously absorbing data, learning from use across a broad set of customers, and integrating those learnings into the core tool' - solution providers reorient their workflows and business models around the engine to extract its performance gains. The book is explicit: the trap is created by 'solution providers marching downward into the tool, hoping to gain its benefits to compete better in the short term.'

  • AI Commoditization ai-commoditization enables Vertical Encroachment vertical-encroachment

    The book frames the irony of dependence explicitly: 'when the cost of executing knowledge work collapses, and what used to take a team of analysts now takes a single prompt, companies that adopt these tools might gain short-term efficiency but risk losing long-term control.' Commoditization at the task level enables encroachment because, once executed cheaply, the underlying capability is no longer the moat. The tool provider takes the surplus.

  • AI Commoditization ai-commoditization enables Industry Boundary Dissolution Mechanism industry-boundary-dissolution-mechanism [I0→I1]

    When task-level AI commoditizes, expertise that used to define an industry's gates becomes available off the shelf. The book is direct: 'industry boundaries are constantly shifting, making it easier to borrow capabilities from other sectors… A startup from another sector can become your fiercest rival.' MrBeast in burgers, fitness apps cross-selling therapy, insurers pricing health off fitness data - boundaries dissolve because the bottlenecks that held them in place are no longer scarce. Commoditization is the dissolver.

  • Industry-as-Platform Model industry-as-platform enables Strategic Postures Typology (Reactive Optimizer / Anticipator / Logic Shifter / Field Reshaper) strategic-postures-typology [I6-internal]

    Once the industry runs on platform logic, the firm-level posture choice becomes structural. The book's four-posture taxonomy - reactive optimizer, anticipator, logic shifter, field reshaper - is built on the agricultural example precisely because the industry has become platform-shaped. Traditional agribusinesses optimize today's tasks; precision-ag anticipators ride the puck; Deere logic-shifts decision authority into the tractor; Climate reshapes the field. The platform-shaped industry is what makes the typology actionable rather than theoretical.

Where this fires in the wild

Real-world cases where the cascade has played out (or where it's currently playing out). The abstract primitives become concrete when you can see the mechanism firing at a named entity in a specific year.

From the book 2006-2018

Climate Corp moves the bottleneck from data to insurance

Climate Corp / Monsanto

Climate Corp started as a weather-data and analytics layer for farmers, then built a digital representation of every US field. Once it held that representation, the binding bottleneck migrated from agronomic data (commoditizing) to insurance underwriting and field-level recommendations. After Monsanto's 2013 acquisition, Climate Corp became the platform setting farming standards - orchestrator-emergence-mechanism firing on industry-bottleneck-shift, with vertical-encroachment up the value chain into seed and chemical decisions.

From the book 2015-2026

CCC vs Tractable: the auto-claims bottleneck splits

CCC Intelligent Solutions vs Tractable

CCC built auto-claims coordination on consensus-based standardization - a unified vehicle-damage representation, repair cost model, and shop/parts workflow. Tractable arrived with photo-based AI damage assessment that needed no consensus and no industry standard. The bottleneck migrated from CCC's standardization moat to AI-generated damage representations. Insurers like Geico and Tokio Marine now coordinate around Tractable's shared model in real time, compressing claim cycles from 14 days to hours. Industry-bottleneck-shift fires; CCC's industry-as-platform position is contested.

From the book 2001-2010

Apple's iPod and iTunes shift the music bottleneck

Apple

The book's canonical case: as the recorded-music industry's manufacturing and distribution bottlenecks collapsed, Apple rebundled discovery, access, and playback into iTunes + iPod across the consumer-electronics boundary. The new bottleneck - integrated discovery and frictionless access - sat outside the music industry. industry-bottleneck-shift drove industry-architecture-shift, and value created in music ended up captured in consumer electronics. The classic Jacobides illustration.

Reading from your position

Pick where you sit in this cascade. Same primitives, completely different read - what you cause, what's coming for you, and what counter-moves you can wield.

As Ecosystem Orchestrator 🟢 advantaged

As Ecosystem Orchestrator, this cascade plays to your structural advantage. 2 capabilities you can wield are present. 0 threats to watch.

Platforms, marketplaces, ecosystem leaders - you coordinate complementors around a value proposition you own.

You are here

  • ecosystem-control
  • the-coordinated-organization

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

No specific threats to your position in this cascade.

What's available to you

  • 🟢 Platform Tax Fees hop 2 · Competitive Ecosystem
  • 🟢 Industry-as-Platform Model hop 2 · Competitive Ecosystem

Your moves

  1. Move first to capture the orchestrator-emergence position the cascade opens.
    The cascade routes from bottleneck-shift through orchestrator-emergence-mechanism - bottleneck migration creates a brief window where the new orchestrator hasn't been named yet. Whoever moves first with credible coordination capability gets the platform-tax-fees flow for the next architecture.
    watch for If two or more well-capitalized firms are launching 'platform' or 'standard' initiatives in the same year, the orchestrator slot is being contested. Whoever signs the first 50 anchor complementors wins it.
  2. Lock in industry-as-platform structure before any incumbent firm restructures into one.
    The cascade ends in industry-as-platform as the I6 model. The orchestrator who shapes the platform model first sets the rules - complementor terms, take-rates, governance. Incumbents who try to restructure into platforms after the orchestrator emerges face the orchestrator's terms, not their own.
    watch for When an incumbent in your industry announces 'we're building a platform,' check whether they're announcing your standard or theirs. If theirs, you mispriced your platform terms; tighten before they sign their first anchor partner.
    • industry-as-platform
    • ecosystem-control
    • complementor-alignment-mechanism
As Tool Provider 🟢 advantaged

As Tool Provider, this cascade plays to your structural advantage. 4 capabilities you can wield are present. 0 threats to watch.

Foundation-model providers, infrastructure layers, AI primitives - you sell capability that others integrate.

You are here

  • ai-as-an-engine

What you cause

  • causes Behavior Graph
  • causes Performance-Based Lock-In
  • causes Wrapper
  • causes Ecosystem Control
  • causes AI-Driven Rebundling
  • causes Unbundling

What's coming for you

No specific threats to your position in this cascade.

What's available to you

  • 🟢 AI Commoditization hop 2 · Jobs (workers)
  • 🟢 Vertical Encroachment hop 2 · Organizations
  • 🟢 Performance-Based Lock-In hop 2 · Workflows
  • 🟢 Platform Tax Fees hop 2 · Competitive Ecosystem

Your moves

  1. Lock in performance-based moats while the bottleneck still sits at your layer.
    The cascade routes through performance-based-lock-in as the hop-2 effect of bottleneck migration. Tool providers have a window where superior model performance directly hardens customer dependence - once the bottleneck migrates, performance gaps stop converting to lock-in.
    watch for When customers stop benchmarking your model against competitors and start benchmarking integration depth, the bottleneck has already moved. You have 6-12 months to convert performance gaps into switching costs.
  2. Forward-integrate into vertical-encroachment before the bottleneck migrates away from raw capability.
    The cascade surfaces vertical-encroachment as a cross-layer driver from org to industry once the bottleneck shifts. Tool providers who don't encroach early get squeezed between commoditization below and orchestrators above. Pick three verticals and ship first-party products before the orchestrator emerges.
    watch for If a solution-provider in your ecosystem is signing customers faster than you can ship integrations, they're capturing the margin pool you should have. That's the cue to encroach, not partner.
As Solution Provider 🔴 threatened

As Solution Provider, you're on the receiving end of this cascade. 4 threats surface against your position. 1 counter-strategy is available.

You package tools into outcomes for end customers - vertical-SaaS, services firms, integrators absorbing risk.

You are here

  • solution-provider

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Tool Integration Trap hop 3 · Organizations
  • 🔴 Wrapper hop 3 · Organizations
  • 🔴 Vertical Encroachment hop 2 · Organizations
  • 🔴 AI Commoditization hop 2 · Jobs (workers)

What's available to you

  • 🟢 Vertical-AI Specialist (industry archetype) hop 2 · Competitive Ecosystem

Your moves

  1. Reposition above the new bottleneck before it stabilizes - the old margin pool is gone.
    Jacobides' core insight in the cascade: industry-margin-pool follows industry-bottleneck-shift. Solution providers stuck at the old bottleneck location collapse into the wrapper trap. The move is to identify where the next bottleneck is forming (data, coordination, distribution) and reposition there before it hardens.
    watch for Track which layer of the value chain is gaining pricing power quarter over quarter. If it's not yours, you have 2-4 quarters to migrate before the orchestrator at the new bottleneck calcifies a take-rate.
  2. Specialize as a vertical-ai-specialist where the bottleneck migrated to domain-specific data and trust.
    The cascade flows from bottleneck-shift directly into vertical-ai-specialist as an I5 archetype. Solution providers who package generic AI plus deep domain data into a vertical can sit on the new bottleneck before horizontal players reach it.
    watch for If you can name a customer who would lose 6+ months of work product by switching to a horizontal competitor, you hold vertical specificity. If they could switch in a sprint, the bottleneck didn't migrate to you.
As Complementor 🔴 threatened

As Complementor, you're on the receiving end of this cascade. 3 threats surface against your position. 0 counter-strategies are available.

You build on someone else's platform or ecosystem. Your leverage comes from being substitutable across orchestrators.

You are here

  • solution-provider

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Ecosystem Control hop 3 · Competitive Ecosystem
  • 🔴 Platform Tax Fees hop 2 · Competitive Ecosystem
  • 🔴 Wrapper hop 3 · Organizations

What's available to you

No specific counter-strategies for your position appear in this cascade.

Your moves

  1. Track bottleneck migration and reposition before the platform-tax-fees structure firms up.
    The cascade shows platform-tax-fees being produced as bottleneck shift hardens into orchestrator emergence. Complementors who don't reposition before the take-rate is set will pay it forever. The move is to find the next bottleneck and become indispensable there before the new orchestrator arrives.
    watch for If you're paying a take-rate above 15% and the orchestrator's marginal cost to serve you is falling, you've been priced into a wrapper. Multi-home or migrate up the stack.
  2. Bet on vertical-specificity where horizontal orchestrators can't economically follow.
    Vertical-ai-specialist is the I5/I6 escape route from generic complementor positions. Complementors who go deep into a regulated, trust-bound, or relationship-bound vertical earn margin the horizontal orchestrator can't squeeze without losing their own platform claim.
    watch for If your orchestrator launches a generic version of your category and your churn doesn't move, you've found vertical-specificity. If churn spikes, you were a horizontal complementor pretending to be a specialist.
As Incumbent Firm 🔴 threatened

As Incumbent Firm, you're on the receiving end of this cascade. 5 threats surface against your position. 0 counter-strategies are available.

Established firms with legacy advantages, embedded customer relationships, and the burden of pre-AI structure.

You are here

  • the-coordinated-organization

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Tool Integration Trap hop 3 · Organizations
  • 🔴 Wrapper hop 3 · Organizations
  • 🔴 AI Commoditization hop 2 · Jobs (workers)
  • 🔴 Industry Bottleneck Location Shift (Jacobides) hop 0 · Competitive Ecosystem
  • 🔴 Vertical Encroachment hop 2 · Organizations

What's available to you

No specific counter-strategies for your position appear in this cascade.

Your moves

  1. Acknowledge the bottleneck has moved - your legacy margin pool is being unwound, not defended.
    Incumbents lose the cascade because they fight to hold the old bottleneck. The cascade routes through industry-margin-pool restructuring - the old pool drains. The first move is structural acceptance: the firm has to be rebuilt around the new bottleneck, not the old one.
    watch for If your strategic-plan slides still organize the firm around the value chain as it looked five years ago, the bottleneck has moved without you. Rewrite the plan around where margin is going, not where it came from.
  2. Use network-capital and existing customer relationships to become a vertical-ai-specialist incumbent.
    Incumbents have an asset AI-natives don't: customer relationships, regulatory standing, distribution. The cascade shows vertical-ai-specialist as an I5/I6 escape; for incumbents, the play is to combine their existing trust with AI-native execution speed to occupy the new bottleneck.
    watch for If the AI-native entrants in your space are still hiring sales teams, you have time. When they hire their first heads of regulatory affairs, the trust moat is being attacked - match clockspeed or cede the vertical.
As AI-Native Entrant ⚖ mixed

As AI-Native Entrant, the cascade is mixed for you - 2 capabilities and 2 threats both fire.

AI-first firms unburdened by legacy structure - fast-clockspeed startups and AI-native verticals.

You are here

  • vertical-ai-specialist

What you cause

  • cross-layer-driver Rebundled Role

What's coming for you

  • 🔴 Ecosystem Control hop 3 · Competitive Ecosystem
  • 🔴 AI Commoditization hop 2 · Jobs (workers)

What's available to you

  • 🟢 Clockspeed hop 1 · Organizations
  • 🟢 AI-Driven Rebundling hop 3 · Jobs (workers)

Your moves

  1. Race to lock in vertical-ai-specialist positions before incumbents wake to the bottleneck shift.
    The cascade puts vertical-ai-specialist as the I5/I6 archetype that emerges from bottleneck-shift. AI-natives have a clockspeed advantage in the window where incumbents are still defending the old bottleneck. Use it.
    watch for If you're winning deals on demo-day capability rather than on integrated workflow ownership, the bottleneck hasn't fully moved yet. Spend the next two quarters building the workflow depth that will hold when capability commoditizes.
  2. Sit on the new bottleneck as a coordination-layer position, not just a vertical product.
    Bottleneck-shift produces orchestrator-emergence - AI-natives who build single-vertical products miss the chance to become the platform. Look at whether your vertical, plus two adjacent ones, can be coordinated by the same data substrate. If yes, build platform; if no, deepen vertical.
    watch for Three signals you should orchestrate, not just ship: (1) your customers are asking to share data with their suppliers; (2) competitors are integrating to your data shape, not theirs; (3) regulators are citing your terminology in rule-making.
As Worker (Above the Algorithm) 🟢 advantaged

As Worker (Above the Algorithm), this cascade plays to your structural advantage. 3 capabilities you can wield are present. 1 threat to watch.

You direct or govern AI - strategy, judgment, design, taste, exception-handling, system-of-work ownership.

You are here

  • rebundled-role

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 AI Commoditization hop 2 · Jobs (workers)

What's available to you

  • 🟢 Tacit Knowledge hop 3 · Jobs (workers)
  • 🟢 Curation hop 3 · Jobs (workers)
  • 🟢 Curiosity hop 3 · Jobs (workers)

Your moves

  1. Position your role on the new bottleneck - coordination, judgment, design - not on the dissolving one.
    The cascade routes through skill-premium and rebundled-role at the jobs layer. The new premium roles are the ones that resolve the new bottleneck, not the ones that polished work at the old one.
    watch for If your job description in 2026 is recognizably the same as it was in 2022, the bottleneck moved without you. Negotiate a re-scope that puts you on coordination, exception-handling, or strategy - not execution.
  2. Lean into tacit-knowledge and curiosity as the residual moats once the bottleneck dissolves at the task layer.
    The cascade surfaces tacit-knowledge, curation, and curiosity as the S5b counter-positions. When the bottleneck migrates from task execution to coordination, the workers who held the firm's tacit context become the bridge - and the bridge is paid.
    watch for If junior peers and outside consultants can answer your firm's hard questions as well as you can, your tacit-knowledge premium has eroded. Re-deepen by taking on the cross-functional problems no one has documented yet.
    • tacit-knowledge
    • curation
    • curiosity
As Worker (Below the Algorithm) 🔴 threatened

As Worker (Below the Algorithm), you're on the receiving end of this cascade. 3 threats surface against your position. 1 counter-strategy is available.

Your tasks are AI-mediated and AI-governed. You execute against AI-set parameters.

You are here

  • below-the-algorithm-worker

What you cause

Your position doesn't cause downstream effects in this cascade - you're at the receiving end.

What's coming for you

  • 🔴 Labor Market Clearing under New Task Economics hop 2 · Jobs (workers)
  • 🔴 AI Commoditization hop 2 · Jobs (workers)
  • 🔴 Skill Premium hop 3 · Jobs (workers)

What's available to you

  • 🟢 Rebundled Role hop 3 · Jobs (workers)

Your moves

  1. Recognize the bottleneck has migrated away from your task layer - labor-market-clearing is coming.
    The cascade ends in labor-market-clearing for jobs that sat on the old bottleneck. Below-the-algorithm workers whose task category was the bottleneck face the steepest clearing. The first move is honest: the task is being repriced, not just retooled.
    watch for If posting volume in your job category is rising while average salary is falling, that's labor-market-clearing in progress. Don't wait for layoffs - move to a role on the new bottleneck while you still have option value.
  2. Build network-capital across teams faster than the labor-market clears your task.
    The cascade routes through skill-premium collapse. The escape is network-capital - being the person across teams who knows where to route problems, not the person who handles a now-commoditized task.
    watch for Track the number of cross-functional projects you're on. If you're stuck on a single team running the same workflow, you're exposed to clearing. If you're tagged into three teams' decisions, you've built routing capital that survives task-level repricing.
1st-order Competitive Ecosystem

At the competitive ecosystem, bottleneck migration immediately enables orchestrator-emergence-mechanism (Adner) and reshapes industry-margin-pool. The value-chain-position-strategy question becomes the central strategic question for every firm in the industry. By hop 2 the industry-as-platform form emerges and vertical-ai-specialist firms position themselves at the new bottleneck. By hop 3 the failure chain - vertical-encroachmenttool-integration-trapwrapper - runs its course, and performance-based-lock-in consolidates control around the new bottleneck holders.

2nd-order Organizations

Firms feel the bottleneck shift as a clockspeed test: whoever recognizes the new bottleneck location fastest moves first. By hop 2 firms confronting the wrong bottleneck face tool-integration-trap risk. By hop 3 the structural sorting completes - firms exhibiting incumbent-restructure-success-pattern or entrant-scaling-success-pattern survive; the rest become wrappers.

3rd-order Workflows

The workflow scale only activates at hop 2: workflows must be redesigned around the new bottleneck location. By hop 3, the solution-advantage position becomes the workflow-level expression of bottleneck mastery - workflows that absorb risk and integrate systems at the new bottleneck win.

4th-order Jobs (workers)

Worker effects appear at hop 2 as labor-market-clearing shifts demand toward roles aligned with the new bottleneck. By hop 3 worker-level rebundling is widespread, and the residual sources of human value (tacit-knowledge, curation, curiosity) align around what the new bottleneck can't yet automate.

1st-order Jobs (workers)

Worker effects appear at hop 2 as labor-market-clearing shifts demand toward roles aligned with the new bottleneck. By hop 3 worker-level rebundling is widespread, and the residual sources of human value (tacit-knowledge, curation, curiosity) align around what the new bottleneck can't yet automate.

2nd-order Workflows

The workflow scale only activates at hop 2: workflows must be redesigned around the new bottleneck location. By hop 3, the solution-advantage position becomes the workflow-level expression of bottleneck mastery - workflows that absorb risk and integrate systems at the new bottleneck win.

3rd-order Organizations

Firms feel the bottleneck shift as a clockspeed test: whoever recognizes the new bottleneck location fastest moves first. By hop 2 firms confronting the wrong bottleneck face tool-integration-trap risk. By hop 3 the structural sorting completes - firms exhibiting incumbent-restructure-success-pattern or entrant-scaling-success-pattern survive; the rest become wrappers.

4th-order Competitive Ecosystem

At the competitive ecosystem, bottleneck migration immediately enables orchestrator-emergence-mechanism (Adner) and reshapes industry-margin-pool. The value-chain-position-strategy question becomes the central strategic question for every firm in the industry. By hop 2 the industry-as-platform form emerges and vertical-ai-specialist firms position themselves at the new bottleneck. By hop 3 the failure chain - vertical-encroachmenttool-integration-trapwrapper - runs its course, and performance-based-lock-in consolidates control around the new bottleneck holders.

This cascade has no counter-strategy primitives surfaced - bottleneck migration is a structural force, not something individual firms counter. The strategy is to *position* at the new bottleneck before others do, which is the value-chain-position-strategy question this cascade activates immediately. What to watch: which of the four candidate new bottlenecks (data-aggregation, coordination-substrate, risk-absorption, ecosystem-orchestration) your industry's pressure is actually crystallizing around.