The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”) — Lenny's Podcast: Product | Career | Growth Summary

The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”) — Lenny's Podcast: Product | Career | Growth Summary | Galaxy of Podcasts

The Conversation Breakdown

Share credit visibly

⏱ Untimed topic

Fournier says engineers can feel overlooked when the front-facing PM receives the attention for a shared project. Give engineers chances to explain their contribution and name the work they did. She treats this as a two-way relationship, not a claim that only PMs create friction.

Respect details without needing to know every one

⏱ Untimed topic

She argues that engineering depends on details, and dismissing them as irrelevant shows a lack of empathy. A broad-view leader need not understand everything to ask useful questions. Be patient while separating a meaningful constraint from a detail that may not affect the decision.

Avoid becoming a telephone relay

⏱ Untimed topic

When a question needs technical expertise, she warns against repeatedly carrying answers between the engineer and the original asker without understanding them. Connect the right people directly when useful. Occasional coordination is normal; an inefficient relay should not become the default.

Keep engineers in the creative loop

⏱ Untimed topic

Fournier says excluding engineers from product ideas can push their creative energy into unnecessary technical complexity. Invite their ideas about the product rather than reserving all decisions for the PM. Her observation is a hypothesis to consider, not a universal explanation for over-engineering.

Stage system changes and budget for migration

⏱ Untimed topic

She accepts that major re-architecture is sometimes needed, but favors contained stages where possible. Migration and support of the old system add work beyond building the replacement. A plan should include those costs rather than assuming a long feature freeze solves everything.

Build technical mastery before stepping away

⏱ Untimed topic

Her advice to aspiring leaders is to stay hands-on until there is a durable baseline of skill. Later technical leadership can involve understanding the work and asking good questions rather than choosing every library. This is her guidance, not a fixed qualification rule for all managers.

Treat management as service and protect meeting time

⏱ Untimed topic

Fournier says managers serve the team and company rather than simply gaining control of their time. She protects one-on-ones with direct reports and her manager but questions recurring one-on-ones with every stakeholder. Shared discussions may expose differing views more efficiently than isolated updates.

The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”)

Executive Summary (TL;DR)

Key Takeaways

Share credit visibly

Respect details without needing to know every one

Avoid becoming a telephone relay

Keep engineers in the creative loop

Stage system changes and budget for migration

Build technical mastery before stepping away

Treat management as service and protect meeting time

The Conversation Breakdown

Share credit visibly

Respect details without needing to know every one

Avoid becoming a telephone relay

Keep engineers in the creative loop

Stage system changes and budget for migration

Build technical mastery before stepping away

Treat management as service and protect meeting time

Core Frameworks & Ideas

Direct expert communication

Staged re-architecture

Purposeful one-on-ones

Actionable Next Steps

Notable Quotes

The One Thing to Remember