Lenny's Podcast · Jun 21, 2026
Fiona Fung, head of Claude Code and Co-work at Anthropic, argues that coding is no longer the bottleneck — the new constraint is ambition, verification, and accountability. The episode covers concrete practices her team uses to manage 8x productivity increases: async agent routines, spec-driven code review, bad/sad quality frameworks, and manager-as-IC onboarding.
AI coding tools have made writing software fast enough that the new bottleneck is the ambition and vision of the person directing the work.
As a PM, your ideas are no longer gated by engineering bandwidth. This means the quality of your product thinking — not your ability to get things on the roadmap — becomes the primary constraint. Teams that don't raise their ambition will under-use their new capacity.
It's like switching from hand-mixing concrete to a cement truck: the pour speed is no longer the problem — now you need a bigger blueprint.
Instead of relying on human reviewers to hold the quality bar, you write down what "good" means as a spec in the repo, and the AI validates every PR against it automatically.
At high velocity (8x code output), human reviewers become a bottleneck for quality, not just throughput. This approach lets quality scale with output without proportionally scaling reviewer headcount. For a PM, it also forces the team to make implicit standards explicit — a governance benefit.
It's like a linter, but instead of syntax rules, you're enforcing product and design principles.
Instead of tracking raw performance numbers, teams classify every quality issue as either 'bad' (irrecoverable, e.g., crash) or 'sad' (recoverable but painful, e.g., flicker) to make cross-team quality conversations tractable.
In a high-velocity environment with many surfaces, dashboard numbers without context are hard to interpret. This framework lets leadership zoom out and see the overall experience health without drowning in metric debates. It also gives each team ownership (high agency) while maintaining a common language.
It's like a hospital's triage system: not every problem needs immediate surgery, but the nurses all use the same severity scale.
Instead of a manager manually scanning Slack channels and dashboards each morning, a scheduled agent does it overnight and delivers a curated summary plus draft fixes ready for review.
At 8x code throughput, a manager physically cannot review everything manually. This is how you stay informed without becoming the bottleneck. For product leaders in complex orgs, this pattern generalizes: any recurring information-gathering ritual is a candidate for automation.
It's a night-shift analyst that reads everything while you sleep and leaves a briefing on your desk.
Freedom to build anything must be matched by personal ownership of whether it actually worked — the two are non-negotiable as a pair.
In AI-accelerated teams, the risk isn't under-shipping — it's shipping a lot of the wrong things fast. This principle is a lightweight governance mechanism that scales better than process-heavy review gates. As a PM, this is how you maintain strategic coherence without micromanaging.
It's like giving someone the keys to the company car — but only after they've filed where they're going and why.
New managers join as ICs first, building real product knowledge and team rapport, before picking up their management responsibilities.
In AI-accelerated engineering orgs, a manager who can't evaluate code quality or understand the product deeply is flying blind. This practice ensures managers can do meaningful verification work — not just status meetings. It also signals to the team that leadership is earned through contribution, not title.
It's the chef who works every station in the kitchen before becoming head chef — they earn the title by knowing the work.
When people jump through hoops to use your product in a way you didn't design for, that workaround is a product roadmap item in disguise.
Latent demand signals are pre-validated — users are already spending effort on the behavior without being asked. For a PM in a fast-moving space, these signals are higher-confidence than surveys or interviews. Co-work (Claude's knowledge work product) was reportedly discovered this way.
It's like finding a desire path in a park — the worn grass where people cut across tells you where the real path should be paved.
High output metrics — code shipped, tokens consumed, PRs merged — can all be moving fast while the product is going nowhere meaningful.
This is a direct challenge to how most teams are currently measuring AI ROI. If your engineering productivity dashboard tracks PR velocity or AI tool adoption rates, you may be measuring the wrong things. The Facebook Marketplace anecdote (number of sellers vs. power sellers) is a concrete illustration of how proxy metrics drift from outcomes.
It's like measuring a sales team by calls made instead of deals closed — busy, but possibly going nowhere.
When every engineer works solo with their own AI agent all day, team knowledge stops flowing — scheduled pair sessions are a structural fix.
This is an early signal of a new management problem: AI-accelerated teams may ship more but lose the informal knowledge transfer and social cohesion that previously happened naturally around shared code. As an engineering leader or PM, this is a culture and retention risk, not just a productivity concern.
It's like reinstating the office water cooler after everyone went remote — the work still gets done, but the side-channel learning disappears without a structural replacement.
AI tools are erasing the functional separation between engineering and product, making every team member responsible for both building and thinking about impact.
This has hiring and org design implications. The clean separation of PM/Engineering/Design that most enterprise orgs rely on is being disrupted. Your next team structure may need to optimize for product engineers and creative builders rather than functional specialists. It also changes what skills to screen for in interviews.
It's like the difference between a restaurant with strict kitchen stations vs. a food truck where everyone does everything.
Your team is about to 8x its output — are you ready for what breaks next?
The bottleneck has shifted from shipping code to verifying it, directing it, and measuring whether it mattered. If your processes (code review, quality monitoring, roadmap prioritization) were designed for human-speed output, they will not survive AI-speed output.
The role of PM is being redefined in real time at the most AI-native company on earth.
PMs at Anthropic now commit code. Engineers own product outcomes. This is not a future prediction — it is current practice. The skills, hiring profiles, and org structures this implies are directly applicable to B2B and enterprise product teams building with AI.
The social and cultural consequences of AI-first engineering are arriving before anyone has solutions.
Isolation, skill atrophy, and metric drift are emerging problems on the team that builds Claude Code. The patterns Fiona describes — pairwise lunches, IC onboarding, spec-driven review — are early experimental responses worth adapting before the problems arrive in your org.
Everything is now possible in theory. Now, it's about how ambitious can you be?
Crystallizes the central thesis of the episode in one sentence — the constraint has shifted from capability to vision.
don't forsake motion for progress. Um because if you're measuring like, you know, like tool user usage, then you're you're measuring the action, but is it really making whatever the end outcome of yours like important?
Direct challenge to how most teams are currently measuring AI ROI — highly relevant for anyone building AI productivity cases for stakeholders.
we say with high agency is also high accountability. So, it's all about making sure folks have that freedom to code. But, then it's also like, okay, what's the accountability for it? What's the hypothesis of what you're trying to solve?
The most operationally concrete org principle in the episode — applicable directly to team operating models.
it could start being a lonely experience cuz we all started just working with our agent so much. And on the Claude Code team, recently, we started up pair-wise programming lunch.
First-hand evidence of a new cultural failure mode in AI-first teams, with a concrete mitigation — not theoretical.
whatever metric whether for productivity or even for product, always keep an eye and make sure that you're not just having blinders on that's blindly following a metric that used to make sense cuz sometimes the landscape can change so fast.
Applies equally to product metrics and AI productivity metrics — warning against metric inertia in fast-changing environments.
the more that we can automate to almost check in the framework for what good looks like. Claude is very good when you give it a framework to validate against those frameworks.
The core insight behind spec-driven AI review — actionable immediately for any team using AI-assisted code review.