We have been scammed by the Gaussian distribution club

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, 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

2026

  1. How I started building softwares with AI agents being non technical

2025

  1. Legible and illegible tasks in organisations
  2. L2 Fat marker sketches
  3. Writing as moats for humans
  4. Beauty of second degree probes
  5. Read raw transcripts
  6. Boundary objects as the new prototypes
  7. One way door decisions
  8. Finished softwares should exist
  9. Essay Quality Ranker
  10. Export LLM conversations as snippets
  11. Flipping questions on its head
  12. Vibe writing maxims
  13. How I blog with Obsidian, Cloudflare, AstroJS, Github
  14. How I build greenfield apps with AI-assisted coding
  15. We have been scammed by the Gaussian distribution club
  16. Classify incentive problems into stag hunts, and prisoners dilemmas
  17. I was wrong about optimal stopping
  18. Thinking like a ship
  19. Hyperpersonalised N=1 learning
  20. New mediums for humans to complement superintelligence
  21. Maxims for AI assisted coding
  22. Personal Website Starter Kit
  23. Virtual bookshelves
  24. It's computational everything
  25. Public gardens, secret routes
  26. Git way of learning to code
  27. Kaomoji generator
  28. Style Transfer in AI writing
  29. Copy, Paste and Cite
  30. Understanding codebases without using code
  31. Vibe coding with Cursor
  32. Virtuoso Guide for Personal Memory Systems
  33. Writing in Future Past
  34. Publish Originally, Syndicate Elsewhere
  35. Poetic License of Design
  36. Idea in the shower, testing before breakfast
  37. Technology and regulation have a dance of ice and fire
  38. How I ship "stuff"
  39. Weekly TODO List on CLI
  40. Writing is thinking
  41. Song of Shapes, Words and Paths
  42. How do we absorb ideas better?

2024

  1. Read writers who operate
  2. Brew your ideas lazily
  3. Vibes
  4. Trees, Branches, Twigs and Leaves — Mental Models for Writing
  5. Compound Interest of Private Notes
  6. Conceptual Compression for LLMs
  7. Meta-analysis for contradictory research findings
  8. Beauty of Zettels
  9. Proof of work
  10. Gauging previous work of new joinees to the team
  11. Task management for product managers
  12. Stitching React and Rails together
  13. Exploring "smart connections" for note taking
  14. Deploying Home Cooked Apps with Rails
  15. Self Marketing
  16. Repetitive Copyprompting
  17. Questions to ask every decade
  18. Balancing work, time and focus
  19. Hyperlinks are like cashew nuts
  20. Brand treatments, Design Systems, Vibes
  21. How to spot human writing on the internet?
  22. Can a thought be an algorithm?
  23. Opportunity Harvesting
  24. How does AI affect UI?
  25. Everything is a prioritisation problem
  26. Now
  27. How I do product roasts
  28. The Modern Startup Stack
  29. In-person vision transmission
  30. How might we help children invent for social good?
  31. The meeting before the meeting
  32. Design that's so bad it's actually good
  33. Breaking the fourth wall of an interview
  34. Obsessing over personal websites
  35. Convert v0.dev React to Rails ViewComponents
  36. English is the hot new programming language
  37. Better way to think about conflicts
  38. The role of taste in building products
  39. World's most ancient public health problem
  40. Dear enterprises, we're tired of your subscriptions
  41. Products need not be user centered
  42. Pluginisation of Modern Software
  43. Let's make every work 'strategic'
  44. Making Nielsen's heuristics more digestible
  45. Startups are a fertile ground for risk taking
  46. Insights are not just a salad of facts
  47. Minimum Lovable Product

2023

  1. Methods are lifejackets not straight jackets
  2. How to arrive at on-brand colours?
  3. Minto principle for writing memos
  4. Importance of Why
  5. Quality Ideas Trump Execution
  6. How to hire a personal doctor
  7. Why I prefer indie softwares
  8. Use code only if no code fails
  9. Personal Observation Techniques
  10. Design is a confusing word
  11. A Primer to Service Design Blueprints
  12. Rapid Journey Prototyping
  13. Directory Structure Visualizer
  14. AI git commits
  15. Do's and Don'ts of User Research
  16. Design Manifesto
  17. Complex project management for product

2022

  1. How might we enable patients and caregivers to overcome preventable health conditions?
  2. Pedagogy of the Uncharted — What for, and Where to?

2020

  1. Future of Ageing with Mehdi Yacoubi
  2. Future of Equity with Ludovick Peters
  3. Future of Tacit knowledge with Celeste Volpi
  4. Future of Mental Health with Kavya Rao
  5. Future of Rural Innovation with Thabiso Blak Mashaba
  6. Future of unschooling with Che Vanni
  7. Future of work with Laetitia Vitaud
  8. How might we prevent acquired infections in hospitals?

2019

  1. The soul searching years
  2. Design education amidst social tribulations
  3. How might we assist deafblind runners to navigate?