What follows from holding the Right to Coordinate?
From the meta-capability through workflow ownership, firm-level decision rights, and industry-level orchestration.
visited
16
edges
22
hops
3
chains
4 / 4
failure modes
4
counters
3
right-to-coordinatecapability
Right to Coordinate
Jobs S6 Org O3 Workflow W5 Industry I4
The earned ability to organize an ecosystem by reducing friction in both decision-making and execution, requires deep integration, not just UI simplification.
Reading the cascade
The Right to Coordinate is the meta-capability that lets a firm or actor wield the five coordination powers (representation / decision / execution / composition / governance). It is the most consequential single primitive in the AI-era stack: whoever holds it captures the substrate. The cascade defaults to outside-in because the start node is multi-chain and the strongest first-order effects appear at industry and org scales.
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 1immediate
hop 22nd hop
hop 33rd hop
1st-orderCompetitive Ecosystem
4🔴🟢
4🔴
2🟢
2nd-orderOrganizations
5🔴🟢
3🔴
3rd-orderWorkflows
5🔴🟢
5🔴▼
3🟢
4th-orderJobs (workers)
1
1
1
▲inside-out
hop 1immediate
hop 22nd hop
hop 33rd hop
1st-orderJobs (workers)
1
1
1
2nd-orderWorkflows
5🔴🟢
5🔴▼
3🟢
3rd-orderOrganizations
5🔴🟢
3🔴
4th-orderCompetitive Ecosystem
4🔴🟢
4🔴
2🟢
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
Right to Coordinateright-to-coordinate cross layer driver Gate Evolution Mechanism (endogenous gates)gate-evolution-mechanism🔀 workflow→jobs
Whoever holds the right to coordinate at workflow scale defines what gates workers have to pass to participate. The trucker case is the bluntest: when Uber Freight became the workflow owner, the gates moved from skill, reliability, and local relationship to algorithmic metrics - acceptance rate, on-time delivery, what the platform could measure. The workflow owner doesn't just decide work allocation; the workflow owner sets the criteria for who counts as a worker.
Right to Coordinateright-to-coordinate cross layer driver Coordination Powers Typologycoordination-powers-typology🔀 workflow→org
The book's five-factor coordination framework - representation, decision, execution, composition, governance - is the typology of coordination powers. Whoever earns Right to Coordinate at workflow scale acquires these powers at firm scale, because they hold the substrate from which all five operate. Walmart with barcodes, Climate Corp with farm data, CCC with the damage model - workflow-level coordination wins translate directly into firm-level redistribution of decision rights.
Right to Coordinateright-to-coordinate cross layer driver Vertical Encroachmentvertical-encroachment🔀 workflow→industry
The book is unambiguous: 'when the tool a company uses to build its solution becomes so central that it defines the solution itself, the balance of power shifts, and the tool provider moves from being an enabler to becoming a rival.' Workflow ownership - Right to Coordinate at W5 - is what tool providers ride into the solution layer. Vertical encroachment at industry scale is the playing-out of workflow-scale ownership.
Right to Coordinateright-to-coordinate causes Tool Integration Traptool-integration-trap[W5→W6]
Whoever owns the right to coordinate ends up holding the chokepoint others have to work through. The book traces this through the tool-integration trap directly: as the AI engine improves and solution providers re-orient around it to gain its performance gains, the engine acquires Right to Coordinate, and 'every improvement in the engine delivers an improvement in the solution… but each lift tightens the grip.' Ownership of coordination at workflow scale is what tips solution providers into the trap.
The book describes the integration trap as performance-based lock-in, distinct from contractual lock-in: 'the solution becomes so reliant on the superior performance of an external engine that leaving it would mean falling behind the rest of the industry.' As more firms in an industry fall into the same trap, the same tool provider's lock-in becomes the industry's lock-in. Org-level trap propagates to industry-scale dependence.
The book's five coordination powers determine which actor in a firm shapes governance at workflow scale. Whoever holds representation-power decides what is visible in the workflow; whoever holds governance-power sets the rules. As coordination powers redistribute at the org level - decentralized in some cases (sales forecasting to edges), centralized in others (predictive pricing to HQ) - the workflow's governance locus follows the redistribution.
Coordination Powers Typologycoordination-powers-typology cross layer driver Above-the-Algorithm vs. Below-the-Algorithmabove-the-algorithm-vs-below-the-algorithm🔀 org→jobs
The book is explicit that when a firm centralizes decision-power in AI, more workers end up below-the-algorithm: 'pricing decisions increasingly shift to the center, where AI tools set prices at scale. Power consolidates at headquarters, and local autonomy goes down.' Firm-level redistribution of coordination powers directly determines which workers sit above the algorithm and which sit below it.
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.'
Tool Integration Traptool-integration-trap produces when Wrapperwrapper
Wrapper position is the third stage of the integration trap, as the book lays it out: first the solution provider builds workflows around the engine; then it reorients its business model to leverage the engine; finally it no longer competes on its own capabilities but on how well it integrates someone else's. At that point the company may still look like a solution provider, but it has become 'a pejorative reference to an interface wrapped around someone else's performance layer.'
Hop 3 3rd hop · 3 mechanisms
Above-the-Algorithm vs. Below-the-Algorithmabove-the-algorithm-vs-below-the-algorithm cross layer driver Workflow Governance Locus Shiftworkflow-governance-locus-shift🔀 workflow→workflow
The book's clearest claim on governance is that workers above the algorithm - those who design or operate it - govern the workflow; workers below the algorithm are governed by it. Where governance locus sits within a workflow is therefore a function of where workers are positioned relative to the coordination layer. Move workers above; governance moves with them. Push workers below; governance moves to whoever holds the algorithm.
Once a solution provider is reduced to a wrapper, pricing power has already left. The tool provider extracts 'by adjusting pricing or usage terms or by instituting performance-based fees.' The wrapper's customers aren't buying the wrapper's expertise - 'they're buying an experience powered by the same engine that now underlies dozens of other players in the industry.' Wrapper position causes tool-provider lock-in because at that point the wrapper has no leverage left to resist.
Workflow Governance Locus Shiftworkflow-governance-locus-shift enables Value-Capture Measurement (workflow-level)value-capture-measurement[W5→W6]
You can't capture value you can't see. The book frames the move from selling tools to delivering outcomes as a shift in representation first: 'the solution provider builds a live model of the customer's environment by capturing data on how the tool performs.' Once governance is throughout-workflow rather than end-of-workflow, the per-step data needed to bill for outcomes - Winterhalter per wash, Rolls-Royce per propulsion hour, Orica per rock-on-ground - becomes generable. Governance locus shifts first; outcome pricing follows.
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.
Validation walkthrough 2022-2025
Mastercard earns the right to coordinate fraud across the network
Mastercard
Mastercard's Decision Intelligence and Account Intelligence built on a coordination substrate Mastercard already held - the network itself. Once gen-AI scoring became the operating layer for fraud decisions across issuers, merchants, and cardholders, Mastercard held the right-to-coordinate at workflow scale (per-transaction decisioning) and accrued the five coordination powers at firm scale. Scope-expansion to Account Intelligence repackages those powers as a B2B product. The cascade fires: right-to-coordinate produces system-integration at O4, scope-expansion at O5, and vertical-encroachment into bank-analytics territory.
DBS Bank restructures around the right to coordinate
DBS Bank
DBS reorganized into 33 cross-functional platforms in 2018 under a Platform Operating Model with 2-in-a-box (business + IT) leadership, then ran successive Operating Model Transformations from 2024 to rebuild specific workflows around human + AI collaboration (9 completed in 2025; 800+ models, 350+ use cases). DBS earned the right-to-coordinate INSIDE the bank - across consumer, SME, and institutional banking - rather than across an industry. The cascade produces the-coordinated-organization at O5, system-integration at O4, and coordination-advantage at O1 that competitors can't replicate without paying the same decade-long restructuring cost.
Walmart's barcode-native architecture as right-to-coordinate
Walmart vs Kmart
Both Walmart and Kmart adopted barcodes. Only Walmart built a barcode-native architecture - turning scan data into representation-power (real-time SKU state across the chain), decision-power (replenishment without human intervention), execution-power (supplier-direct flow), composition-power (cross-dock vs warehouse logic), and governance-power (vendor compliance via the data). Walmart earned the right-to-coordinate at workflow scale and translated it directly into vertical-encroachment up the supplier chain. The cascade is the canonical book illustration of how workflow-scale ownership cascades into industry-scale dominance.
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.
+4 absent actors
These actors don't appear in this cascade: Tool Provider, Incumbent Firm, AI-Native Entrant, Worker (Below the Algorithm).
AsSolution Provider ⚖ mixed
As Solution Provider, the cascade is mixed for you - 3 capabilities and 3 threats both fire.
You package tools into outcomes for end customers - vertical-SaaS, services firms, integrators absorbing risk.
Earn right-to-coordinate by integrating both decision and execution layers, not just one.
The cascade frames right-to-coordinate as a meta-capability requiring deep integration. Solution-providers who automate execution but not decision (or vice versa) leave half the workflow to a competitor or to the tool provider. Own both, or neither.
watch forWhen customers route a decision through your product without escalating it back to a human dashboard, you hold the decision layer. When the same product also executes the resulting action without handoff, you hold both - and right-to-coordinate is yours.
Convert system-integration depth into solution-bundle pricing that the tool provider can't replicate.
The cascade routes from right-to-coordinate to solution-bundle. Once you hold coordination, bundle the workflow into a single outcome-priced offer. The tool provider can match capabilities but can't match a coordinated bundle without becoming a solution provider themselves - and they won't.
watch forIf your average contract value is rising while your seat count is flat, you've moved to bundle pricing. If it's the reverse, you're still selling tools dressed up as solutions.
Use value-capture-measurement at the workflow level to defend against wrapper drift.
The cascade surfaces value-capture-measurement as the W5->W6 counter-strategy. Without measurement, right-to-coordinate gets mistaken for UI ownership - and the firm drifts into wrapper. Measure the workflow-level outcome you're improving, and price against it.
watch forTrack the percentage of revenue tied to outcome-based pricing vs. seat-based. If outcome-based is rising, you're defending coordination. If seat-based is rising, you're drifting toward wrapper.
Use right-to-coordinate concepts to negotiate your terms - if you hold one of the coordination powers, price for it.
The cascade's coordination-powers-typology gives complementors a vocabulary for what they actually hold. Complementors who can name their power (representation, decision, execution) can negotiate from structural strength, not from feature parity.
watch forIf you can articulate which coordination power the orchestrator can't replicate without you, you have negotiating power. If the orchestrator can list five complementors with your same claim, you don't.
Avoid the wrapper trap by holding solution-bundle pricing, not feature pricing.
The cascade explicitly produces wrapper when right-to-coordinate is mishandled. Complementors who sell discrete features to an orchestrator end up wrapped; those who sell coordinated bundles to end customers via the orchestrator hold real value.
watch forTrack who signs your contracts - the orchestrator (you're a vendor and likely a wrapper candidate) or the end customer through the orchestrator (you hold the value relationship). The latter is the structural defence.
Operationalize right-to-coordinate through coordination-powers-typology - pick which power you hold and entrench.
The cascade routes right-to-coordinate through coordination-powers-typology. Orchestrators should explicitly choose: decision power, representation power, or execution power as their primary lock-in. Generalists across all three get out-specialized; specialists win their slice and bundle later.
watch forIf your platform's pitch deck claims all three coordination powers equally, you haven't picked. Pick - and let the metrics for that one rise faster than the others.
Protect right-to-coordinate from workflow-governance-locus-shift by hard-coding governance into your platform's standard.
The cascade surfaces workflow-governance-locus-shift as a hop-2 cross-layer driver. Orchestrators who don't hard-code governance into the standard see it drift toward whichever participant captures the workflow's bottleneck. Bake governance in early.
watch forIf a regulator or industry body proposes governance rules for your ecosystem that differ from yours, your governance claim is being contested. Engage and win the rule-making, or migrate to a frame where they can't override you.
As Worker (Above the Algorithm), the cascade is mixed for you - 0 capabilities and 0 threats both fire.
You direct or govern AI - strategy, judgment, design, taste, exception-handling, system-of-work ownership.
You are here
above-the-algorithm-vs-below-the-algorithm
What you cause
causesCoordination-Based Constraints
cross-layer-driverWorkflow Governance Locus Shift
What's coming for you
No specific threats to your position in this cascade.
What's available to you
No specific counter-strategies for your position appear in this cascade.
Your moves
Position your role at the above-the-algorithm side of the coordination layer the cascade opens.
The cascade routes right-to-coordinate through above-the-algorithm-vs-below-the-algorithm as a cross-layer driver. Workers who hold coordination authority over AI workflows sit above the algorithm; those who execute under AI-set parameters sit below. Pick deliberately.
watch forIf you're the human signing off on AI-generated outputs in your firm, your above-the-algorithm role is real. If the AI's outputs go directly to execution without your sign-off, you've already been moved below - negotiate a coordination scope or risk redundancy.
Build coordination-based-constraints into your firm's workflows that depend on your judgment to operate.
The cascade surfaces coordination-based-constraints as the S4->S5a transition. Above-the-algorithm workers who design and own these constraints become structurally necessary - the constraint can't fire without their interpretation.
watch forIf you've authored a workflow constraint (compliance, quality, escalation) that other teams cite as authoritative, you've built coordination-based-constraint ownership. The role is structurally yours until the constraint changes.
The Right to Coordinate immediately produces vertical-encroachment at industry scale - actors holding it reach into adjacent territories. Gate-evolution-mechanism fires because the holder of Right-to-Coordinate redefines the gates others must pass. By hop 2 tool-provider-lock-in consolidates; solution-provider positions emerge as the structural alternative. By hop 3 the risk-absorption and value-capture-measurement counter-strategies are visible.
2nd-orderOrganizations
At the firm scale, holding (or losing) Right-to-Coordinate immediately produces system-integration (counter-strategy), coordination-powers-typology (the typology activates), and tool-integration-trap (the failure mode for firms that lose it). By hop 2 wrapper position is the outcome for firms that ceded their Right-to-Coordinate.
3rd-orderWorkflows
Workflows are where Right-to-Coordinate is actually wielded. At hop 1 the coordination-powers-typology structures the workflow; system-integration is the operational mechanism. By hop 2 workflow-governance-locus-shift activates; by hop 3 risk-absorption and value-capture-measurement appear as the workflow-level counter-strategies.
4th-orderJobs (workers)
Worker effects are minimal - only one node per hop. Right-to-Coordinate is a firm/workflow capability; its worker-level effect is mostly indirect, through above-the-algorithm-vs-below-the-algorithm sorting at hop 2.
1st-orderJobs (workers)
Worker effects are minimal - only one node per hop. Right-to-Coordinate is a firm/workflow capability; its worker-level effect is mostly indirect, through above-the-algorithm-vs-below-the-algorithm sorting at hop 2.
2nd-orderWorkflows
Workflows are where Right-to-Coordinate is actually wielded. At hop 1 the coordination-powers-typology structures the workflow; system-integration is the operational mechanism. By hop 2 workflow-governance-locus-shift activates; by hop 3 risk-absorption and value-capture-measurement appear as the workflow-level counter-strategies.
3rd-orderOrganizations
At the firm scale, holding (or losing) Right-to-Coordinate immediately produces system-integration (counter-strategy), coordination-powers-typology (the typology activates), and tool-integration-trap (the failure mode for firms that lose it). By hop 2 wrapper position is the outcome for firms that ceded their Right-to-Coordinate.
4th-orderCompetitive Ecosystem
The Right to Coordinate immediately produces vertical-encroachment at industry scale - actors holding it reach into adjacent territories. Gate-evolution-mechanism fires because the holder of Right-to-Coordinate redefines the gates others must pass. By hop 2 tool-provider-lock-in consolidates; solution-provider positions emerge as the structural alternative. By hop 3 the risk-absorption and value-capture-measurement counter-strategies are visible.
Three counter-strategies surface: risk-absorption, system-integration, value-capture-measurement - all at workflow and org scales. The structural read: Right-to-Coordinate is the highest-leverage primitive in the graph because it sits upstream of the entire failure chain *and* the entire counter-strategy chain. What to watch: who in your industry holds Right-to-Coordinate, and whether your strategic position is consistent with that fact.