On the discipline's intellectual inheritance, what its training leaves out, and why product leaders keep rediscovering social problems too late
Product management rarely says out loud what kind of human it is trained to imagine. But its methods give it away. The user arrives as an individual decision-maker. The team is taught to map journeys, reduce friction, test variants, optimize activation, and improve retention. Those are useful skills. They also train a certain way of seeing.
What goes missing is society. Not people, exactly. Product teams care about people all the time. What they miss are the structures around people: institutions, groups, norms, identity, audience, social capital, labor, power, legitimacy, and the unequal conditions under which behavior becomes possible.
That gap is not accidental. It is part of the discipline's inheritance.
Product management grew at the intersection of engineering, business, and design. Engineering is good at systems. Business is good at markets. Design is often good at interfaces and usability. Even when PMs borrow from the social sciences, they most often borrow from psychology and behavioral economics, which keep the individual closer to the center than society.
The result is a field that has many tools for modeling choice and not many for modeling collective life. It can explain why one person hesitates in a flow more easily than it can explain why a community's norms are collapsing, why a rating system is extracting emotional labor, or why a marketplace feels efficient only because risk has been pushed outward.
That is why modern product teams keep rediscovering social problems late. The tools did not train them to see the system early.
Very few PM learning paths ask future leaders to study sociology, anthropology, institutional analysis, or political economy in any serious way. They may learn experimentation, metrics, prioritization, roadmap discipline, stakeholder management, and customer empathy. Those are all useful. But they do not fully prepare someone to understand products that behave like social infrastructure.
That gap matters more now because products increasingly govern work, learning, speech, care, reputation, and access. The PM who cannot think about audience, norms, labor, recourse, and power is often left diagnosing surface symptoms while deeper social mechanisms keep driving outcomes.
That is one reason I think practitioner work like Putting Users in Context and Why Aren't There More UX Sociologists? matters. These are not abstract academic complaints. They are practitioners naming a recurring failure in how digital work is framed.
It would still teach the core skills. But it would widen the lens. It would teach future product leaders how norms form, how institutions constrain behavior, how categories flatten people, how network structure shapes opportunity, how value gets routed, how products quietly organize power, and how social systems can degrade over time even while dashboards look healthy.
It would also normalize different kinds of evidence. Not only experiment results and feature analytics, but ethnography, historical context, institutional mapping, community diagnostics, and questions about who is absorbing the cost of the model.
Resources like the Product Management and Society Playbook are meaningful because they start to build that bridge. They treat product work as something closer to public infrastructure than to neutral optimization.
I do not think PM education needs more abstraction for its own sake. I think it needs better explanation for the world it already operates in. Products are now part of social order. A discipline trained mainly to see individuals will keep arriving at the collective consequences too late.
This essay is the educational companion to Product Management Has an Individualistic Ontology. That essay describes the blind spot inside the field's worldview. This one asks why the field keeps reproducing it.