Explore / Expand / Extract

Beck's company-lifecycle phase model — find what works, grow past bottlenecks, optimize margins — each phase demanding incompatible behaviors.

Also known as: 3X (Explore/Expand/Extract), 3X, explore / expand / extract (3 X's), explore/expand/extract

How authors use it

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

Documents (7)

• Reject Change, Sometimes Kent Beck · 2026-09-02 Reader 🖥️
  Because a growing product's payoff structure differs by 3X phase — roughly symmetric win/loss during Extract, sharply upside-skewed during Explore, and ruin-inclusive (win/die/switch) during Expand — the correct exposure to volatility differs sharply too: Extract calls for the disciplined, rebalancing 'Shannon's Demon' strategy of protecting revenue and keeping changes reversible even at some cost to upside (i.e., deliberately rejecting some change), Explore calls for going all in on volatility despite that same strategy's mathematical dominance in symmetric bets, and Expand calls for a third move — investing directly to reduce the probability of catastrophic failure — so 'embrace change' is not a universal software-development virtue but a phase-specific one.
• Canon 3X: Explore/Expand/Extract Kent Beck · 2026-07-30 source ↗ Reader 🖥️
  Because a growing idea passes through three phases — Explore, Expand, Extract — that each demand categorically different, even incompatible approaches to finance, team size, strategy, personnel, and risk, applying one phase's playbook to a project actually in a different phase kills the idea; managing a portfolio well means correctly matching each project's approach to its actual phase, and prioritizing Expand-phase work even above currently more profitable Extract activity.
• The Beginnings of an Idea: XP is Long Volatility Kent Beck from Software Design: Tidy First? · 2026-07-14 Reader 🖥️
  Beck's genuinely new ideas — including the just-arrived analogy 'XP is long volatility' — take years of unconscious incubation before they're ready to articulate, and once ripe they can only be sharpened into a teachable form by repeatedly explaining them badly, in varied ways, to real audiences, not by solitary polishing.
• Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) Kent Beck — Still Burning Podcast · 2026-05-20 Reader 🖥️
  We are not in another technology hype wave but in a step-function transformation: the marginal cost of producing software is collapsing toward zero, large incumbents are adopting AI faster than any prior shift, and the whole ecosystem — not just the AI labs — is accelerating; in this 'Red Queen' regime, profit and productivity may not visibly improve because every competitor is running at the new tempo, so the only sane response is to paddle straight into the wave by sustaining the maker's compulsion (the 'itchy brain'), reshaping engineering leadership toward hands-on impact, and accepting that software engineering as a profession will resemble medicine or law more than the unique 2010s template that minted six-figure undergrads.
• Starving Genies Kent Beck · 2026-04-03 source ↗ Reader 🖥️
  The simultaneous usage throttling by AI model providers is best understood not as an engineering constraint but as a narrative constraint: all three face the same investor-story shelf life, forcing synchronized demand-side rationing while the race to bend the supply curve up determines who wins the next wave.
• TBM 390: Governance by Principle, Not by Template John Cutler · 2025-11-23 source ↗ Reader 🖥️
  Governance should be built from first principles — context-specific risk management, accountability, evidence, and decision rights — rather than inherited from project/program templates and accounting-flavored false precision, because software investment is durable and dynamic rather than static and project-shaped; most organizations' governance is procedurally legitimate (defensible on paper) while failing the substantive test of actually serving investors, employees, and customers, and nothing in major governance frameworks (OECD, NIST, ISO 38500, etc.) actually requires projects or programs as the unit of governance.
• 90% of My Skills Are Now Worth $0 Kent Beck · 2023-04-19 source ↗ Reader 🖥️
  A technological revolution has just made roughly 90% of Beck's professional skills economically worthless by making their output free, while multiplying the leverage of the remaining ~10% (knowing what to ask for, and judging the result) by a thousand, so the only sane response is to recalibrate which skills to invest in by rapidly trying many things rather than reasoning it out in advance.

Propositions touching this concept (1)

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

2026-07

• implicitcorroboratedBeck's other major recent frameworks (3X: Explore/Expand/Extract, the 'Genie' metaphor for LLMs, Thinkies) all originated through the same slow-incubation-then-repeated-bad-explanation process he is now describing for 'XP is long volatility'.
  The Beginnings of an Idea: XP is Long Volatility · p7

Open gaps (19)

• incompleteThe post gives no account of how to actually identify, prospectively, which bucket a given skill falls into before investing further effort in it — the only proposed method is retrospective trial. This mirrors a diagnostic gap Beck's own later Explore/Expand/Extract framework has about phase-identification being retrospective-only.
  90% of My Skills Are Now Worth $0 — read next: See extract-canon-3x-explore-expand-extract-beck#g1, which notes the same structural gap (every exit/diagnostic criterion in 3X is recognizable only after the fact) — this 2023 post is arguably an early, personal instance of exactly that problem, applied to skills rather than products.
• alternative explanation not consideredRegulatory signaling is not discussed. Providers may be synchronizing on usage limits partly to demonstrate responsible scaling to regulators, not only to investors.
  Starving Genies — read next: Look at EU AI Act timeline and responsible scaling commitments from Anthropic, Google, OpenAI.
• evidence gapThe 'narrative shelf-life' explanation is offered through elimination rather than direct evidence. No investor statements, board dynamics, or financial data are cited.
  Starving Genies — read next: Cross-reference with investor communications, earnings calls, or insider reporting on AI funding dynamics.
• incompleteThe framework gives no prospective way to diagnose which phase a project is currently in. Every exit criterion offered is retrospective — Explore's exit is 'one experiment works way better than others,' Expand's is 'cause and effect of growth become predictable,' Extract's is 'no further return on investment' — each recognizable only after the transition has already happened. Since Beck's highest-stakes claim is that applying the wrong-phase approach kills ideas, and phase identification is the one capability that claim depends on, the piece asserts the stakes of misdiagnosis while leaving diagnosis itself unaddressed.
  Canon 3X: Explore/Expand/Extract — read next: Read against lean-startup / product-discovery literature on leading indicators of product-market fit, which attempts exactly this real-time diagnosis problem; also reread Explore's own tactic ('quickly discard failures') for whether Explore's fast-failure discipline is itself an implicit workaround for the missing diagnostic — i.e., you don't diagnose the phase, you make Explore cheap enough that misdiagnosis is affordable.
• illogicalThe Canon series promises to explain ideas 'no analogies, no persuasion, just the facts,' yet the load-bearing explanatory device of this very essay — the S-curve as a tug-of-war between two feedback loops — is an analogy, self-flagged mid-sentence ('oops, analogy, sorry'). The piece doesn't reconcile this with its stated method or revise the promise, leaving open whether an abstract systems concept like a feedback loop can be explained non-analogically at all, or whether 'no analogies' is a rhetorical framing device rather than a constraint the writing actually follows.
  Canon 3X: Explore/Expand/Extract — read next: Compare with Canon TDD (the first entry in the series, referenced but not read here) to see whether it holds the no-analogy constraint more successfully, or whether the constraint reliably breaks down whenever Beck needs to explain a systems-level abstraction rather than a concrete practice.
• incompleteBeck names the practical failure mode of portfolio management ("prioritize Expand even over profitable Extract ... simple to say and apparently nearly impossible to execute") but doesn't explain the mechanism behind the difficulty — is it incentive misalignment (Extract's returns are more legible and immediately rewarded), organizational structure (separate teams/budgets per phase competing for the same pool), or plain risk aversion? The failure is asserted, not analyzed.
  Canon 3X: Explore/Expand/Extract — read next: Cross-reference extract-tbm-430-incubate-compound-refinance-liquidate for a more developed treatment of portfolio-allocation mechanics across investment-lifecycle stages, and organizational-behavior literature on why legible short-term metrics crowd out illegible but longer-term-critical investment.
• incompleteThe essay never specifies how a team is supposed to determine, for any actual proposed change, which of the three payoff regimes (Extract's symmetric flip, Explore's skewed flip, or Expand's win/die/switch) applies — the entire prescriptive value of the framework depends on this classification step, which is left as an exercise.
  Reject Change, Sometimes — read next: Watch for a follow-up Beck post operationalizing the classification (a checklist, heuristic, or worked real-world case); or pressure-test the framework against a real proposed change in your own team's Extract-phase product to see whether 'which regime is this?' has an obvious answer in practice.
• incompleteExpand's strategy ('invest to reduce probability of death, or increase probability of clearing the bottleneck') is asserted without the same numeric/simulated grounding given to Extract and Explore — no payoff numbers, no simulator branch, no worked example of the tradeoff between the two sub-strategies.
  Reject Change, Sometimes — read next: Watch for Beck extending the Appendix simulator to model a three-outcome (win/die/switch) game, which would let the Expand claim be tested the same way the Extract/Explore claims already are.
• uninformedBeck imports the volatility/rebalancing framing directly from Kunal Bhalla ('pointed out the exception... introduced me to... Shannon's Demon') but gives no independent check that the coin-flipper model captures the actual statistical structure of real product changes, versus being an elegant trading analogy that happens to sound applicable.
  Reject Change, Sometimes — read next: Look into the empirical distribution of 'did this change help or hurt' outcomes for real product changes (e.g. from experimentation/A-B-testing literature) to see whether they're closer to symmetric, skewed, or something else entirely — and whether that distribution actually differs by company stage the way Beck assumes.
• incompleteThis essay finally explains the 'long volatility' claim that an earlier post in this series ('The Beginnings of an Idea: XP is Long Volatility') left undefined — but it delivers the general 3X (Explore/Expand/Extract) framing, not XP specifically; it never closes the loop back to concrete XP practices (pairing, TDD, continuous integration, spikes) as instances of 'short' or 'long' volatility bets the way the original teaser promised.
  Reject Change, Sometimes — read next: Watch for Beck to explicitly re-connect this volatility/Shannon's-Demon framework to specific XP practices (is TDD a 'rebalancing' practice? is a spike a 'Reckless' Explore bet?) to fully deliver on the original 'XP is long volatility' framing.
• incompleteVendor incentive distortion in the 'whole ecosystem is accelerating' claim
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: DORA 2025 and the Stanford/Microsoft developer-productivity studies on AI's actual code-quality effects; Gergely Orosz on enterprise sales-cycle compression; Marc Andreessen's classic 'why software is eating the world' for the prior pattern. For the contrarian counterweight: Gary Marcus and Ed Zitron on whether the AI productivity story is being narrated by the people selling it.
• incompleteThe marginal-cost claim is accounting-incomplete (Beck flags it; Grinich doesn't return)
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Anything in your Kent Beck file on TCR and scope-of-done (this is exactly the conversation about plausible deniability and shrinking scope); Lorin Hochstein on operational complexity; the Böckeler harness-engineering extraction in this repo (the 'gap between running system and trusted system' is the harness-engineering surface). The Adam Tooze / Brad DeLong line on 'productivity gains that don't show up in the statistics' is the macroeconomic complement.
• incompleteThe 'descaling of software' counter-trend is named by Beck and left hanging
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Steve Yegge on vibe coding; Gene Kim's vibe coding series; Simon Willison on the 'no-coder using LLMs to build real software' phenomenon; the Schoening agency-over-skills extraction in this repo (the agency thesis is the descaling-friendly side of this tug of war). Honest framing: Beck's craft instincts and Grinich's institutional instincts pull in opposite directions; you may have to choose.
• incompleteGrinich's 'industrialization phase' analogy launders externalities
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Tooze on energy transitions; the IEA's compute-electricity projections; the literature on whether the late-19th-century industrialization actually 'cleaned up' or just exported externalities. For Kjetil specifically: this is the systems-thinking lens — feedback loops, stocks/flows, who absorbs what — applied to the rhetoric of inevitability.
• incompleteWhat changes about Beck specifically — the craft thinker in this regime
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Beck's own recent Substack posts (Tidy First, the 'starving genies' piece, 'forest thinning'); your highlights on Beck for where he reframes craft for the agentic era; Hickey's 'Simple Made Easy' as the substrate craft argument; Ousterhout's complexity work. The persona-relevant cross-thread: this is where Kjetil's 'fragility of ideas' hidden layer touches the AI transition — if the craft of attentive code-reading is the protected attention surface, what protects it now?
• incompleteWhat does the 'itchy brain' protect against, exactly?
  Itchy Brain (Still Burning: Michael Grinich & Kent Beck on AI adoption, enterprise developer tools) — read next: Pressfield on Resistance; Cal Newport on deep work degradation under tool proliferation; the David Whyte/Maria Popova line on the difference between making and consuming; the persona's Bailey/Hyperfocus annotations on what attention needs in order to do anything. This is where the persona's hidden layer (fragility of ideas) and the episode's title concept (itchy brain) collide — and it is the most productive question the episode opens.
• incompleteCutler opens by conceding this is 'absolutely not a new idea' (software as a portfolio of assets/investments/bets/liabilities) but never names or differentiates from the obvious antecedents his own framing invites comparison to -- most directly the BCG growth-share matrix (Question Marks/Stars/Cash Cows/Dogs maps closely onto Incubate/Compound/.../Liquidate) and Kent Beck's Explore/Expand/Extract company-lifecycle model already in this corpus. The self-effacing 'none of the underlying ideas are especially new' reads as honest but is never cashed out into an actual comparison of what, if anything, the carrying-cost axis adds.
  TBM 430: Incubate, Compound, Refinance, Liquidate — read next: The explore-expand-extract concept (Beck's 3X) already in this corpus for a direct lifecycle-model comparison; BCG growth-share matrix literature for the portfolio-management antecedent.
• incompleteThe 'long-baked ideas' theory of how his frameworks originate is offered purely as autobiographical pattern-matching across Beck's own past examples (3X, Genie, Thinkies), with no engagement with the existing psychology-of-creativity literature on incubation.
  The Beginnings of an Idea: XP is Long Volatility — read next: Graham Wallas's four-stage model of creativity (preparation, incubation, illumination, verification, from The Art of Thought, 1926); empirical work on incubation effects in problem-solving (e.g. Sio & Ormerod's meta-analysis on incubation and insight).
• uninformedBeck doesn't say who originated the 'XP is long volatility' framing he 'heard... yesterday' — whether it's his own restated insight, a collaborator's phrase, or something from the broader trading/software crossover community. Without attribution, readers can't independently trace or evaluate the idea's source before Beck's own treatment arrives.
  The Beginnings of an Idea: XP is Long Volatility — read next: No source available yet; would require Beck's future post or direct correspondence to resolve.