Aristotle drew a distinction between two kinds of knowledge that most product organizations collapse into one: *episteme* — the kind of understanding that holds universally — and *phronesis*, practical wisdom that only works inside a specific context, for this situation, with these people, right now. Modern product culture has become very good at the first kind. We run discovery frameworks, write specs in structured templates, cite benchmark data, build reusable research repositories. All of this is episteme-flavored: it travels well, it scales, it looks authoritative in a deck. The trap is that phronesis doesn't travel. It lives in the practitioner who has spent three years watching how a particular user population hesitates before abandoning a flow, or who has felt the specific organizational gravity that makes 'engineering will push back on this' not a guess but a known quantity. When you bring in a new PM lead and hand them a playbook, you have handed them episteme. What they are missing — what takes 18 months to grow and cannot be onboarded in a sprint — is phronesis. The practical consequence: the most important thing a product leader does with someone early in their tenure is not share frameworks. It's to deliberately engineer the kind of situated, repeated contact with real users and real constraints that can only be learned by being there.

Think of a major product call you made in the last six months that turned out right. How much of what made it right was something you could write down — and how much was something you couldn't have explained to someone who wasn't already in the room?

Drawing from Aristotelian Ethics / Virtue Epistemology — Aristotle (Nicomachean Ethics, c. 350 BCE)