Riding Dynamics, Fighting Inertia skill

Riding Dynamics, Fighting Inertia

Table of Contents

• Why Waves of Change Favor Attackers
• Five Guideposts for Sensing Waves
• Writing a Wave Brief
• The Three Inertias
• Entropy
• Attacker Playbooks
• Notes for Defenders

Why Waves of Change Favor Attackers

In stable periods, incumbents win: scale, brand, distribution, and accumulated learning compound in their favor, and a second-rate strategy is enough. Waves of change — technology shifts, deregulation, demographic and cost-structure changes — reset the contest. The incumbent's optimized machine is optimized for the old world; its margins are hostage to the old model; its people were promoted for mastering rules that no longer apply. For an attacker, a wave is exogenous leverage: you do not have to create the shift, only to see its implications earlier and commit to them more coherently than those who cannot.

The discipline is seeing the wave as it is breaking — not predicting the far future. Most of what matters has already happened: the cost curve has already bent, the rule has already been announced, the behavior has already shifted in the youngest cohort. Strategy reads the present closely rather than the future speculatively.

Five Guideposts for Sensing Waves

Use these as a standing checklist whenever an industry feels like it is moving.

1. Rising fixed costs. When the cost of staying at the technical frontier rises sharply (R&D, content, capital equipment), the industry consolidates around the few who can pay, and everyone else must reposition. Detection questions: What does it cost to field a competitive offering today vs. five years ago? Who can no longer afford the table stakes? Product read: frontier-model training costs consolidate AI infrastructure into a handful of labs — so most companies' strategies should assume models are rented, not owned, and differentiation must live in data, workflow, and distribution built on top of the consolidating layer.

2. Deregulation — and rule changes generally. When governments or platform owners change the rules (deregulation, new compliance regimes, app-store policy, privacy frameworks), the value pool is re-divided. Incumbents systematically misjudge the new world: they keep prices and cross-subsidies anchored to the old regime, overpay to defend formerly protected businesses, and underinvest where the new rules open ground. Detection questions: Which prices in this industry exist only because a rule made them possible? Whose cross-subsidy becomes untenable? Product read: a platform's API pricing change or a new AI act is a re-division of the pool — map who was subsidized by the old rules and serve the newly orphaned.

3. Predictable biases. In transitions, people forecast badly in patterned ways: they extrapolate the present (assuming growth continues because it has), assume the old normal will return, imitate the most visible player, and pile into whatever the herd funds. Each bias is exploitable by whoever bets on the underlying mechanics instead. Detection questions: What does everyone currently assume continues forever? Where is capital crowding on momentum rather than mechanism? The contrarian opportunity is rarely "the opposite" — it is the specific spot the herd's simplification ignores.

4. Incumbent response. Incumbents respond to waves in predictable defensive shapes: protect the legacy margin (milk the old business rather than cannibalize it), retreat upmarket toward their best customers, bundle the threatened product into suites, and announce hybrid offerings that preserve the old economics. Each defensive move tells you where the door is open. Detection questions: Read the incumbent's earnings calls — what number are they defending? What would they have to destroy internally to follow you? Product read: when the suite vendor responds to your point product by bundling harder, they are conceding the standalone market's users while defending the CFO relationship — choose which contest you want.

5. Attractor states. An attractor state is where the industry "should" end up given technology and cost fundamentals — the configuration that would emerge if efficiency alone decided. "All data transport becomes IP" was telecom's attractor state; Cisco rode it for a decade while incumbents protected circuit-switched margins. Attractor states discipline wishful thinking because they are grounded in demand and cost logic, not in your hopes. Detection questions: In the efficient end state, who does the work, who gets paid, and which of today's toll booths still exist? What accelerants (cost curves, standards) and impediments (regulation, switching costs, installed bases) set the pace? Product read: "routine support tickets get resolved by software" is an attractor state; the strategic questions are pace and who owns the workflow when it arrives.

Writing a Wave Brief

Condense the guideposts into a one-page brief before betting a roadmap on a wave:

WAVE BRIEF: [shift name, date]
What already changed: [cost curves, rules, behaviors — facts, not forecasts]
Guidepost readings: [fixed costs / rules / biases / incumbent response / attractor state]
Who is mispositioned: [incumbents and why their economics block response]
The attractor state: [who does the work, who gets paid, when]
Timing risk: [what makes this slower than it looks; can we survive being early?]
Our asymmetry on this wave: [why us]

The timing line is mandatory. Waves reliably take longer than enthusiasts expect — being early without the runway to wait is indistinguishable from being wrong.

The Three Inertias

Inertia is an organization's inability or unwillingness to adapt. Diagnose the type before prescribing — or before attacking — because each has a different mechanism.

Type	Mechanism	Signs	Fix (incumbent)	Attack (challenger)
Routine	Old playbooks keep executing	Metrics, pricing, and processes from the previous era	New metrics, outside hires, forced exposure to lost deals	Compete where the playbook misfires
Culture	Identity blocks adaptation	"We are an X company"; sacred projects; new ventures starved	Simplify, break insulated units, change leaders; takes years	Announce the future loudly — their culture will deny it
Proxy	Customers' inertia shields the incumbent	Incumbent profits from customers not switching	Painful: moving first cannibalizes today's profit	Collapse the customers' switching cost directly

Inertia by routine is the mildest: the organization could adapt but its standard procedures keep reproducing yesterday's answers — airlines after deregulation kept the route, pricing, and staffing formulas of the regulated era for years. The cure is changing what gets measured and who is hired; the attack is simply moving where the routine gives wrong answers.

Inertia by culture is deeper: adaptation threatens identity, status hierarchies, and internal coalitions. Engineering-led cultures dismiss design threats; sales-led cultures dismiss self-serve. Renewal requires simplification first — killing the overgrowth of units, initiatives, and committees in which the old culture lives — then breaking the political structure, then rebuilding. Leaders who skip to "rebuilding" with a new slogan change nothing.

Inertia by proxy is the subtle one: the incumbent is not asleep — it is rationally unresponsive because its profits ride on its customers' inertia. Banks paid low deposit rates while money-market funds grew because most depositors didn't move, and repricing for everyone to retain the few who did would have destroyed margin. The attack: make switching trivial and visible — one-click data migration, automatic import, side-by-side statements. When the customers' inertia breaks, the incumbent's position collapses quickly and it has no practiced response, because its "strategy" was the inertia itself.

Entropy

Entropy is drift, not resistance: absent active management, organizations blur. Product lines proliferate and overlap; prices drift toward undisciplined discounts; cross-subsidies appear that nobody chose; ownership fuzzes. GM's brands — once a clean price-quality ladder from Chevrolet to Cadillac — drifted over decades into overlapping offerings that competed with each other and stood for nothing.

Entropy matters to strategists for two reasons: weeding it from your own garden is valuable work even with no competitor in sight, and a rival's entropy is a map of your opportunity.

Entropy audit (quarterly or annual):

1. Plot every product/plan/SKU by price against the customer need it serves. Overlaps are entropy; so are gaps everyone assumed someone owned.
2. Trace margin by offering. Unchosen cross-subsidies — profitable line A quietly funding zombie line B — get a decision: re-price, kill, or choose the subsidy explicitly.
3. List the discounts, exceptions, and custom deals added in the last two years. Each was locally rational; ask what the set does to the price ladder.
4. Re-draw the intended structure (clean ladder, named segments, one owner per line) and schedule the cuts.

The test for entropy is the no-competition test: if these blurred lines and leaky prices would still be wrong with zero competitors, the problem is entropy, and the fix is housekeeping, not repositioning.

Attacker Playbooks

Playbook A — Margin shadow. Exploit an incumbent defending legacy margins. (1) Identify the revenue line they cannot cannibalize — seat licenses, services attach, transaction fees. (2) Configure your economics so following you destroys that line: usage-based pricing against per-seat, software against their services revenue. (3) Take the customers they rationally sacrifice first (small, price-sensitive, modern-stack), then move up. Requirement: your cost structure must be structurally lower, not VC-subsidized — a subsidy shadow evaporates. Risk: an incumbent with a board-level crisis may burn the boats and follow anyway; watch for leadership change as the signal.

Playbook B — Wave rider. Pick the wave with the guideposts, then commit with a design-type strategy configured for the attractor state: every piece — pricing, architecture, hiring, channel — presupposing the new world, with no hedge dragging the old one along. Set a proximate-objective ladder (resolve ambiguity in weeks, capability in quarters) rather than a five-year vision. Risk is timing: size the bet to survive the wave arriving two years late.

Playbook C — Proxy breaker. Attack the customer inertia that shields the incumbent. Make migration the product: importers, parallel-run modes, switching concierges, contract buyouts. Aim at moments when inertia naturally breaks — renewals, audits, platform deprecations, a champion changing jobs — and instrument them. Risk: switching subsidies attract deal-shoppers; qualify for fit, not just willingness to leave.

Notes for Defenders

If you are the incumbent: run the guideposts against yourself annually; diagnose which inertia you have before launching a "transformation" (the fixes are different and culture-stage fixes take years you must start now); weed entropy on a calendar, not when crisis forces it; and when a wave is real, judge your response by what it does to the attacker's economics, not by how well it protects this year's margin — the margin you are defending is often the door you are holding open.