Concepts

When Frameworks Fail

Published by When Notes Fly

https://whennotesfly.com/concepts/frameworks-models/when-frameworks-fail

When Notes Fly article, fact-checked and corrected.

Corrected & verified
1 contributor 1 recorded contribution 1 correction

Who created and checked this page

Correction history

Every accepted correction to this page is recorded with the exact change, so readers can see how the page improved over time.

  1. 28 July 2026 · corrected by Emir Baycan

    Corrected six overstated or inaccurate claims: clarified that 'the customer is always right' is a retail-era maxim, not an Agile principle (Agile emphasizes customer collaboration); reframed the Gaussian copula as one important contributor to mispriced CDO risk rather than the single universal cause of the 2008 crisis; qualified the Lehman VaR framing to note VaR by design says little about extreme tail events, rather than implying its outputs were predictably wrong; corrected the Waterfall description to sequential plan-driven engineering/manufacturing practice that can work when conditions hold rather than consistently failing; flagged the British-India cobra bounty as a widely repeated but poorly documented parable; and reframed Nokia's market-segmentation framework as one factor among several (software, ecosystem, organizational) in its smartphone struggles. The Porter/Five Forces Android illustration was left as a valid example.

    Before

    The article said Lehman VaR models made the collapse predictably wrong, Waterfall came from civil engineering and consistently fails, 'the customer is always right' is an Agile principle, the Gaussian copula was the universal standard cause of the CDO crisis, and Nokia's internal framework caused its smartphone failure.

    After

    Qualified the VaR, Waterfall, copula, and Nokia claims to acknowledge multiple causes and design limitations, corrected the false Agile attribution, and flagged the cobra story as a parable.

    Why: The claims were more absolute or mono-causal than the evidence supports, and the Agile attribution was incorrect. Corrections scope the claims and fix the attribution rather than adding new sources.

    View the full record →

Full contribution timeline

  1. Correction 28 July 2026

    Emir Baycan: Corrected six overstated or inaccurate claims: clarified that 'the customer is always right' is a retail-era maxim, not an Agile principle (Agile emphasizes customer collaboration); reframed the Gaussian copula as one important contributor to mispriced CDO risk rather than the single universal cause of the 2008 crisis; qualified the Lehman VaR framing to note VaR by design says little about extreme tail events, rather than implying its outputs were predictably wrong; corrected the Waterfall description to sequential plan-driven engineering/manufacturing practice that can work when conditions hold rather than consistently failing; flagged the British-India cobra bounty as a widely repeated but poorly documented parable; and reframed Nokia's market-segmentation framework as one factor among several (software, ecosystem, organizational) in its smartphone struggles. The Porter/Five Forces Android illustration was left as a valid example.

    Proof record →