AI agents have long promised productivity gains, but until now, they demanded coding skills that most agile practitioners lack or are uncomfortable with. In this article, I share my first impressions on how Claude Cowork removes that barrier, why it is a watershed moment, and how you could integrate AI Agents into your work as an agile practitioner.
The A3 Framework categorizes AI delegation before you prompt: Assist (AI drafts, you actively review and decide), Automate (AI executes under explicit rules and audit cadences), or Avoid (stays entirely human when failure would damage trust or relationships). Most AI training teaches better prompting. The A3 Framework teaches the prior question: Should you be prompting at all? Categorize first, then prompt.
Welcome to the 526th edition of the Food for Agile Thought newsletter, shared with 35,788 peers. This week, Ethan Mollick and Teresa Torres unpack how Claude Code’s agentic architecture and workflow primitives hint at a new era of autonomous work: powerful, yet risky in practice. John Cutler and Randy Silver challenge teams to stop copying frameworks and start fixing the organizational rules that shape product behavior, while Stephanie Leue highlights why speed stalls when finance, structure, and decision rights stay frozen. Also, Barry O’Reilly and Annie Duke close with lessons on judgment, attention, and decision hygiene.
Next, Teresa Torres lists 2026 product conferences and asks readers to add missing events. Peter Yang shares 25 product beliefs that favor user contact, ruthless focus, and shipping over process theater, and Jaclyn Konzelmann outlines AI-era principles that build agency, intuition, and clear thinking. Mike Fisher warns that culture debt compounds when leaders trade trust for speed, plus Daniel North reframes performance issues as system signals and pushes calm, incentive-aware technical leadership.
Then, Nathan Furr and Andrew Shipilov argue that AI pilots fail when teams pursue scattered experiments rather than customer value, and they call for disciplined tests that scale through empowered cross-functional teams. Andi Roberts reframes silent meetings as social risk or overload and shows how leaders can make speaking up safer, and Christina Wodtke explains how OKR key results force clarity and can legitimize joyful work. Also, Anh-Tho Chuong breaks down AI-driven SaaS pricing. Finally, Aakash Gupta and Pawel Huryn show PMs how to use n8n for automations and agents.
Without a decision system, every task you delegate to AI is a gamble on your credibility and your place in your organization’s product model. AI4Agile’s A3 Framework addresses this with three categories: what to delegate, what to supervise, and what to keep human.
Learn more about what is coming in Q1 of 2026.
🎉 Happy 2026 and welcome to the 525th edition of the Food for Agile Thought newsletter, shared with 35,782 peers. This week, John Cutler warns product operating model failures when artifacts replace enabling conditions, while Stephanie Leue shows how reactive overload blocks real product work. Itamar Gilad critiques Google’s drift toward output over learning. Andrej Karpathy tracks 2025 LLM shifts reshaping who builds software, and Janelle Teng Wade examines AI’s power-law economics and fragile bets. Also, Mike Fisher uses Nokia to show how relentless change overwhelms the capacity for absorption and judgment.
Next, Marty Cagan and Elias Lieberich describe Google’s product model built on empowered teams, discovery, and outcomes at scale. Ant Murphy surveys 2026 product shifts and urges PMs to strengthen strategy and business judgment amid noisy AI adoption. Stephane Derosiaux questions AI productivity claims outside greenfield work, while Teresa Torres shares how she deliberately uses Claude Code, even for non-coding tasks. Andi Roberts distills Adam Kahane’s view of change through habits, experiments, and relationships.
Then, Johanna Rothman argues that culture shifts through stories, experiments, and flow metrics that improve decisions, not activity counts. Kevin Kelly reframes data as a commons that gains value through connection and shared governance, Sean Goedecke shows how complexity erodes system understanding over time, and Rich Mironov urges product leaders to speak in revenue terms. Finally, Jenn explains why sustainable meetups depend on organizer energy, clear norms, and intentional culture design.
Organizations resist change through immune responses: encapsulation, assimilation, exhaustion, redefinition, and expulsion. But immune systems attack what they recognize. Hence, if you are in the business of change and expect push-back, stop announcing transformations. Instead, to overcome the immunity response, start solving problems: The principles spread through practice, through demonstrations of value, not by proclamation.
This article is Part 3 of a three-part series. In Part 1, Agile Is Dead, Long Live Agility, we saw how the Agile brand became toxic while the principles spread faster than ever under different names. In Part 2, The Reformation That Became the Church, we traced how every disruptive movement hardens into the orthodoxy it opposed.
This final part answers the question we left open: Can you practice the principles without the apparatus? Yes. But only if you understand why organizations reject change and how to stop triggering that rejection.
