Lenny's PodcastCamille Fournier: Why PMs lose engineers to credit hoarding
Through ideation invites and shared-credit launches, Camille Fournier: ends 'telephone' loops; rewrites should yield to staged platform migrations.
CHAPTERS
- 0:00 – 0:59
What engineers wish PMs would stop doing: credit hoarding and dismissing details
Camille outlines common PM behaviors that frustrate engineers—especially taking too much credit and treating technical details as irrelevant. The conversation frames these issues as empathy gaps that can damage trust and motivation.
- •PMs often become the “face” of initiatives and accidentally (or intentionally) hoard credit
- •Engineers want their contributions recognized and, at times, represented directly
- •Dismissing details signals lack of respect for how engineering work actually succeeds
- •Even if details feel excessive, patience and curiosity go a long way
- 0:59 – 7:10
Camille Fournier’s background and what this episode will cover
Lenny introduces Camille Fournier’s career across major tech and finance companies and her influential book, The Manager’s Path. He previews the wide-ranging topics: PM–engineering friction, rewrites, management, culture, and platform engineering.
- •Camille’s leadership roles (CTO/VP/Head of Platform Engineering)
- •The Manager’s Path as a guide to engineering management careers
- •Preview of topics: rewrites, one-on-ones, management transitions, platform teams
- •Upcoming book: Platform Engineering
- 7:10 – 8:10
Avoiding the “telephone game”: when PMs become an inefficient middle layer
Camille explains how PMs can fall into a translation role—relaying technical answers they don’t fully understand. She shares when to connect people directly while still protecting engineers’ focus time.
- •“Playing telephone” wastes time and creates information loss
- •If you frequently say “I’ll get back to you,” you may be the wrong interface
- •Direct connections (or small group discussions) can reduce confusion
- •Balance: reducing meeting load for ICs vs. avoiding harmful translation
- 8:10 – 14:07
When PMs hoard ideas, engineers over-engineer: restoring shared creativity
Camille argues that when engineers are excluded from ideation, they seek creativity elsewhere—often through unnecessary technical complexity. The antidote is welcoming engineers into the problem space without PMs feeling threatened.
- •Idea-hoarding can push engineers toward over-engineering as a creative outlet
- •Engineers often want to understand customer and business problems, not just code
- •Strong PMs aren’t threatened by others’ ideas; they curate and refine them
- •Healthy collaboration builds mutual respect for what “the product job” entails
- 14:07 – 20:38
Rewrites are usually a trap: evolution plans beat “build a new system” fantasies
Camille breaks down why big rewrites so often fail: migration is underestimated, legacy behavior is misunderstood, and teams still must maintain the old system. She recommends staged evolutions that uplift the most constrained parts first.
- •Migration time (data, users, APIs) is massively underestimated
- •You must support the old system while building the new one
- •Legacy systems contain undocumented business rules that are hard to replicate
- •Prefer staged, contained re-architectures over all-at-once rewrites
- 20:38 – 28:35
Staying technical as a leader: mastery first, then ask great questions
Camille shares how engineering leaders can remain credible without coding daily. The focus shifts from picking libraries to maintaining deep understanding, asking thoughtful questions, and staying close to strong technical peers.
- •Don’t go hands-off before you’ve built “in your bones” technical mastery
- •Leadership credibility often comes from asking good questions, not dictating tools
- •Surround yourself with smart engineers; stay curious about real operational issues
- •Keep up with tech trends without chasing every fad
- 28:35 – 31:09
Tech fads and context: when frameworks don’t translate (GraphQL, VC-backed tools)
The conversation explores how certain technologies gain popularity despite mixed outcomes in practice. Camille emphasizes evaluating tools by the problem they solve and the organizational context they assume.
- •GraphQL as an example of a popular choice many senior engineers view skeptically
- •Beware “promises” that reduce needed collaboration (e.g., frontend vs backend)
- •VC-funded tooling can create adoption pressure that isn’t aligned with your needs
- •Big-company frameworks may not work without the rest of the big-company context
- 31:09 – 35:56
When engineers should move into management: a years-to-mastery heuristic
Camille advises not to jump into management the moment it’s offered—especially if you want to stay technically grounded. She shares a rough timeline for reaching lasting mastery and why confidence matters for underrepresented engineers.
- •A rough benchmark: ~10 years of serious coding experience (varies by background)
- •Underrepresented engineers may face extra skepticism—internal mastery builds confidence
- •Early management offers may actually be “project management,” not real leadership
- •If you’re still enjoying coding, there’s no need to rush the transition
- 35:56 – 40:31
The biggest surprise of management: you don’t own your time (and it’s a service job)
Camille describes the reality shock many new managers experience: less autonomy, more responsiveness, and influence over authority. Effective management is about serving the team and company, not command-and-control decision making.
- •Managers increasingly lose control of their calendars as scope grows
- •Management is a service job: support, unblock, and enable others
- •Command-and-control kills creativity—tech cultures resist it strongly
- •Leadership is often nudging, setting guardrails, and persuading
- 40:31 – 45:20
Rethinking one-on-ones: keep directs sacred, reduce the rest
Camille challenges the default advice to do 1:1s with everyone. She argues it doesn’t scale, can waste time, and can actually weaken stakeholder alignment by fragmenting feedback into private channels.
- •Weekly/biweekly 1:1s with direct reports and your manager are essential
- •Excess 1:1s with peers/stakeholders don’t scale as org size and scope grow
- •Stakeholder issues can fester when feedback is siloed across private meetings
- •Respect your own (and others’) time: only schedule when there’s purpose
- 45:20 – 51:16
Building a balanced culture: focus over hours, delegate to scale
Camille explains why overwork often masks poor prioritization. She recommends regular time audits, delegating earlier, and deliberately creating boundaries that force clearer thinking about what matters most.
- •Overwork can be an avoidance mechanism for hard prioritization decisions
- •Do regular time audits to remove low-value work
- •Delegation is an investment that enables scale and empowers team members
- •Boundaries (log off times, no weekends) can improve focus and output
- 51:16 – 54:14
Personal productivity mechanics: rituals, deep focus, and avoiding distractions
Camille gets specific about how she maintains focus, from caffeine routines to choosing non-lyrical music. She also reflects on how early-career focus habits helped her build technical mastery faster.
- •Deliberate boundaries can train intensity during working hours
- •Rituals (tea, caffeinated water, lunch soda) as focus cues
- •Quiet environments and non-lyrical music to prevent cognitive interference
- •Less social distraction can translate to more sustained deep work
- 54:14 – 58:03
Working with a platform team when you’re product-facing: collaborate and “PM the platform”
Camille responds to common complaints about platform teams (slow, bureaucratic, unclear ROI). She suggests finding what works, giving concrete feedback, and sometimes stepping in to provide product clarity when the platform team lacks PM support.
- •Many platform teams fail by not listening, not delivering, and not explaining value
- •Avoid “undermining”; instead, collaborate and clarify what you truly need
- •Identify the parts of the platform org that work well and strengthen those ties
- •If there’s no platform PM, product-facing teams may need to provide product direction
- 58:03 – 1:02:42
How to build an effective platform team: composition, product mindset, and measurable impact
Camille outlines what platform engineering should include (real software engineering, not only ops) and why internal platforms must be treated as products. She emphasizes outcome-based goals like cycle time reduction, scalability, and cost efficiency.
- •Platform engineering requires software engineers, not only DevOps/SRE-style roles
- •Platforms are products—product management is essential for coherence and adoption
- •Use outcome metrics: engineering cycle time, scalability blockers removed, cost savings
- •Avoid building “cool stuff” divorced from real internal customer needs
- 1:02:42 – 1:12:42
Platform team fundamentals: what they are, when to form one, and how to thrive on one
Camille defines platform teams (dev tools, CI/CD, infra tooling, shared frameworks, billing/integration platforms) and gives a threshold for when they make sense. She also explains what makes people successful on platform teams: operations excellence, migrations, and stakeholder navigation.
- •Platform teams manage complexity and provide leverage across the business
- •Examples: CI/CD, infrastructure provisioning, internal dev tools, shared frameworks, billing platforms
- •Forming signal: ~50+ engineers, repeated duplicated work across teams, or major scaling pain
- •Success requires operational excellence, migration discipline, and strong stakeholder management
- 1:12:42 – 1:17:02
AI Corner: using AI for rewriting sentences—and why you should never trust its quotes
Camille shares a practical use case for AI: rephrasing awkward sentences during writing. She warns that tools like ChatGPT can hallucinate sources and fabricate quotes, making verification essential.
- •Useful: rephrasing sentences when you know what you mean but not how to say it
- •Less reliable: summarizing long/technical documents without careful prompting
- •Major warning: AI-generated quotes and citations may be completely fabricated
- •Always validate outputs before using them in published work
- 1:17:02 – 1:23:14
Lightning round and closing: books, media, workouts, and where to find Camille
Camille recommends influential books, shares a recent favorite movie, and highlights products and personal mottos. The episode closes with her workout routine, where to follow her online, and how listeners can support her work.
- •Book recs: What Got You Here Won’t Get You There; When Things Fall Apart
- •Favorite recent watch: Alien: Romulus; favorite product: Whoop
- •Mottos: take risks to grow; stay curious and be willing to be wrong
- •Find her on LinkedIn and Medium; support by reading/sharing her books
