We have been scammed by the Gaussian distribution club

08 Apr 2025

Shreyas Prakash headshot

Shreyas Prakash

Taleb insists that we’ve been scammed by the Gaussian distribution club.

The gaussian distribution has become so ubiquitous in our daily jargons, oru day-to-day decisions even.

“We have been duped by the bell curve. Mandelbrot was the first to rigorously prove that markets are not Gaussian.” – Taleb

As most real-world phenomena: especially complex, human-involved systems are not well-behaved in any sense : Gaussian distributions are the exception, not the rule.

My world view has also changed after reading Nassim Taleb’s Fooled by Randomness book, and I’ll form my opinion here in this essay as to why it’s so:

Most of the non-deterministic random events can be classified as either a thin-tail, or a fat-tailed in nature.

If we take the example of the average height of human population, it’s a thin-tailed event, especially since there is a strict upper bound (ceiling) to what the tallest person could be. There are also no complex interdynamic feedback loops that reinforce each other, and therefore, it’s possible to estimate with certain confidence, what the “average height” could be. It can certainly (NEVER) be the equivalent of Burj Khalifa no matter what edge case we might consider for modelling this distribution.

Mandelbrot builds on this idea, and explains that most natural phenomena dont follow such normalised thin-tail gaussian distributions. Instead, they exhibit more “wild randomness”. Mandelbrot’s early work was on cotton price fluctuations, and how he demonstrated this to be incongruous with the Gaussian models.

And it’s not just with financial markets, you could see it all over: wealth distributions, book sales, war, Fukushima, pandemics — places where a single data point (a Black swan), can completely disrupt the average. And to model real-world risks more accurately, Taleb insists we follow Mandelbrot’s Lévy-stable distributions which better explain real-world risks. What is a Lévy-stable distribution?

Example:

  • If 10,000 people each lose 1,thats1, that’s 10,000.
  • If one person loses $10 million, that single event overwhelms the rest.

In these examples, there are volatile clusters, price changes in market are more “jumpy”, large changes are more frequent. And are therefore, fat-tailed. And in such systems, it becomes pointless to even do a forecast, as they have infinite variance.

And as a result, it leads to a form of epistemic humility, where you don’t use confidence intervals, don’t use standard deviation, don’t even do probabilistic forecasts. You could throw all the standard deviation math you learnt in school textbooks and put it into the dustbin.

And instead of them, you focus on other aspects of risk-management: what is the maximum loss you can absorb? any non-linear payoffs? any hedging strategies? you might also do more “stress testing” to understand the jumpiness, rather than pointless scenario modelling.

Once we acknowledge that we’re living in a levy-stable world, and not a gaussian world, our decisions change. For example, when it comes to portfolios, in the gaussian world, we might want to diversity across many uncorrelated assets, expecting that some of them might pick up well. But in a Levy-stable world, we acknowledge that market crashes can be 100x more likely than predicted (it’s the rule, not the exception). And therefore, you might switch to a format of the barbell strategy: where 90% in ultra-safe assets (gold, cash, farmland), and 10% in high-risk, volatile, high-optional assets (eg. startup equity, crypto, etc).

Similarly, if we look at insurance, in the gaussian world, an insurance company might expect to sell lots of policies assuming claims average out. But in a Levy-stable world, you acknowledge that one freak event (COVID, Fukushima, 9/11) can wipe out 10 years of profits. The compound tail risk is huge. So in the Levy-stable world, you are spending more time thinking about stress-testing, where you try to limit the maximum exposure to a single catastrophic event. This thinking, even applies to national-infrastructure, cybersecurity etc, where most of the resource allocation goes towards risk-minimisation around the most frequent issues (eg. threats circulated in newspapers, small outages, recent scandals etc), but there could be breaches which are from the unknown unknowns.

Levy-stable world acknowledges us to simulate catastrophic scenarios, not just the average-case scenarios.

DomainGaussian ApproachLévy-Stable (Fat-Tailed) Approach
InvestingDiversify, maximize Sharpe ratioBarbell strategy, seek asymmetry
EntrepreneurshipPlan, forecast ROISmall bets, high asymmetry, fail fast
InfrastructureMean-time-to-failure modelingDesign for rare catastrophic failure
CareerSteady ladder climbingSeek optionality, build many convex exposures
Risk modelingUse standard deviation, confidence intervalsUse stress testing, max drawdown, convex payoff maps

Subscribe to get future posts via email (or grab the RSS feed). 2-3 ideas every month across design and tech

Read more

  1. Home is where the feeling of home residesreflections
  2. Notes on doing most good, doing some good, and living goodphilanthropy
  3. Notes on Londontravel
  4. 18 key ideas from reading Henrik Karlsson this monthwriting
  5. Stop arguing, and start drawing circles togethermathematics
  6. The whole world is just the snake eating its own tailmental-models
  7. Life lessons and hot takes from my 30slifestyle
  8. Building a skill for coherent science illustrationsscience
  9. My agentic engineering workflow (step by step)agentic-coding
  10. Hammock driven developmentagentic-coding
  11. Peculiar ways number three fits into our funny little brainsmental-models
  12. AI sandwich as a defacto principle for anything agentic engineering relatedagentic-coding
  13. Authority in the guise of evidencecritical-rationalism
  14. Map is not the territoryphilosophy
  15. Self hypnosis as a manifestation ritualmeditation
  16. Hegelian dialectic for structured reasoning with AI agentsphilosophy
  17. How I prepare for tough negotiations nowadaysnegotiation
  18. When should we steelthread somethingproduct-development
  19. Breadboarding, shaping, slicing, and steelthreading solutions with AI agentsproduct
  20. Healthy conflict in teams have a tipping pointteam-building
  21. How I deslopify AI writingwriting
  22. How I started building softwares with AI agents being non technicalagentic-coding
  23. Read raw transcriptswriting
  24. Legible and illegible tasks in organisationsproduct
  25. L2 Fat marker sketchesdesign
  26. Writing as moats for humanswriting
  27. Beauty of second degree probesdecision-making
  28. Boundary objects as the new prototypesprototyping
  29. One way door decisionsproduct
  30. Finished softwares should existproduct
  31. How I periodically rank my rough draftsobsidian
  32. Flipping questions on its headinterviewing
  33. Vibe writing maximswriting
  34. How I blog with Obsidian, Cloudflare, AstroJS, Githubwriting
  35. How I build greenfield apps with AI-assisted codingagentic-coding
  36. We have been scammed by the Gaussian distribution clubmathematics
  37. Classify incentive problems into stag hunts, and prisoners dilemmasgame-theory
  38. I was wrong about optimal stoppingmathematics
  39. Thinking like a shipmental-models
  40. Hyperpersonalised N=1 learningeducation
  41. New mediums for humans to complement superintelligenceagentic-coding
  42. Maxims for AI assisted codingagentic-coding
  43. Virtual bookshelvesaesthetics
  44. It's computational and AI everythingagentic-coding
  45. Public gardens, secret routesdigital-garden
  46. Git way of learning to codeagentic-coding
  47. Style Transfer in AI writingagentic-coding
  48. Understanding codebases without using codeagentic-coding
  49. Vibe coding with Cursoragentic-coding
  50. Virtuoso Guide for Personal Memory Systemsmemory
  51. Writing in Future Pastwriting
  52. Publish Originally, Syndicate Elsewhereblogging
  53. Poetic License of Designdesign
  54. Idea in the shower, testing before breakfastsoftware
  55. Technology and regulation have a dance of ice and firetechnology
  56. How I ship "stuff"software
  57. Writing is thinkingwriting
  58. Song of Shapes, Words and Pathscreativity
  59. How do we absorb ideas better?knowledge
  60. Read writers who operatewriting
  61. Brew your ideas lazilyideas
  62. Trees, Branches, Twigs and Leaves — Mental Models for Writingwriting
  63. Compound Interest of Private Noteswriting
  64. Conceptual Compression for LLMsagentic-coding
  65. Meta-analysis for contradictory research findingsdigital-health
  66. Proof of workproduct
  67. Gauging previous work of new joinees to the teamleadership
  68. Task management for product managersproduct
  69. Beauty of Zettelswriting
  70. Stitching React and Rails togetheragentic-coding
  71. Exploring "smart connections" for note takingwriting
  72. Deploying Home Cooked Apps with Railssoftware
  73. Repetitive Copypromptingwriting
  74. Questions to ask every decadejournalling
  75. Balancing work, time and focusproductivity
  76. Hyperlinks are like cashew nutswriting
  77. Brand treatments, Design Systems, Vibesdesign
  78. How to spot human writing on the internetwriting
  79. Can a thought be an algorithm?product
  80. Opportunity Harvestingcareers
  81. Everything is a prioritisation problemproduct
  82. How I do product roastsproduct
  83. The Modern Startup Stacksoftware
  84. In-person vision transmissionproduct
  85. How might we help children invent for social good?social-design
  86. The meeting before the meetingmeetings
  87. Design that's so bad it's actually gooddesign
  88. Lessons learnt interview prepping for product rolesinterviewing
  89. Obsessing over personal websitessoftware
  90. English is the hot new programming languagesoftware
  91. Better way to think about conflictsrisk-management
  92. The role of taste in building productsdesign
  93. Dear enterprises, we're tired of your subscriptionssoftware
  94. Products need not be user centereddesign
  95. World's most ancient public health problemsoftware
  96. Pluginisation of Modern Softwaredesign
  97. Let's make every work 'strategic'consulting
  98. Making Nielsen's heuristics more digestibledesign
  99. Startups are a fertile ground for risk takingentrepreneurship
  100. Insights are not just a salad of factsdesign
  101. Minimum Lovable Productproduct
  102. Methods are lifejackets not straight jacketsmethodology
  103. How to arrive at on-brand colours?design
  104. Minto principle for writing memoswriting
  105. Importance of Whytask-management
  106. Quality Ideas Trump Executionsoftware
  107. Why I prefer indie softwareslifestyle
  108. Use code only if no code failscode
  109. Self Marketing
  110. Personal Observation Techniquesdesign
  111. Design is a confusing worddesign
  112. A Primer to Service Design Blueprintsdesign
  113. Rapid Journey Prototypingdesign
  114. Visualise detailed file structures on CLIcli
  115. Do's and Don'ts of User Researchdesign
  116. Design Manifestodesign
  117. Complex project management for productproducts
  118. How might we enable patients and caregivers to overcome preventable health conditions?digital-health
  119. Pedagogy of the Uncharted — What for, and Where to?education
  120. Future of Equity with Ludovick Petersinterviewing
  121. Future of Ageing with Mehdi Yacoubiinterviewing
  122. Future of Tacit knowledge with Celeste Volpiinterviewing
  123. Future of Mental Health with Kavya Raointerviewing
  124. Future of unschooling with Che Vanniinterviewing
  125. Future of Rural Innovation with Thabiso Blak Mashabainterviewing
  126. Future of work with Laetitia Vitaudinterviewing
  127. How might we prevent acquired infections in hospitals?digital-health
  128. The why to endure any howentrepreneurship
  129. Design education amidst social tribulationsdesign
  130. How might we assist deafblind runners to navigate?social-design