By Marty Cagan · svpg.com · LinkedIn
Marty Cagan argues that engineers often make excellent product managers because they understand what is technically possible, and that the move from engineering to product management requires specific mindset and skill shifts. The essay highlights that engineers must stop assuming users think like them, build empathy through direct contact with customers, and shift focus from developer productivity to end-user experience. It also notes the need for humility when user feedback is negative, a different persuasion style than technical debates, and careful handling of relationships with former teammates. Cagan encourages companies to support this career path, since the resulting product managers and even returning engineers gain valuable customer insight.
01Key takeaways
- Your engineering knowledge of what is possible is a real advantage when paired with deep user understanding.
- Never assume users will find or like a product just because you do; test assumptions with real users.
- Optimize for the end-user experience instead of the fastest or most elegant way to build.
- Expect user feedback to humble you, and stay open to learning and handling rejection.
- Build persuasion through evidence and support, since product decisions lack the clarity of technical ones.
- Let the engineering team own technical decisions while you focus on overall product responsibility.
02Key sections
- Why engineers make strong product managers
- Engineers bring a deep understanding of what is currently possible, which becomes powerful when combined with knowledge of users and new product skills.
- Mindset shifts needed
- Engineers must stop assuming users resemble them and must optimize for the end-user experience rather than developer productivity.
- Empathy and humility with users
- Spending face time with customers builds empathy and humility, since users rarely know exactly what they want and often respond differently than hoped.
- Changing how you persuade
- Product decisions lack the objective clarity of technical trade-offs, so former engineers must work harder to build support for their opinions.
- Managing the old engineering team
- Former colleagues may doubt the new PM's technical grounding, so the PM should let the engineering team own technical decisions while participating in discovery.
03From the post
“A partnership dedicated to teaching best practices to product teams and product leaders”
Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.