With both dimensions understood—work modes and product types—you can map your specific context to capability requirements.

Start by assessing your strategic situation. What mode of product work dominates your current needs? Is your priority finding PMF for a new initiative, optimizing growth for an established product, building features that deepen retention, or creating infrastructure for scale?

Then consider your product type. Where does complexity live? What makes your product hard to build well? Domain expertise, technical architecture, data science, user experience, go-to-market motion?

The intersection points to the skills that matter most. A vertical SaaS company focused on PMF expansion needs PMs with deep domain expertise and tolerance for ambiguity. A data-heavy product in growth mode needs PMs with statistical rigor and experimentation skills. An enterprise platform in scaling mode needs technically deep PMs who can partner with infrastructure engineering.

The corollary is that skills outside this intersection, while valuable, are secondary. Hiring for the wrong profile—even if the individual is excellent—creates friction. A growth-oriented PM in a context that requires patient feature work will push for experiments that don't fit. A consumer PM in an enterprise context will underweight stakeholder management.

There is no perfect PM. There is only the right PM for your current context. Understanding that context clearly is the first step toward building the right team.