The Product Manager and Engineering Partnership
The relationship between product management and engineering is one of the most important partnerships in a technology organisation. When it works well, it produces focused, efficient delivery of valuable features. When it doesn't, it produces a contested, slow, and demoralising environment where neither discipline functions effectively.
The PM Role (Engineering Perspective)
Product managers own the "what and why" — defining what to build based on customer needs, business strategy, and market context. Engineers own the "how" — defining how to build it with quality, reliability, and maintainability. This division of responsibility is productive when each side respects the other's domain and the boundary is genuinely collaborative rather than adversarial.
Where PM-Engineering Friction Comes From
- PMs who over-specify implementation — defining "how" when they should define "what"
- Engineers who under-appreciate business context — treating all technical work as equally important regardless of business value
- Scope creep and specification changes mid-sprint without renegotiation
- Technical debt vs features tension — PMs constantly pushing features, engineers wanting refactoring time
- Estimation disagreements — unrealistic business deadlines meet engineering time reality
Building a Strong Partnership
Strong PM-engineering partnerships share these characteristics: genuine mutual respect; shared product context (engineers understand the customer and business); collaborative discovery (engineers in customer interviews and user research); transparent technical constraints communicated early; joint ownership of quality; and regular structured reflection on what's working and what isn't.