The things engineers are desperate for PMs to understand | Camille Fournier (“The Manager’s Path”)
Executive Summary
Camille Fournier joins Lenny Rachitsky to discuss PM-engineer relationships, system changes, technical leadership and meetings. Selected coverage omits overwork and platform-engineering sections. Her observations and management advice reflect her experience, not universal rules. Untimed topics are editorial, not video chapters.
Key Takeaways
Share credit visibly
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
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
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
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
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
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
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 Conversation Breakdown
Share credit visibly
⏱ Untimed topicFournier 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 topicShe 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 topicWhen 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 topicFournier 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 topicShe 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 topicHer 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 topicFournier 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.
Core Frameworks & Ideas
Direct expert communication
Bring the person who can answer the technical question into the conversation rather than relaying uncertain details.
Staged re-architecture
Change contained parts of a system while planning migration and support of the old version.
Purposeful one-on-ones
Protect direct-report and manager conversations while reviewing whether other recurring meetings earn their time.
Actionable Next Steps
- ✓Give engineers visible credit and space to explain their contribution.
- ✓Connect an engineer directly to a stakeholder for a detailed technical question.
- ✓Break a proposed rewrite into stages and estimate migration explicitly.
- ✓Review stakeholder one-on-ones for a clear purpose or a shared-discussion alternative.
Notable Quotes
“The third is playing telephone.”
“They underestimate the time to migrate stuff from the old system to the new system, is a huge, huge problem.”
“You are serving the team, you are serving the company.”
The One Thing to Remember
Respect the engineering work, share the creative process and plan for the costs hidden behind a rewrite or a meeting.