The Product Manager Who Manages No Products
Nothing reveals an organization’s theory of product quite like giving someone the title “product manager” while denying them a product.
The role only works when you stay close enough to a problem space for its texture to become second nature. Marty Cagan has spent two decades making this argument while the industry nods politely and keeps spreading PMs across teams like jam on toast.
Pool the function across half a dozen teams, then again as the headcount maths demands, and you cross a dilution threshold below which the practitioner deserves a new name: the asymptotic homeopathic PM, an infinitesimal trace of product thinking dissolved in the organization, yet asked to produce finite outcomes from a vanishing concentration. That metaphor is generous: homeopathy at least promises something survives near-infinite dilution, which is more than the teams who have not seen you since the last reorg can claim about you.
Engineers escalate problems only when something burns, so by the time you appear half the decisions are already baked into code, which leaves you reconstructing context while the team stalls. The organization manufactures a bottleneck, and then blames you for being that bottleneck.
Discovery dies too, because noticing patterns requires sustained presence in a domain you do not have, and every product question you meet is already overdue by the time it reaches you.
Prioritization disappears next. The queue resolves by whoever escalates fastest or loudest, which the status deck continues to label strategy. Trust follows the same logic and migrates to whoever stays in the room. You are everywhere in people’s calendars and nowhere in their mental model of ownership.
The cruelty of the design is that the one capacity it still permits you, sitting between technical and managerial worlds and ferrying information across, is precisely the capability that organizational research has long identified as essential in complex environments. A small population of people able to translate across specialist communities can improve coordination and information flow considerably. The same pool that drowns the individual PM washes away any organizational advantage that translation between worlds has been shown to deliver.
Platforms decay too, though complex systems rarely crash and burn from a single dramatic failure. They drift through small unowned shortcuts, deferred decisions, and risks that no one is paid to notice. And a pooled PM function guarantees that no one is paid to notice.
In the review cycle, your year reduces to a list of crises parachuted into and left behind, which reads as drift rather than anything a committee can defend. You have no arc to sell, only activity to describe, which any competent external hiring manager reads as someone the previous organization kept busy without trusting. The model robs you of the only currency the profession respects, which is a before-and-after with your fingerprints on it.
The arrangement is usually defended as flexibility, which would be more persuasive if it produced any. What it produces is institutionalized amnesia in management vocabulary, with each team reintroducing itself to you, each review cycle resetting the context you had begun to build, each new initiative starting from a blank page someone else filled in last quarter and discarded. Calling this a bold reinvention of product management is the polite name for abolishing the role under cover of efficiency: your slow disappearance from a role the org chart still counts as filled.