blog / engineering-manager-product-manager
8 Tips for Engineering Managers Working with Product Managers
8 tips for engineering managers working with product managers — shared priorities, healthy tension, and a partnership that ships without the blame game.
- product
- stakeholders
- collaboration
The engineering manager–product manager relationship can be the best lever on the team — or a weekly blame ritual. Partnership beats turf. Here’s how to make it work.
Healthy EM–PM partnerships still require saying no as an engineering manager when capacity is real.
1. Agree on decision rights out loud
Who decides problem priority, sequencing, technical approach, quality bar? Ambiguity creates passive-aggressive Slack. Write a lightweight RACI and revisit quarterly.
2. Share one prioritization board
Features, debt, incidents, experiments — same view. Separate secret lists guarantee conflict. Argue on one page.
3. Bring constraints early, not at commitment time
Hiring ramp, on-call load, migrations, unknowns. Surprising product in week 5 of a sprint is how trust dies. Be the early-warning system.
4. Translate tech into customer and business language
“Refactor the monolith” loses. “Cut checkout incidents 50% so we can ship pricing experiments safely” wins. Speak outcomes.
5. Co-own discovery, don’t wait for tickets
Sit in research when it matters. Offer technical options during shaping. EMs who only take orders get treated like a ticket factory.
6. Protect healthy tension — kill contempt
Push on scope; let them push on urgency. Mocking “product doesn’t understand” in engineering channels poisons the well. Disagree in private; align in public.
7. Run a weekly EM/PM sync with teeth
Risks, sequencing, staffing, open decisions. Twenty-five focused minutes beats a chaotic standup cameo.
8. Celebrate joint wins to the org
When you ship, tell the story as a pair. Shared credit builds shared responsibility next time something slips.
When capacity fights get heated, lean on prioritization, say-no scripts, and an explicit tech-debt budget — process beats personality clashes.
Frequently asked questions
- Who should own the roadmap — EM or PM?
- Product usually owns problem/opportunity prioritization; engineering owns how and what’s feasible. The best pairs co-create a roadmap neither would write alone.
- How do I push back on unrealistic dates?
- Bring ranges, risks, and tradeoffs — not vibes. Offer a cut scope that hits the date, or a date that hits the scope. “No” without options feels like obstruction.
- What if my PM and I just don’t get along?
- Align on working agreements: decision rights, communication cadence, how conflict gets resolved. If respect is gone, escalate early — the team pays for your cold war.
Related posts
More in Prioritization & delivery
- 8 Ways to Prioritize Software Engineering Work When Everything Is Urgent
8 ways engineering managers prioritize software engineering work when everything is urgent — impact vs effort, kill lists, saying no with options, and protecting focus.
- 9 Ways Engineering Managers Can Say No Without Killing Trust
9 ways engineering managers can say no without killing trust — protect capacity, offer tradeoffs, and keep stakeholders as partners.
- 8 Ways Engineering Managers Can Prioritize Technical Debt
8 ways engineering managers can prioritize technical debt — sell it to product, pick high-leverage fixes, and stop the backlog from becoming a graveyard.