What are the key takeaways from “Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)” on Lenny's Podcast: Product | Career | Growth?

Frequently asked questions about “Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)”

What is "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)" about?

In "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)" (Lenny's Podcast: Product | Career | Growth, June 2026), software engineering has fundamentally shifted from manual code creation to high-velocity AI-assisted building. Leaders must now prioritize…

What does "Just-in-Time (JIT) Planning" mean in "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)"?

In "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)", Because the technological landscape moves so fast, six-month plans become obsolete almost immediately. JIT planning keeps the team focused on immediate priorities, checking in weekly to ensure…

What does "High Agency, High Accountability" mean in "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)"?

In "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)", With AI tools removing blockers, anyone can build anything. To prevent chaos, every action must be backed by a clear hypothesis for what problem it is solving.

What does "Bad vs. Sad Framework" mean in "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)"?

In "Building the most AI-pilled engineering team in the world | Fiona Fung (Manager of the Claude Code and Cowork Teams)", This allows teams to prioritize effectively. While bad errors demand immediate action, tracking 'sad' moments prevents a slow accumulation of friction that eventually leads to user churn.

What is this episode about?

Software engineering has fundamentally shifted from manual code creation to high-velocity AI-assisted building. Leaders must now prioritize verification, system architecture, and cultivating high-agency teams while managing the new risks of async agent-based development.

What are the key takeaways?

• Coding is no longer the primary constraint; the bottleneck has shifted toward system verification and product sense. — Teams must stop measuring productivity by lines of code and start measuring it by business outcome and product quality.