Work
Five different product managers, each speaking what seemed like entirely different languages. One talked about APIs and data schemas. Another kept discussing "North Star metrics" and "strategic alignment." A third was sketching wireframes while muttering about user flows. Welcome to the strange ecosystem of product management, where even those sharing the same job title are different species entirely.
The great PM divergence.
After two years of commuting, I've catalogued these fascinating creatures in their natural habitat. I've been each type at various points in my career, sometimes by design, sometimes by accident, and occasionally by what could only be described as workplace evolutionary pressure.
The technical PM:
Code-whisperers & API-botherers.
Technical Product Managers (TPMs) are the ones who've been in the trenches. Former infrastructure engineers, developers, and yes, even those patient IT help desk warriors. They speak fluent Engineer and can translate that into something approaching Human when needed. Their superpower is bridging the gap between engineering teams and business management.
In meetings, you'll spot them by their uncomfortable expressions whenever someone says something technically inaccurate. "Actually, that would require refactoring the entire authentication service", might as well be their mating call.
TPMs excel at understanding technical constraints, spotting potential architecture issues, and generally keeping products from exploding. However, they occasionally forget that users don't care about elegant code as much as they do about solving their problems. I've been guilty of this myself.
The strategic PM:
Vision-havers & future-dwellers.
Strategic PMs operate at 30,000 feet, spotting market opportunities and connecting business goals to product decisions. They work with diverse stakeholders to develop new products or enhance existing ones based on strategic customer needs. When a Strategic PM speaks, executives listen, mainly because they use the same language.
Strategic PMs thrive on competitive analysis, market research, and building business cases. They're the ones who understand why we're building things, not just how. Their weakness? Sometimes, losing sight of immediate user needs while chasing grand visions.
The designer PM:
Pixel-perfectionists & empathy-engines.
These PMs have design backgrounds and obsess deeply about user experience. The Designer PM brings unique perspective through their natural understanding of user empathy and visual problem-solving. They're the ones who will die on the hill of a button UX issue. They drive user satisfaction scores.
Designer PMs create intuitive, beautiful products that users enjoy using. However, they sometimes struggle with technical constraints and business priorities. Their strength is imagining perfect experiences; their weakness is accepting necessary compromises.
The data PM:
Number-crunchers & insight-miners.
Data PMs are the ones who actually know if your product is working. They speak in cohorts, funnels, and statistical significance. Every decision must pass its rigorous analysis. "Let's A/B test it" isn't just a suggestion – it's their philosophical outlook on life.
Data PMs bring objectivity and measurement to product decisions. They know what's working, what isn't, and can prove it with charts that make executives nod thoughtfully. Their kryptonite? Sometimes missing the forest for the statistically significant trees.
The accidental PM:
Chaos-navigators & necessity-inventors.
Perhaps the most fascinating species is the Accidental PM – those who never planned to enter product management but somehow ended up responsible for a product's success. They might be former marketing managers, customer support leads, or sales representatives who showed too much interest in how things worked.
What Accidental PMs lack in formal training, they make up for in domain knowledge and stakeholder relationships. They often emerge as informal project managers, providing valuable input from unconventional pathways. They ask the questions others are afraid to ask, mainly because they don't know what they're not supposed to ask.
I began my career as an Accidental PM after complaining too specifically about our product's shortcomings. "Since you have so many opinions," my manager said, "why don't you fix it yourself?" Turns out, throwing someone into the deep end either teaches them to swim or provides valuable lessons about workplace drowning.
The PM ecosystem:
Symbiosis & warfare.
The most successful product teams I've worked with embrace PM diversity. Understanding whether your organization is PM-serviced, PM-guided, or PM-dominated helps navigate these complex dynamics. Technical PMs keep things feasible, Strategic PMs keep things relevant, Designer PMs keep things usable, and Data PMs keep everyone honest.
The taxonomy of PMs might seem academic, but understanding these species and their natural habitats helps us build better products together. And if nothing else, it helps explain why that one PM keeps talking about database indexing during what should be a simple roadmap discussion.
As for me? I'm still unsure which type I am—probably some evolutionary oddity – a product manager who writes articles taxonomising other product managers. Darwin would be baffled.
TAGS:
Keep Reading
ALL POSTS
