SVPG · Free post · Execution, roadmaps & process · Communication & influence

Product Management vs. Engineering

Marty CaganOct 31, 20073 min
SourceSVPG
KindFree post
PublishedOct 31, 2007
Originalsvpg.com ↗
N:

Cagan argues that a great product comes from pairing a real customer need with a solution that has just become technically possible, which makes the product manager and engineer relationship critical. He frames the two roles as peers: the PM defines the right product, while engineering builds it right, and each needs the other. He offers concrete ways each side can help the other, such as bringing engineers into user testing and early discovery, and PMs keeping scope minimal, limiting churn, and answering questions quickly. The piece matters because a strained PM-engineering relationship makes product work miserable, while a strong one improves both the product and the team.

01Key takeaways

  • Treat engineering as a peer partner, not a subordinate, and respect their ownership of building the product well.
  • Bring engineers into customer visits and prototype testing so they see user struggles and generate better solutions.
  • Involve a lead engineer early in discovery to get rough cost estimates before committing to an idea.
  • Define the smallest product that meets your goals rather than the ultimate product, to keep scope manageable.
  • Avoid introducing new ideas mid-build, since requirement churn hurts the team and the product.
  • Answer implementation questions as fast as possible to keep the team moving.

02Key sections

Why the relationship matters
A great product combines a real customer need with what is newly possible, so the PM and engineering partnership is central to success. Strained relationships make the PM's job very hard.
Treat each other as peers
PMs and engineers each own a critical half, defining the right product versus building it right. Neither should see themselves as subordinate, and each should give the other room to do their job.
How engineers can help the PM
Engineers can join customer and prototype sessions, explore emerging technologies, and take part early in discovery to estimate costs and find better solutions. Throwing a finished spec over the wall delays the critical negotiation.
How the PM can help engineers
PMs should focus on the minimal product that meets the goals, reduce churn once building starts, and respond quickly to implementation questions. Late new ideas disrupt the team.
Encouraging engineers into product management
Cagan encourages top engineers to try PM work, since great engineering needs something worthwhile to build. Many strong products were created by engineers who understood what was possible.

03From the post

“A partnership dedicated to teaching best practices to product teams and product leaders”

“One key to this relationship is to each be very clear that you are peers.”Marty Cagan · SVPG
“One of the most common mistakes that product managers make is to come up with some great product definition, and then throw it over the…”Marty Cagan · SVPG
“Remember your job is not to define the ultimate product, it’s to define the smallest possible product that will meet your goals.”Marty Cagan · SVPG

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.