When a product is failing, the instinct is to generate more options — new features, pivots, experiments. But the 11th-century Persian polymath Al-Biruni, writing about how knowledge hardens into dogma, noticed something subtler: people in trouble don't need more choices, they need a sharper account of what's actually happening. He called this the difference between *taqlid* — inherited assumption — and *tahqiq*, disciplined inquiry into first principles. Most product roadmaps are taqlid dressed up as strategy. The team inherits a theory of the user's problem from early discovery, and every subsequent quarter, that theory accumulates features like barnacles. Al-Biruni's method — used to reconcile wildly different astronomical systems across cultures — was to hold the inherited model lightly enough to test its load-bearing assumptions directly against observation. In PM terms: before your next sprint planning, identify the one belief about your user that has never been pressure-tested since inception. That belief is probably running the show.

What did you assume about your user in the first month of your product that you have treated as settled fact ever since — and what would it cost to be wrong about it?

Drawing from Islamic Classical Scholarship / Comparative Epistemology — Al-Biruni (Kitab al-Hind / Book of India, c. 1030 CE)