Product Management: Foundations to Practice · Working with Design and UX
The PM-Designer Relationship
The most common design collaboration failure is not disagreement, it is sequencing: bringing a designer in after the problem has already been solved on paper. This chapter covers how to avoid that.
Product managers and designers share responsibility for the customer experience but approach it from different angles: a PM typically focuses on which problem is worth solving and why, while a designer focuses on how the solution should look, feel, and behave for the person actually using it. Both perspectives are necessary; a PM without design input can define a technically correct problem with a solution nobody can comfortably use, while a designer without clear problem framing can produce a beautiful interface for the wrong underlying problem.
- PMs and designers approach the same problem from different angles; both perspectives are necessary, not redundant.
- Involving a designer only after the solution is already specified wastes their most valuable contribution.
- The product trio model has PM, designer, and engineer jointly conduct customer interviews to share the same raw evidence.
- Genuine PM-designer disagreements should be resolved with evidence and testing, not by organizational seniority.