Why Engineer Voices Don’t Get Heard — Practical Tips for Engineers to Influence Product Decisions
summary
How engineers can influence product decisions by framing technical arguments so they’re explainable to stakeholders like managers, executives, and other departments. It covers practical tactics—preparing proposals proactively, surfacing conflicts early, focusing on objectives, anticipating stakeholder concerns and roadmaps—and explains the product manager perspective to help engineers communicate proposals that PdMs can justify and act on.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 2:21Engineer vs PDM roles
- 5:08Engineer voices unheard
- 9:07Understanding PDM context
- 10:11PDM context traits
- 16:04PDM blind spots in engineering
- 17:47Mindset and resistance
- 20:59Act without waiting
- 23:50Escalate early discomfort
- 25:39Align on shared goals
- 28:31Debating opinions
- 30:22Communicate broadly
- 34:37Propose and delegate
- 37:49Summary and techniques
- 39:55Q&A
related talks
34mHow Engineers can Influence Other Engineers and PMs
29mHow to Become a Great Engineering Manager
31mFrom Engineer to Engineering Manager
15mIt Works on My Machine: Why Engineers Are Misunderstood (and What They Can Do About It)
25mBeyond Code: The Power of Thought Leadership in Engineering
42mHow engineering managers can lead with visibility
17mThe Industry Standard hoax: How Engineers Can Steer Product Decisions
42mThe Art of Engineering Diplomacy - Driving Significant Changes in Large Org.