The Product, Design, and Engineering Venn
The most useful one-picture answer to "what is a PM" is three overlapping circles, Product, Design, and Engineering, with the PM sitting in the middle. It is a cliche diagram for a reason. It is right. But almost everyone reads it wrong. The middle is not where you do a third of each discipline's job. The middle is where the trade-offs live, and the PM's job is to own the overlap, not to be a mediocre designer and a junior engineer at the same time.
#What each circle owns
- Engineering owns "can we build it, and how": feasibility, architecture, the cost of the work.
- Design owns "can people use it, and should it feel this way": usability, interaction, craft.
- Product (you) owns "should we build it, and is it worth it": value to the user and viability for the business.
Each discipline has a circle of genuine authority. You do not overrule your tech lead on architecture or your designer on interaction patterns, any more than they overrule you on what is worth building. Respecting the circles is what earns you the right to stand in the middle.
#The PM owns the overlap
The overlap is not empty space. It is the hardest space. It is where "the cleanest design" meets "a six-week build" meets "a feature only 4% of users want." Someone has to hold all three truths at once and decide. That someone is the PM. Teresa Torres calls the PM, design, and engineering unit the product trio and argues the three should discover together. I agree, with one caveat. Discovering together does not dissolve accountability. When the trio cannot agree, the PM owns the call on what is worth building, the designer owns how it works, and the tech lead owns how it is built. Shared discovery, clear ownership.
The Product and Design overlap specifically is richer than people think. In my experience it is where service design, information architecture, research synthesis, stakeholder facilitation, concept modeling, and the writing of user stories actually happen. That work belongs to neither discipline cleanly, and a good PM and a good designer do it together. See User Experience Design and Design Sense and Critique for where my circle and design's circle genuinely blend.
#The center is trade-offs
This is the whole point, so I will say it plainly. The value you add in the middle is making the trade-offs nobody else is positioned to make. Engineering optimizes for feasibility and maintainability. Design optimizes for usability and craft. Both are right to. Left alone, each would build a different product. The PM is the only seat with the full context (user value, business viability, technical cost, design quality), and therefore the only seat that can make the call across all four. That maps directly onto The Four Big Product Risks: value and viability are yours, usability is design's, feasibility is engineering's.
- The wannabe specialist. Tries to be a part-time designer and part-time engineer, redlines mockups, writes pseudo-code. You will be worse than the specialists and you will insult them. Stay in your circle and own the overlap.
- The empty middle. Sits in the center and just relays messages between the other two circles, a router rather than a decision-maker. That is a facilitator, not an owner. The center is where you decide, not where you forward.
#Continue Reading
- Understanding Trade-offs for the act that the center of the Venn actually consists of.
- The Four Big Product Risks for the formal version: which circle owns which risk.
- Cross-Functional Collaboration for running the trio so shared discovery does not blur ownership.
- Product Manager vs Adjacent Roles for why owning the overlap is not the same as doing the other roles.
- Design Sense and Critique for where the Product and Design circles legitimately blend.