Reliability of Case Evidence

You're seeing it when a board member advocates entering a new market because "Company X did it and tripled revenue." One case — no matter how successful — doesn't establish that the strategy works in general or for you specifically.

You're seeing it when a sales team builds an entire persona around one enthusiastic early customer. That customer's needs may be idiosyncratic, not representative of the broader market.

You're seeing it when a hiring decision is justified by "our best engineer came from a non-traditional background, so let's change all our hiring criteria." One success story doesn't validate a systematic policy change.

Use customer case studies and competitor examples to generate hypotheses, not to confirm them. Before changing strategy based on a single compelling case, ask how many counterexamples exist that you haven't encountered. Seek the base rate before trusting the anecdote.

Ek built Spotify's recommendation and content strategy on aggregate data patterns rather than individual case evidence. Early music-industry wisdom was driven by case-based reasoning: "This artist broke out this way, so that's the formula." Ek's insight was that individual breakout stories were unreliable guides to systematic strategy — survivorship bias made every success story look replicable when most attempts following the same path failed. Spotify instead built systems that analyzed millions of listening patterns to identify reliable signals, treating each individual data point as one observation among many rather than a standalone conclusion. Founders benefit from the same discipline: let individual cases inform intuition, but let aggregate evidence drive decisions.