Should Product Managers and Engineers Get Along?
The question of whether product managers and engineers should get along seems to have an obvious answer: yes, of course they should. Collaboration is better than conflict. Professional relationships should be cordial. Two functions working toward the same goal should support each other.
But the obvious answer misses something important about how productive product development actually works. The most effective PM-engineering relationships aren’t characterized by frictionless agreement — they’re characterized by productive tension that produces better outcomes than either party would achieve alone.
Why Some Tension Is Productive
Product managers and engineers naturally bring different perspectives to product decisions, and these perspectives are genuinely in tension in ways that are useful rather than dysfunctional.
Engineers tend to value technical elegance, system coherence, long-term architectural soundness, and implementation quality. Product managers tend to value user outcomes, time-to-market, competitive responsiveness, and business impact. These values genuinely conflict sometimes: the technically elegant solution often takes longer than the user-facing problem requires; the competitive response often requires accepting technical debt that engineering knows will compound.
The tension between these perspectives produces better decisions than either perspective would produce alone. Engineering’s concern about technical debt prevents product decisions that seem commercially attractive in the short term but create the systemic problems that slow development for years. Product’s urgency about user impact prevents the engineering perfectionism that polishes internal architecture while users wait for capabilities they need.
Where Tension Becomes Destructive
The line between productive and destructive PM-engineering tension is crossed when:
Either side stops listening: When PMs treat engineering concerns as excuses for slowness, or when engineers treat product direction as arbitrary interference, the information exchange that makes the tension productive stops. Both sides have domain knowledge the other needs; when either dismisses the other’s expertise, decisions deteriorate.
Blame becomes the default: Product-engineering conflict is often externalized as blame — products that miss their intended impact blamed on engineering execution, or technical debt blamed on product rushing scope. Attribution rather than learning is the symptom of destructive tension.
Authority displaces merit: When “the PM decides” becomes the answer to every product-engineering disagreement, the engineering perspective stops being brought to those conversations at all. The organizational authority of the PM role shouldn’t substitute for the genuine engagement with engineering concerns that good product decisions require.
Building the Productive Partnership
The PM-engineering relationship that produces the best outcomes is characterized by mutual respect for domain expertise, genuine intellectual engagement with each other’s concerns, shared commitment to user and business outcomes, and the psychological safety to raise concerns rather than route around them.
This partnership doesn’t emerge automatically from organizational structure; it’s built through consistent behavior over time — product managers who follow through on commitments, who engage seriously with technical concerns, and who share credit for successes as generously as they share accountability for failures.
Key Takeaways
Product managers and engineers should get along — but “getting along” means productive professional partnership, not frictionless agreement. The tension between engineering’s technical perspective and product’s user and business perspective is generative when both sides engage it honestly. The investment in building this partnership through consistent respect, shared credit, and genuine intellectual exchange pays dividends in the quality of product decisions and the pace of execution that emerge from it.
The Partnership Investment
Building the PM-engineering partnership takes consistent investment over time: following through on commitments, acknowledging engineering concerns even when overriding them, sharing credit for successes, and being candid about failures. None of these behaviors produces immediate relationship dividends; all of them accumulate into the kind of trust that makes the productive tension between product and engineering orientation a genuine organizational strength rather than a constant friction.