Lenny's PodcastWhat happens after coding is solved? | Fiona Fung (Claude Code and Cowork)
CHAPTERS
Fiona Fung’s journey: from IBM terminals to Visual Studio dogfooding
Lenny introduces Fiona Fung and frames the conversation around the dramatic productivity jump from AI-assisted coding. Fiona recounts early career shifts—IBM’s low-level systems work and Microsoft’s IDE revolution—and how dogfooding shaped her product instincts.
When coding stops being the bottleneck: verification becomes the new constraint
Fiona explains why the core bottleneck has moved from writing code to verifying correctness and impact. The team’s challenge is less about generating output and more about ensuring quality, reliability, and user experience across fast-moving surfaces.
What an “AI‑pilled” team looks like in 2026: roles blur into builders
Fiona describes the emerging team model where nearly everyone becomes a “builder,” and traditional role boundaries fade. Management practices shift toward enabling autonomy, scaling feedback, and maintaining clarity on outcomes.
Claude as a manager’s operating system: visibility, retros, and coaching via a shared agent
Fiona details how she uses Claude Code as a persistent session with access to repos, Slack, and metrics to review team output and drive better conversations. Monthly look-backs become richer: what shipped, how it performed, what broke, and what to improve.
From manual feedback sweeps to automated routines: the rise of async agent workflows
Fiona explains how “routines” (cron-like automation) changed her daily ritual of scanning feedback channels. Instead of summarizing issues manually, routines can summarize themes and even propose PRs, pushing work toward an asynchronous, agent-driven operating model.
Code review evolves: frameworks, specs-in-repo, and AI validation against “what good looks like”
With human review becoming a bottleneck, Fiona emphasizes encoding standards and expectations into repos so AI can review against them. This extends test-driven thinking and makes quality checks more scalable as output explodes.
Hiring for the AI era: creative product builders + deep systems experts
Fiona shares the two profiles Anthropic prioritizes: end-to-end builders with product sense and deep subject-matter experts for critical systems. AI increases what generalists can do, but verification and hard infrastructure still demand real expertise.
Ambition, growth mindset, and fear: who thrives vs. who resists
The conversation shifts to mindset: ambitious thinking becomes the differentiator when “everything is possible in theory.” Fiona highlights growth mindset and leaning into fear as key traits for adapting, and shares personal stories about taking control amid uncertainty.
Bridging the AI adoption divide: helping small businesses and spreading practical use cases
Fiona explains her passion for small businesses and how Cowork can remove painful admin work like invoicing and expenses. She argues adoption spreads best through concrete, relatable examples and hands-on help, especially for those hesitant about AI.
How Anthropic spots latent demand: watching “people jumping through hoops”
Fiona describes the product pattern of noticing unexpected usage and turning it into a first-class experience. Latent demand emerges when users hack around limitations; teams should form hypotheses and smooth the workflow rather than fight the behavior.
Agency with accountability—and the shift from token maxing to outcome/ROI measurement
Fiona emphasizes a team culture of high agency paired with high accountability, grounded in hypotheses and measurable outcomes. She critiques shallow productivity metrics and argues for aligning outputs to real outcomes, using metrics as tools—not targets.
Quality at scale: proactive monitoring and the “bad vs. sad” framework
To manage quality amid high velocity, the team invests in proactive detection and shared language. “Bad vs. sad” helps teams classify irrecoverable failures vs. recoverable pain points, enabling consistent prioritization across disparate surfaces.
Why managers start as ICs: dogfooding, credibility, and preventing skill atrophy
Fiona explains Anthropic’s preference for managers to begin as individual contributors and continue hands-on work. Staying in the flow improves product intuition, builds rapport, and helps leaders understand rapidly changing tools and codebases.
What’s lost (and what’s next): loneliness, context switching, changing PM/data science, and JIT planning
They discuss tradeoffs: less classic “flow,” more loneliness, and heavier context switching with many async agents. Fiona highlights evolving PM and data science roles, open questions about automated review and org structure, and a move from roadmaps to monthly just-in-time planning.
