Technology Diffusion & Transformation Curves

How transformations actually land: slow compounding flywheels, high-friction liminal phases, decades-long diffusion — against the instant-revolution narrative.

Also known as: svinghjul / svinghjuleffekt (flywheel / flywheel effect), svinghjul, flywheel, flywheel effect, S-kurve (S-curve), S-curve, liminalfase (liminal phase), liminal phase, traktor-analogien (the tractor analogy), tractor analogy, co-evolution of practice, produktivitetsvekst (productivity growth), fra opposisjon til posisjon (from opposition to position), industrial revolution, industriell revolusjon

Skill Infrastructure (Ding)

How authors use it

Oldest first (extraction date when no publication date is known).

AuthorTheir termTheir meaning
Simon Wardley's Post — Industrialisation of ML: nine notes on what to expect
Simon Wardley · 2025-12
co-evolution of practiceWhen a technology industrialises, the surrounding doctrine, tooling, metrics, and professional practices lag and then converge over a typical 5-8 year window. This is a Wardley climatic pattern, not a guess.
Kunstig intelligens gir neppe en ny, industriell revolusjon
Tobias Lunde · 2026-04-10
industriell revolusjon (Industrial Revolution)Not merely the invention of steam power, but a sustained increase in the rate of change in economy and society, beginning in 17th-century Britain — driven by a confluence of factors, not technology alone.
Kunstig intelligens gir neppe en ny, industriell revolusjon
Tobias Lunde · 2026-04-10
produktivitetsvekst (productivity growth)Measurable increases in economic output per unit of input — the metric by which technology's economic impact should be judged.
17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis
Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18
svinghjul / svinghjuleffekt (flywheel / flywheel effect)Slow-building organisational momentum where many capability investments compound silently and then deliver disproportionate returns when an event arrives. Used twice: about NAV's IT capability before COVID, and about transformations more generally — 'energetic processes that happen slowly first, then fast'.
17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis
Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18
liminalfase (liminal phase)The transitional phase between two paradigms — after the old rules are abandoned and before the new ones are established. Characterised by friction, higher risk, and the need to let some old structures go before the new can settle. Jonas attributes the term to social anthropologists he worked with at NAV. He applies it both to NAV's transformation and to the current AI moment 'on almost all fronts'.
17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis
Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18
S-kurve (S-curve)The adoption/diffusion curve — slow start, steep middle, plateau — invoked to argue that many simultaneous S-curves were rising during the NAV transformation (deploy frequency, share of developers, team formation) and that AI in mid-2026 is still 'very early on the curve'. Distinct from a 'kumulativ' curve.
17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis
Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18
fra opposisjon til posisjon (from opposition to position)The transition phase in transformation when the change agents stop fighting and become the institution that invites others in. 'Fighting' stops working past a certain point; one must occupy the structures and meet people where they are.
17) Jonas Slørdahl Skjærpe om svinghjuleffekter, liminalfaser og kunsten å ta heis
Truls Jørgensen og Audun Fauchald Strand — Heis Podcast · 2026-05-18
traktor-analogien (the tractor analogy)Tractors arrived in the US around 1900 but did not displace horses until the 1950s because the product was immature, skills were scarce, and farms were too small to justify capital-intensive operation. Jonas uses this to argue that AI's real impact will unfold over decades of restructuring, not in a couple of years.
The Org Age of AI: A Collection of Enterprise AI Adoption Guides
Turing Post · 2026-07-04
flywheelA closed-loop workflow in which AI generates its own work, tests it, and refines it without a human checking every step — a further automation layer built on top of an already-redesigned workflow
Are We Entering a New Age of Creativity with the Help of AI?
Harvard Business Review · 2026-07-07
S-curveA strategy-playbook metaphor for the adoption/maturity trajectory of a technology or business model; 'getting on the next S-curve' means proactively adopting the next disruptive wave rather than being disrupted by it, as Kodak and BlackBerry failed to do.

Documents (16)

Propositions touching this concept (11)

By publication month, oldest first (extraction month when no publication date is known).

2025-12

2026-04

2026-05

2026-06

2026-07

2026-08

2026-09

Tensions

Is code a durable artifact humans must keep reading, or an ephemeral byproduct regenerated from a spec?
from: What did the participants of the Thoughtworks 'Future of Software Engineering' Europe retreat (mid-2026) conclude about how agentic AI is reshaping software engineering?
Assessment: The retreat's own 'largest divide' (Ördög). It is unresolved inside the room and inside the individual essays: Herlein concedes the deterministic 'code is the better spec' counter is 'hard to wave off', and Ördög reports being ironically pulled toward the dark-factory camp by her own good-code practices. The crux is whether a fuzzy prose spec can ever be the durable source of truth when the stated quality bar is verifiability — a tension none of them resolves.
Reversibility as a hedge vs a one-way commitment to deeper autonomy.
from: What did the participants of the Thoughtworks 'Future of Software Engineering' Europe retreat (mid-2026) conclude about how agentic AI is reshaping software engineering?
Assessment: Incompatible risk models. Verraes treats deep AI-dependence as the danger to insure against; Herlein treats not-committing as the existential danger. They cannot both be the rational strategy: reversibility trades some upside for exit options, while flywheel-commitment trades exit options for compounding lead. The tie-breaker is empirical (will access/economics deteriorate?) and neither has evidence — Fowler's 'tokenpocalypse' data leans slightly toward Verraes.
If code is no longer the bottleneck, what is the new binding constraint?
from: What did the participants of the Thoughtworks 'Future of Software Engineering' Europe retreat (mid-2026) conclude about how agentic AI is reshaping software engineering?
Assessment: They agree code/delivery has ceased to be the constraint but name three different successors, with different investment implications — expand decision-making capacity (Vella), optimise for learning (Edwards-Alexander), or capture tacit knowledge (Herlein). These are complementary in principle but rivalrous for attention and budget; the disagreement matters because each implies a different 'first thing to fix.'
Is code a durable artifact to be maintained, or an ephemeral byproduct regenerated from a more durable source (spec/objective)?
from: What is the future of software development in the agentic/AI age?
Assessment: The most-cited open question of the corpus, and genuinely unresolved (Herlein: 'no consensus here. None.'). The 'code is the better spec' counter is strong — code is unambiguous, executable, deterministic, whereas a prose spec is reinterpreted each run, which sits in tension with verifiability being the quality bar. Ruby's move is the most defensible: it dissolves the code-vs-spec fight by locating durability in the evaluation rather than any representation. Verraes and Ördög expose the load-bearing empirical unknown — nobody has data on regenerate-vs-patch cost or on long-term evolvability of agent-maintained code.
Strategically, is the right move to accelerate adoption to build a permanent lead, or to decelerate and hedge against AI's risks?
from: What is the future of software development in the agentic/AI age?
Assessment: Nearly opposite bets: Herlein optimizes for a world where AI keeps getting cheaper and better and first-movers win permanently; Verraes and Fowler optimize for a world where AI gets costlier, curtailed, or unreliable. Herlein's 'permanent moat' rests on flywheel logic plus a single secondhand anecdote and ignores technology-diffusion catch-up dynamics; Verraes and Fowler's hedge is cheap insurance but under-examines whether reversion is actually achievable once specs, agents, and toolchains are deeply embedded and human familiarity has eroded. The disagreement is ultimately a bet on the trajectory of token economics, which nobody in the corpus can price.
Is preserving human understanding of the system a first-order value, or is comprehension safely offloadable so long as output is verifiable?
from: What is the future of software development in the agentic/AI age?
Assessment: The optimist-practitioner vs. skeptic-humanist axis. Fowler and Nilsson treat comprehension and craft as intrinsic goods whose loss is a harm even when output is fine; Herlein and Ocytko treat comprehension as instrumental — replaceable by verification and platform guardrails. The humanist camp has the stronger long-run argument (Fowler's cognitive-debt case and Ocytko's own 'who-guards-the-guards' problem both show verification and guardrails are themselves fallible artifacts that someone must understand), but the offloadable camp is describing what is actually happening at scale. The crux is whether verifiability can ever be robust enough to make understanding optional — which Ruby's own Goodhart gap (a passable oracle diverging from true intent) suggests it cannot fully be.
If code was never the bottleneck, what is the binding constraint now?
from: What is the future of software development in the agentic/AI age?
Assessment: A productive three-way split downstream of the shared 'code was never the bottleneck' finding. They are not incompatible so much as differently located — decision capacity (Vella) is organisational, learning (Edwards-Alexander) is about the team's rate of understanding the problem, and knowledge (Herlein) is about capturing rationale. But they imply different investments: expand downstream absorption, restructure around learning, or build knowledge-capture pipelines. The corpus has not reconciled which is the true binding constraint, and each author generalizes from a different vantage (a retreat-floor convergence, an org-design frame, a knowledge-engineering frame).

Open gaps (28)