Why this is in the vault
Cedric closes the loop on Commoncog's five-case "Navigating Disruptive Change" sequence (Swatch/quartz, Amazon/dotcom, Ford/GFC, Blockbuster/Netflix, BlackBerry), flagging cross-case patterns worth "hmm"-ing at — a meta-note on the case-method itself, not a new case.
Issue contents
- How to Handle Disruptive Change (main essay, mostly paywalled/members-only in this issue): Cedric revisits the five most recent Commoncog disruption cases, all commissioned after his Sensemaking Series, and says there's enough cross-case pattern to warrant deliberate comparison. He asked readers to pre-commit voice-note reactions before reading his own — a forcing function against anchoring. The "three points" he draws from the pattern are gated behind membership; not reproduced here.
- The five cases referenced: Swatch/Swiss watch quartz crisis, Amazon surviving the dotcom bust (explicitly flagged as relevant "if you're currently an AI darling"), Ford surviving the GFC (the one Big Three automaker that didn't need a bailout), Blockbuster vs. Netflix (nearly won, then lost), How BlackBerry Died.
- Forum highlights: a live debate on whether "far transfer" (a mainstream learning-science finding that skill doesn't generalize across domains) is actually a fatal objection to case-based learning; a resurrected case-study thread on land-development financing from a member with construction-industry depth; the BlackBerry case is being turned into Commoncog's first Tactical Decision Game.
- Elsewhere on the web: Gary Klein (2019) on why a 42-page systems-integration training manual missed everything that actually matters — the hard decisions, the failure modes, the tacit judgment calls — because manuals document procedure, not expertise; a book review of James Marriott's The New Dark Ages on declining literacy; Bryan Cantrill on "The Contagion of Fear" re: AI-development-pause rhetoric.
- Production note: Commoncog is converting its case library to AI-generated audio using premium TTS, with amusing failure modes (voices flipping gender mid-paragraph, static building into "screaming," mangled Malay/Chinese pronunciation).
Mapping against Ray Data Co
The Amazon/dotcom-bust case is the direct hook: Cedric explicitly frames it as a lens for "if you're currently an AI darling" — which is exactly RDCO's positioning bet (L4→L5, agent-capability-driven bets per project_l5_north_star_strategic_direction). The useful frame isn't the case content (paywalled here) but the method: pre-commit your own read before consuming the expert's, then compare. That's a sharper discipline than RDCO currently applies to its own thesis reviews (e.g. project_investing_markov_capital_cycle) — worth stealing for any future case study or dissent-cluster review: write the take first, then check it against the graph/vault evidence, rather than reading-then-concluding.
Related
- [[2026-09-09-commoncog-blackberry-died]]
- [[2026-08-06-commoncog-ford-survived-gfc]]
- [[2026-08-18-commoncog-blockbuster-vs-netflix]]
- [[2026-07-03-commoncog-quartz-crisis-tech-disruption]]
- [[2026-07-28-commoncog-disruption-calibration-case-method]]
- [[project_l5_north_star_strategic_direction]]