Zombie Companies  🔗 **Source:** [Zombie Companies](https://www.jonoalderson.com/conjecture/zombie-companies/) > [!note]+ Document Notes > tags: [business-strategy, corporate-decline, disruption-theory, incumbency, ai-disruption] > author: Jono Alderson > source: jonoalderson.com (Conjecture) > reference: https://www.jonoalderson.com/conjecture/zombie-companies/ > date created: {{date:YYYY-MM-DD}} {{time:HH:mm}} > > # 🏷️ Title: Zombie Companies > <!-- deep-read:sections start --> ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - [The middle is a graveyard](https://www.jonoalderson.com/conjecture/the-middle-is-a-graveyard/) - [When scrutiny becomes cheap](https://www.jonoalderson.com/conjecture/when-scrutiny-becomes-cheap/) - [Marketing after the fog clears](https://www.jonoalderson.com/conjecture/marketing-after-the-fog-clears/) - [The inversion of purpose](https://www.jonoalderson.com/conjecture/the-inversion-of-purpose/) - [Clicks don't count](https://www.jonoalderson.com/conjecture/clicks-dont-count/) ## 📝 Summary - Alderson argues that companies can fail strategically years before the failure shows up financially, because the metrics everyone trusts — revenue, margin, retention, market share — measure the residue of past success rather than the organization's current capacity to build its own future. - A "zombie company" is defined precisely: current performance depends on advantages built under earlier conditions, demand is moving elsewhere, and the organization cannot follow without damaging the business it's currently rewarded for protecting. All three conditions must hold; absent one of them, it's just maturity or ordinary decline. - The mechanism that hides this: incumbents mistake "momentum" (weight and velocity from past success) for a "moat" (an advantage still actively reinforcing itself). Momentum produces the same outward numbers as a moat for years, which lets leadership misread delay as resilience. - Symptoms include defending revenue through price increases and harder-to-cancel bundles, performing change via reorganizations that alter the org chart but not the underlying commercial logic, misjudging challengers by comparing today's feature set instead of the challenger's trajectory, and quietly losing the low-value/entry-level users who determine what the market expects next. - The reason incumbents can't just "adapt faster": meaningful change requires choosing against something that already works, and every internal function — finance, sales, product, legal — rationally protects its own piece of the current model, so change gets approved in principle and prevented in practice. - Two forces are shortening the runway zombie companies used to have: falling costs of building competitive alternatives (rented infrastructure, cloud, open source), which lets challengers take a single profitable slice instead of replicating the whole business; and AI, which makes it cheaper to scrutinize a company, compare it to alternatives, and act on dissatisfaction — compressing the gap between strategic decay and market recognition. - Stakeholders: incumbent leadership and boards (whose incentives reward defending the present), challengers and smaller competitors (who benefit from cheaper infrastructure and AI-assisted discovery), customers (whose migration friction is falling), and employees/executives whose status is tied to the legacy model. - Risk/tradeoff: the framework is diagnostic, not prescriptive — it explains why zombie companies exist and why they're hard to fix, but offers only a thin closing gesture toward what "converting reserves into capability" would actually require operationally. - Bottom line: the numbers aren't lying, they're just looking backwards — and by the time they show the difference between a living company and a zombie one, the difference will already have been true for years. ## 📖 Main Content Alderson's central move is to separate what a company *has* from what it can still *do*. Revenue, brand, distribution, contracts, and institutional knowledge are treated by most organizations as proof of ongoing strength. Alderson reframes them as "lagging indicators" — evidence of what the company already built, not evidence that it can still build. A company can therefore be historically successful and strategically dead at the same time, because current financial performance is often "historical success arriving late": the market rewarding decisions made years or decades earlier while the underlying capability to earn that position again has quietly eroded. The piece formalizes "zombie" status with three simultaneous conditions: (1) current performance leans heavily on advantages accumulated under earlier conditions, (2) the sources of future demand are moving elsewhere, and (3) the organization cannot follow without damaging the business it is currently rewarded for protecting. This is a meaningfully narrower claim than "big companies get complacent" — it excludes ordinary maturity, deliberate harvesting of a mature product, or rational shrinkage, all of which can look similar from outside but lack the third condition (structural inability to move). A key analytical distinction is **moat vs. momentum**. Both produce continued sales and stable market share, and both look identical on a quarterly dashboard. But a moat is an advantage that keeps reinforcing itself (better data improves the product, scale lowers costs, trust deepens through delivery); momentum is just accumulated weight and velocity that continues to move even as the underlying forces weaken (brand still opens doors, but less reliably; customers still renew, but with more resentment). The practical danger is that leadership, looking at identical top-line numbers, calls momentum "resilience" when it's actually "latency" — a delay before consequences arrive, not evidence that adaptation was unnecessary. Four symptom clusters follow from this: organizations that (a) protect the *evidence* of success rather than the *soil* that produces it (price rises, harder cancellation, bundling); (b) perform change through reorganization — new org charts, transformation programs, centres of excellence — that redistribute authority without altering what the company is *for*; (c) defend the old market by comparing challengers against the mature incumbent's own standards rather than recognizing the challenger may be building for a different version of the market entirely; and (d) lose the future while retaining the present, because the customers who determine what the market will expect next (students, small businesses, junior employees, creators) are also the customers who look commercially insignificant today. The essay then explains *why* incumbents can't simply execute the obvious advice ("adapt faster, invest in innovation, add AI"). Meaningful adaptation requires choosing against something that already works — a division loses revenue, an executive loses authority, a team loses headcount — and every corporate function has a rational, self-protective reason to slow that down. Nobody has to reject the future outright; they only need to keep asking sensible questions until it arrives too late. Innovation gets "domesticated" into peripheral experiments (a small team allowed to explore, provided it doesn't disturb the core business) that are set up to fail in ways that reinforce the old model rather than threaten it. The second half pivots to why this pattern is becoming more dangerous *now*. Historically, incumbency bought time because building a credible competitor required capital, infrastructure, specialist expertise, and trust that took years to assemble. That cost is falling: cloud infrastructure, open-source software, rentable distribution, and global talent markets mean a challenger can take one profitable workflow or one underserved segment without reproducing the incumbent's full institutional mass. This produces "hollowing out" — a company's average revenue per customer can *rise* even as its long-term customer pipeline evaporates, because it's retreating toward its most defensible, most profitable core while losing the edges where future demand is forming. The category isn't conquered by a single rival; it's disassembled by several narrow ones. Alderson uses Photoshop/Adobe as an illustration (explicitly framed as a thought experiment, not a prediction) of how a company can keep winning within its category while the category itself shrinks in relevance, as Canva, mobile tools, and generative systems remove the *reasons* people become professional-tool users in the first place. Finally, AI is framed not primarily as a production tool (write faster, automate support) but as a force that shortens how long strategic failure can hide, because it makes scrutiny, comparison, and migration cheaper — attacking the specific mechanism (expensive due diligence) that let brand recognition function as a trust shortcut. The essay closes on "dashboards inherit the assumptions" (measurement systems are built by the same organization whose blind spots they're supposed to reveal) and "the accounting lag" (financial failure is a lagging, not leading, signal of strategic failure that already happened). ### 🗒️ Notes - Central reframe: revenue/margin/retention/market-share are outputs of *accumulated* advantage, not evidence of *current* capability to reproduce that advantage — "current success is often historical success arriving late." - Zombie definition requires all three conditions at once (dependency on past advantage + demand moving elsewhere + structural inability to follow) — this is the load-bearing definitional claim of the whole piece; without it, "zombie" collapses into vague decline-talk. - Moat vs. momentum is the diagnostic tool readers can actually apply: ask whether the mechanism producing the advantage is still *active* (moat) or just *inherited weight* (momentum). Both look identical in a quarterly report. - "A resilient incumbent uses brand, capital, distribution and expertise to widen the range of futures available to it. A zombie uses those advantages defensively" — this is the cleanest operational test in the piece for distinguishing healthy incumbency from zombie status. - Political-economy explanation for stuck-ness: adaptation requires someone to lose (a division, an executive, a team), and every function (finance, sales, product, legal, board) behaves rationally to protect itself — collectively producing an organization that agrees change is necessary while preventing it in practice. This is essentially an agency-problem/local-optimization argument, not a claim about individual incompetence or bad faith. - "Innovation theatre" pattern: small ring-fenced innovation teams are permitted to explore but denied the resourcing, governance exemptions, or authority to threaten the core — so when they underperform, the org draws the wrong lesson ("the market wasn't ready") instead of the right one (the experiment was structurally set up to fail). - Falling cost of challenging incumbents ties to real economic infrastructure changes (cloud rental, open source, platform distribution, outsourced specialist functions) — this is the most falsifiable/empirical claim in the essay and the easiest to test against actual market data (see Hypotheses/Methodology below). - "Hollowing out" mechanic: retreating to the most profitable core customers can make quarterly numbers *improve* (higher average revenue per customer, better margins, higher market share among remaining competitors) while the replenishment pipeline for future customers quietly disappears — this is the piece's sharpest counter-intuitive insight, because it means the standard KPIs used to reassure a board are exactly the metrics that get better as the company hollows out. - Photoshop/Adobe example is explicitly hedged as illustration, not forecast — worth flagging for readers who might otherwise treat it as a claim about Adobe's actual trajectory. - AI's role is reframed from "production tool" (internal automation, headcount reduction) to "scrutiny accelerant" (external — makes it cheaper for buyers to investigate, compare, and migrate away from an incumbent). This inverts the dominant corporate-AI narrative Alderson explicitly criticizes at the start of that section. - "Dashboards inherit the assumptions": a subscription business measures subscriptions well; it's structurally poor at measuring the possibility that subscriptions are the wrong lens entirely. Ties to the referenced companion piece "Clicks don't count." - Closing formulation is the piece's thesis in miniature: "The numbers are not lying; they are simply looking backwards" — recurs almost verbatim at both the start and the end of the essay, functioning as a frame device. - Notable absence: no discussion of what a *successful* de-zombification looks like in practice (case study of a company that recognized the pattern and escaped it) — the essay is diagnostic throughout, prescriptive only in the abstract ("advantages only remain alive when converted into new capability"). ## 📚 References - [The middle is a graveyard](https://www.jonoalderson.com/conjecture/the-middle-is-a-graveyard/) — Alderson's companion piece on how better comparison weakens the value of "acceptable" mid-market breadth, cited re: challengers training expectations before they win revenue. - [When scrutiny becomes cheap](https://www.jonoalderson.com/conjecture/when-scrutiny-becomes-cheap/) — cited re: AI lowering the cost of investigating a company, undermining brand-as-shortcut. - [Marketing after the fog clears](https://www.jonoalderson.com/conjecture/marketing-after-the-fog-clears/) — cited re: cheaper comparison exposing trade-offs marketing used to soften. - [The inversion of purpose](https://www.jonoalderson.com/conjecture/the-inversion-of-purpose/) — cited re: AI assistants sitting between intention and action, creating an evaluation surface incumbents don't control. - [Clicks don't count](https://www.jonoalderson.com/conjecture/clicks-dont-count/) — cited re: dashboards describing the interface rather than underlying competitiveness. ## 🗣️ Paraphrase - Companies can look financially healthy for years after they've actually lost the ability to build their own future, because the metrics everyone trusts — sales, renewals, market share — describe what the company already built rather than whether it can still build anything new; that gap between accumulated advantage and current capability is where "zombie" status lives, and it only counts as zombie status when the company is also structurally unable to chase the market's next move without wrecking the business it depends on today. - The reason this is hard to fix isn't stupidity or neglect — it's that every part of a large organization has a locally rational reason to protect what already works (finance protects margin, sales protects closable deals, product protects existing customers), so the company can sincerely agree that change is necessary while every function quietly prevents it, and meanwhile falling infrastructure costs let smaller challengers take one profitable slice of the business instead of rebuilding the whole thing, while AI makes it cheaper for customers to notice, compare, and actually leave — shrinking the amount of time a zombie company has left before the numbers catch up to a decision that was effectively made years earlier. ## 📰 Newsletter Jono Alderson's latest Conjecture piece, "Zombie Companies," is worth a slow read if you've ever sat in a strategy meeting where the numbers looked fine and something still felt off. His core distinction — a moat that's still actively reinforcing itself versus momentum that's just coasting on inherited weight — gives you a genuinely useful diagnostic for your own roadmap reviews, not just a metaphor. The section on why "adapt faster" advice fails in practice (every function in the org has a rational reason to protect its own piece of the status quo) is a sharp explanation of a dynamic a lot of product and platform teams recognize but rarely name out loud. Also useful: his reframe of AI's business impact away from "internal production tool" and toward "external scrutiny accelerant" — it changes how you might think about documentation, transparency, and migration tooling as competitive surface area, not just support cost. Recommended alongside his earlier pieces "The middle is a graveyard" and "When scrutiny becomes cheap," which this one builds directly on. ## ✅ Action Items **General strategic/leadership actions derived from this article** (the article addresses corporate strategy broadly, not a specific developer-relations, OSPO, or WordPress-ecosystem context, so those canned subteams below are marked not applicable): - Audit whether current KPIs (retention, ARPU, margin) could mathematically *improve* while the customer-replenishment pipeline shrinks — build a "hollowing out" check that separates revenue quality from revenue quantity. - Distinguish moat metrics (mechanism still actively reinforcing itself) from momentum metrics (inherited weight) for each major product line; report both separately to the board rather than blended. - Track entry-level/low-value/non-revenue-generating user segments explicitly, since the article argues these determine future category norms even though they look insignificant today. - Give at least one innovation initiative real authority to cannibalize an existing revenue line, rather than ring-fencing it under legacy governance and calling the resulting failure "proof the market wasn't ready." #### DevRel - Not applicable to this source — the article addresses general corporate strategy and market dynamics, not developer advocacy, education, or developer-experience tooling. #### OSPO - Not applicable to this source — no open-source governance, licensing, or software-inventory content is discussed. #### Community - Not applicable to this source — the article discusses customers, competitors, and markets in the abstract; it does not address maintainer, contributor, or sponsor community operations. #### WordPress - Not applicable to this source — the article contains no WordPress-specific content (core, plugins, themes, hosting, or community programs). #### The WPCC - Not applicable to this source — no WordPress Community Collective programs, projects, or funding mechanisms are discussed. ### FAIR - Not applicable to this source — no FAIR federation, provenance, or governance-artifact content is discussed. ## 🧪 Hypotheses - H1: Companies that increase reorganization frequency without a corresponding change in product mix or margin structure show higher subsequent revenue decline than companies that hold org structure constant while changing product mix. - H2: A sustained decline in a company's lowest-revenue/entry-level customer segment predicts category-level revenue decline for that company within 3–5 years, even while enterprise/core-account revenue holds steady. - H3: Companies whose innovation initiatives are legally/organizationally ring-fenced from core-business cannibalization show lower conversion of pilot projects into durable revenue lines than companies that permit internal cannibalization. - H4: The rate of price increases and subscription/cancellation-friction changes correlates with the age of a company's core product line, independent of stated growth strategy — i.e., pricing/friction levers are used more as products mature, regardless of whether leadership frames it as "premiumization." - H5: Wider availability of AI-assisted product-comparison and migration tooling correlates with faster churn specifically among "momentum" incumbents (per the moat/momentum distinction) relative to genuine "moat" incumbents in the same category. ### 📊 Methodology - For H1/H4: longitudinal analysis of public company 10-K/annual-report disclosures (reorg announcements, price changes, bundling/cancellation-policy changes) cross-referenced against subsequent 3–5 year revenue and customer-count trends; requires a coded dataset of reorg events and pricing events per company-year. - For H2: cohort-level customer segmentation data (ideally from company-provided investor disclosures or third-party subscription-analytics panels) tracking entry-level/free/low-ARPU segment size over time against total company revenue in the same window, lagged 3–5 years. - For H3: comparative case studies of internal innovation units (e.g., "labs," "incubators," acquired-startup integrations) coded for governance independence (separate P&L, separate hiring, exemption from core KPIs) against whether the initiative was later absorbed into core revenue, spun out successfully, or quietly discontinued. - For H5: natural experiment using the staggered rollout of AI-assisted comparison/review tools (browser extensions, AI shopping/procurement assistants) across categories, measuring churn-rate change pre/post rollout for companies independently classified (via analyst or survey panel) as "moat" vs. "momentum" businesses. ### ❓ Questions - How would an outside analyst operationally distinguish "moat" from "momentum" using only public data, without access to the internal political dynamics Alderson describes? - Is there a minimum viable governance change (e.g., "innovation unit reports directly to CEO with authority to cannibalize") that reliably converts pilots into core revenue, or is the political-economy problem too structural for any single governance fix? - Does AI-driven scrutiny actually compress the zombie-company runway measurably yet, or is this still a forward-looking claim without observable data behind it? - Which of today's large incumbents would satisfy all three of Alderson's zombie conditions simultaneously, versus merely one or two (i.e., which are actually maturing/harvesting rationally rather than dying)? - What early internal signal (not visible in external dashboards) would most reliably indicate a company has crossed into zombie status, before the accounting lag catches up? ### 🔮 Future Research - Build a public, ongoing "moat vs. momentum" scoring methodology for major incumbents using disclosed segment data, to test the framework against real outcomes over the next 5–10 years. - Study whether AI-assisted procurement/comparison tools are already measurably shortening incumbent runway in any specific B2B software category, as a leading test of the essay's central AI claim. - Research organizational structures (holding-company models, dual-class innovation units, spin-out incentive structures) that have historically succeeded at permitting internal cannibalization, to move the essay's diagnosis toward a tested prescription. ### 💡 Implications - For practice: strategy and product leaders should treat "which of our KPIs would improve as we hollow out" as a standing board-level question, not an occasional audit. - For policy: if AI-driven scrutiny genuinely shortens incumbents' adaptation runway, competition regulators may need to reconsider how much protective delay large incumbents can still expect versus how quickly markets self-correct. - For security: none directly implicated by this source (no security content) — noted here only because the template section is generic; see Learning Styles/Accessibility below for content-specific assessments instead. - For education: the moat/momentum distinction and the three-condition zombie test are teachable frameworks that could be incorporated into MBA-level strategy curricula as a diagnostic exercise against real case studies. - For funding models: venture and PE investors evaluating incumbents for turnaround plays could use the three-condition test as an explicit due-diligence checklist rather than relying on standard financial-multiple screens alone. ### 🧠 Learning Styles Assessment - Reading level estimate: approximately Flesch-Kincaid grade 15–16 (college/graduate level), Flesch Reading Ease roughly 25–35 ("difficult"), estimated manually from consistently long compound-complex sentences (frequently 25–35 words), heavy use of abstract business/strategy vocabulary (e.g., "lagging indicator," "cannibalization," "unbundling," "hollowing out"), and minimal concrete narrative grounding until the Photoshop/Adobe illustration roughly two-thirds through the piece. #### 👀 Visual learners - Present: none — the article is pure prose with no diagrams, charts, screenshots, or labeled visuals of any kind. - Improve: a simple two-axis diagram (moat-strength vs. momentum-strength) plotting example companies would make the central distinction immediately graspable; a timeline diagram showing "strategic failure point" vs. "accounting recognition point" would visualize the core accounting-lag argument. #### 🔊 Aural learners - Present: none — no audio version, podcast, or narration is provided on the page. - Improve: a 3–5 minute audio summary or TTS version would suit this content well, since the argument builds cumulatively and could be narrated as a single throughline. #### 🗣️ Verbal learners - Present: strong — Alderson defines terms carefully (e.g., the explicit three-condition zombie test, the moat/momentum distinction) and uses extended analogy (Photoshop/Adobe) to ground abstract claims. - Improve: a short glossary box (zombie company, moat, momentum, hollowing out, unbundling) at the top would help readers unfamiliar with the essay's recurring vocabulary track definitions across the piece's ~5,000-word length. #### 🧩 Kinesthetic learners - Present: none — no exercises, checklists, or interactive self-assessment tools. - Improve: a short "run this test on your own company" checklist walking through the three zombie conditions and the moat/momentum distinction would convert the framework into a usable diagnostic exercise. #### 🧠 Logical learners - Present: strong — the three-condition definition, the moat/momentum dichotomy, and the "hollowing out" causal chain are all presented as structured, near-syllogistic arguments. - Improve: a decision-tree or flowchart formalizing the three-condition test (with explicit yes/no branches) would make the logical structure even more directly usable. #### 🧑‍🤝‍🧑 Social learners - Present: none — no discussion prompts, forums, or collaborative exercises. - Improve: discussion questions (e.g., "name a company in your industry that fits all three conditions — defend your answer") would suit a book-club or leadership-offsite format. #### 🧘‍♀️ Solitary learners - Present: moderate — the essay's cumulative, meditative structure rewards slow individual reading and re-reading. - Improve: a set of self-reflection prompts (e.g., "which KPI in your organization would improve fastest during hollowing out?") would extend the solitary-reading value into applied self-assessment. #### 🌿 Naturalistic learners - Present: none — no ecological, biological, or sustainability framing, despite the "zombie"/"undeath" biological metaphor running throughout. - Improve: the metaphor could be extended (e.g., explicit ecosystem/succession analogies — a dead tree still standing, still providing habitat, before it falls) to appeal to readers who think in systems/ecology terms; not essential given the metaphor already partially serves this function. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: the fetched content shows clear H2-level section headings and consistent paragraph structure, which should map to reasonable heading landmarks for screen reader navigation. - Improve: cannot verify alt text, ARIA roles, or landmark regions without inspecting the live page's HTML/DOM directly; recommend a manual screen-reader pass on the live URL. #### Keyboard navigation - Present: cannot assess from fetched text content alone. - Improve: manual keyboard-only navigation test recommended on the live page (tab order, focus visibility, skip links). #### Contrast and readability - Present: cannot assess visual contrast from extracted text; the site is a simple text-first blog layout based on structure. - Improve: verify body-text contrast ratio meets 4.5:1 minimum on the live page; long-form text like this benefits from generous line-height (1.5+) given sentence length. #### Text resizing and reflow - Present: cannot assess from extracted text content. - Improve: verify the live page reflows cleanly at 200% zoom without horizontal scrolling or clipped content, given the essay's length. #### Media and captions - Not applicable to this source — the article contains no audio, video, or embedded media requiring captions or transcripts. #### Forms and interactions - Not applicable to this source — no forms, inputs, or interactive widgets appear in the article content. #### Standards reference - Given the unknowns above, the only assessable WCAG 2.2 AA criteria from text content alone are 1.3.1 (Info and Relationships — heading structure appears sound) and 2.4.6 (Headings and Labels — section headings are descriptive); contrast (1.4.3), reflow (1.4.10), and keyboard operability (2.1.1) require a live-page audit to confirm. ### 🌍 DEIB Assessment #### Cultural breadth - Present: none explicit — all examples (Photoshop/Adobe, generic "software markets") are Western/US-centric and framed at a global-abstract level without regional specificity. - Improve: examples drawn from non-US markets or industries outside Western enterprise software would broaden applicability and demonstrate the framework isn't Silicon-Valley-specific. #### Inclusive language - Present: strong — the essay uses gender-neutral language throughout ("the executive," "somebody," "leadership") and defines jargon in-line rather than assuming shared vocabulary. - Improve: minimal gaps; the essay is already careful on this dimension. #### Neurodiversity support - Present: moderate — consistent H2-level section structure and short paragraph chunks aid predictability, though individual paragraphs are dense and sentences are long. - Improve: shorter sentences and more frequent subheadings (the essay currently runs long stretches — some sections exceed 1,000 words — under a single H2) would reduce cognitive load. #### Representation - Present: minimal — the essay speaks in abstractions ("the organization," "leadership," "a challenger") rather than quoting or naming varied real people or roles; Adobe is the only named company, used illustratively rather than as a stakeholder voice. - Improve: including quotes or case perspectives from a range of actual practitioners (founders, incumbents' employees, analysts) across company sizes and backgrounds would add representational texture. #### Psychological safety - Present: the tone is analytical rather than accusatory toward any named company or individual; the Adobe example is explicitly hedged ("illustration rather than a prediction"). - Improve: none needed — the essay already handles its one named-company example carefully to avoid reading as a specific attack. ### ✅ Logical Validity #### Strong reasoning - The three-condition definition of a zombie company (dependency on past advantage + demand moving elsewhere + structural inability to follow) is a strong deductive framing: it explicitly excludes plausible alternative explanations (ordinary maturity, deliberate harvesting, rational shrinkage) rather than defining "zombie" so loosely it could describe any aging company. This is the essay's strongest piece of reasoning because it does definitional work that makes the later claims falsifiable in principle. - The "hollowing out" causal chain (retreat to profitable core → average revenue rises → margins improve → market share increases among remaining competitors → pipeline for future customers quietly disappears) is a strong causal argument because each step is independently plausible and the chain explains a genuinely counter-intuitive outcome: that the exact metrics used to reassure a board get *better* as the underlying business gets worse. This gives the argument real explanatory power beyond restating "big companies get complacent." - The moat-vs-momentum analogical distinction is used consistently and precisely throughout (not just introduced once and dropped), which strengthens it as a working analytical tool rather than a one-off rhetorical flourish. #### Fallacies - Hasty generalization risk in the political-economy argument ("every function protects the company from immediate harm... together, they protect it from becoming anything else"): this is presented as a near-universal mechanism across all large organizations, but no counter-examples or exceptions are examined (e.g., companies that *did* successfully cannibalize themselves). The fix would be acknowledging survivorship among incumbents that did adapt, and specifying what differed in those cases. - Unfalsifiable framing risk: because "zombie" status is defined partly by outcomes only visible in hindsight ("the sources of future demand are moving elsewhere" — how would you know before the market confirms it?), the framework risks being applied only retroactively to companies that have already failed, weakening its claimed diagnostic/predictive value. A fix would be specifying observable leading indicators that could flag zombie status *before* financial confirmation, which the essay gestures at (entry-level customer erosion) but doesn't operationalize into a testable metric. - The Photoshop/Adobe illustration is explicitly hedged as non-predictive, which is good practice, but its placement mid-essay (after several pages building the zombie-company case) risks readers treating it as confirming evidence for Adobe specifically despite the disclaimer — a rhetorical risk more than a strict logical fallacy, but worth flagging. #### Tone of voice - Analytical, measured, and consistently abstract — the essay almost never names specific companies (Adobe/Photoshop and Canva being the sole exceptions, both explicitly hedged), which keeps the tone diagnostic rather than accusatory. Sentences are long and cumulative, building each claim on the prior paragraph's vocabulary, which produces a lecture-like, essayistic register rather than a punchy consulting-deck tone. ### 🛡️ DARVO Analysis - Not applicable to this source — DARVO (Deny, Attack, Reverse Victim and Offender) analyzes rhetorical strategies used to deflect a specific accusation against a named party. This essay is a general analytical/diagnostic piece about corporate strategy patterns; it does not respond to, defend against, or deflect any accusation, and its one named example (Adobe) is explicitly used as a hedged illustration rather than an accusation the essay is defending against or leveling. ## 🎯 Conclusion - Bottom line: financial metrics are lagging indicators of strategic health, so a company can be measurably successful and strategically dead at the same time — the real failure point is when the organization loses the ability to build a credible future for itself, not when the market eventually notices via falling revenue. - The moat/momentum distinction and the three-condition zombie test are the practical takeaways readers can apply directly to their own organizations or portfolio holdings, ahead of any prescriptive fix the essay itself offers. - Practical next steps for readers: run the three-condition test against your own company or a company you're evaluating (invest in, work for, compete against); separately track which KPIs would mathematically improve during a "hollowing out" retreat to the profitable core; and treat entry-level/low-value customer erosion as a leading signal worth board-level attention rather than a segment to happily shed. ## 🔄 Refactor Appendix — Zombie Companies > Density: 2–5 Literature atoms (H3), 0–3 Permanent candidates (H4). > Defaults: 3 Literature, 1 Permanent. Resonance filter: if you can't > articulate in one line why a claim matters, drop it. > > Konik claim-header rules: present tense, declarative, ≤10 words when > possible, searchable, unique, mirrors annotation focus if present. > > Atomicity: one declarative sentence per atom. "and"/"also" → split. > > Tag pool: #bmf · #addendum · #xref · #articleseed · #storystem · #share · #aphorisms ### 📚 Literature Atoms (H3) #### Success metrics measure accumulated advantage, not current capability > [!quote] ID:rw_zombie001 > "Most of them describe what the company has built up, rather than what it can still build." **Context & use**: - Appears in the "Success is a lagging indicator" section, early in the essay, establishing the core reframe. - Central to the whole argument: it's the reason revenue/retention/market-share can stay strong while strategic capability decays underneath them. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### Zombie status requires three conditions holding simultaneously > [!quote] ID:rw_zombie002 > "Current performance depends heavily on advantages accumulated under earlier conditions; the sources of future demand are moving elsewhere; and the organisation cannot follow them without damaging the business it is rewarded for protecting." **Context & use**: - From "What makes a company a zombie?" — this is the essay's precise, falsifiable-in-principle definition. - Distinguishes genuine zombie status from ordinary maturity, harvesting, or rational decline, which only satisfy one or two of the three conditions. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### A moat reinforces itself; momentum just coasts on inherited weight > [!quote] ID:rw_zombie003 > "A moat makes the company harder to attack. Momentum merely makes the consequences of attack slower to appear." **Context & use**: - From "Delay is mistaken for resilience" — the essay's key diagnostic tool for telling healthy incumbency from zombie status from the inside. - Explains why leadership can look at identical positive numbers and misread latency as resilience. **Tags**: #xref **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> #### Retreating to the profitable core can make KPIs improve as the pipeline hollows out > [!quote] ID:rw_zombie004 > "The organisation reports better numbers, while the quality of the underlying opportunity deteriorates. This is how hollowing out hides inside an apparently sensible strategy." **Context & use**: - From "The cost of challenging incumbents is falling" — explains the counter-intuitive mechanism where standard board-level metrics get better precisely as the company's future pipeline disappears. - Sharpest, most falsifiable empirical claim in the piece; worth testing against real cohort data (see Hypotheses H2). **Tags**: #xref #articleseed **Highlight**: [view highlight](readwise://) <!-- atomicity: 1 idea ✓ --> ### 🧠 Permanent Candidates (H4) #### Adaptation fails politically, not intellectually, in large incumbents **Claim** (one sentence, Courtney's voice): Large organizations don't fail to adapt because leadership misunderstands the threat — they fail because every internal function has a locally rational reason to protect its own piece of the current model, so the company can sincerely agree change is necessary while collectively preventing it. **Evidence pointer**: [[#Adaptation fails politically, not intellectually, in large incumbents]] — see literature atom on zombie conditions above; Alderson develops this at length in "Why the company cannot simply adapt." **Scope & conditions**: Holds in large, multi-function organizations with entrenched revenue lines and internal political stakes; less applicable to small, single-owner, or founder-controlled companies where one person can simply override departmental resistance. **Links** (≥1 with annotation): - [[Cannibalization trap]] — because extends (explains why boards approve innovation in principle but starve it of authority in practice) - [[Incentive-driven organizational stasis]] — because applies-in (any large-org change-management context, not just this essay's corporate-strategy frame) **Optional**: status: seedling <!-- atomicity: 1 idea ✓ --> ### ✏️ Fleeting Queue - [F1] Test whether AI-assisted comparison/procurement tools are already measurably shortening incumbent runway in any documented B2B software category — worth a research pass. #articleseed - [F2] Find or build a public "moat vs. momentum" scorecard for a handful of well-known incumbents to see if the framework predicts anything testable over the next few years. #xref ### → Things 3 (max 2 actions) - [ ] Re-read "The middle is a graveyard" and "When scrutiny becomes cheap" as companion pieces to this essay — #things <!-- deep-read:sections end --> 📄 **Full text:** [[Full Document Contents/Articles/Zombie Companies.md|Zombie Companies by jonoalderson.com]] ## Highlights - A company is not a zombie merely because it is old, bureaucratic, shrinking or harvesting a mature product. Those can all be rational conditions or choices. The zombie state requires three things to be true at once: current performance depends heavily on advantages accumulated under earlier conditions; the sources of future demand are moving elsewhere; and the organisation cannot follow them without damaging the business it is rewarded for protecting. ([View Highlight](https://read.readwise.io/read/01kxk2bp7hd9d1c1qaz984xaz3)) - Tags: atom/literature/h1 - At that point, the organisation discovers that everything which made it reliable also made it rigid. New ideas must fit existing departments. Emerging products must justify themselves using the economics of mature ones. Alternatives look naive, incomplete or commercially irresponsible because they threaten the assumptions through which the company understands success. ([View Highlight](https://read.readwise.io/read/01kxpkg1pjke2aa2ywes5fx7zd)) - Tags: 👻 ai highlighted - But a moat makes the company harder to attack. Momentum merely makes the consequences of attack slower to appear. ([View Highlight](https://read.readwise.io/read/01kxk2awe8yzxcj4bvx9m11hh8)) - Tags: atom/literature/h2 - he business is no longer creating proportionate amounts of *new value*. It is improving its ability to extract value from a position created *earlier*. ([View Highlight](https://read.readwise.io/read/01kxpkfftq8ewdhkep09easz9p))