Lenny's Podcast Summaries & Notes

The Need for Lab Teams

• Every company needs a dedicated team operating at the technological frontier.
• This team must experiment with the latest models to identify new possibilities before competitors.
• Labs teams require independence from existing business units to thrive.

Idea Generation and Innovation

• The best ideas rarely come from structured sessions like design sprints.
• Ideas often emerge organically from individuals passionate about side projects.
• Focus on interesting people and their side projects to foster innovative chemistry.
• Cultivate a space where "weird things can grow."
• Maintain an "always on" alert for novel concepts and opportunities.

Identifying Opportunities

• Track "what's almost possible" and identify when a technology crosses into "now possible."
• Look for emerging behaviors and trends, venturing beyond typical innovation hubs.
• Develop a point of view about the future, understanding that many predictions will be wrong.
• Match technological possibilities with compelling user problems and monetization potential.

Product Market Fit and Decision Making

• In early stages, product market fit is indicated by user engagement (e.g., "eyes lighting up").
• Fall in love with the problem, not the product, to navigate necessary pivots.
• Teams often sense when an idea isn't working before leadership does.
• Foster a culture where teams feel empowered to call out ideas that aren't working.

Valuable Skills and Team Dynamics

• Unlearning rate is crucial: how quickly someone can learn and then discard outdated information.
• Explosive endurance: the ability to perform intensely over sustained periods.
• Collaboration is key, especially bridging human and AI agent interactions.
• Building and scaling trust is fundamental for effective collaboration.
• PMs are adept at simulating other functions, a skill amplified by AI.

AI and Future Outlook

• The future of entertainment is a key area of exploration.
• Messaging and chat spaces are ripe for disruption.
• Addressing scarce resources like time and money presents opportunities.
• Model benchmarks are overhyped; focus on practical utility and product value.
• Underhyped: industry-wide discussions on principles and values in AI development.
• Google is working on personal, proactive, and powerful AI assistants.

Organizational Structure and Lab Teams

• Labs need independence, reporting at a distance from core business units.
• Define the lab's goal: graduating products or inventing new categories.
• Labs can challenge company processes and ways of working, creating "good trouble."
• Distinguish between zero-to-one, one-to-ten, and ten-to-hundred labs, each with different challenges.
• Avoid consolidating too early; embrace messiness in organizational design.
• Hiring too many people too fast can be a detrimental vanity metric.

Recognition and Culture

• Award "TPU Harvesters" for efficiency with a miniature rake.
• Recognize "paper cut" fixers with a golden band-aid.
• Celebrate "LLM Whisperers" who push model frontiers with a giant set of ears.
• Conduct surprise "good meetings" with leadership to express appreciation for valuable team members.

Future of AI and Internet Interactions

• The majority of internet actions will be performed by agents.
• Products need to be built for agent success and scale.
• The trend is towards a system that learns, rather than manual loop configuration.
• AI will provide a permanent, active intelligence available through any client or screen.
• The goal is to break free from technology and have it work seamlessly for humans.

OpenAI's Product Evolution

• Dots is positioned as the primary way to interact with AI, an intelligent agent that works 24/7, learns preferences, and understands goals.
• ChatGPT will merge capabilities from work toggles and consumer chat for a simpler experience.
• Eventually, all Dots capabilities will be integrated into ChatGPT.
• The focus is on removing model pickers and simplifying user configuration.
• An open ecosystem with partner integrations ("Sign in with ChatGPT") and plugin revenue sharing is a key focus.

Skills and Work Culture Shifts

• Typing fast is a trending-down skill; great taste, user focus, and building passion are trending up.
• Founders and those with a "build it" mentality are highly valued.
• Roles are blurring, allowing individuals to leverage diverse skills.
• Autonomy and trust are central to OpenAI's culture, enabling rapid iteration.
• The promise of AI is to reduce noise and allow focus on important tasks, not just increased output.

AI Development and Safety

• OpenAI invests heavily in alignment, safety, and security alongside model capabilities.
• Significant compute resources are dedicated to monitoring AI agents.
• The company prioritizes safety and will not release capabilities they deem too risky.
• There is an optimistic view on solving AI alignment and safety challenges.

User Experience and Future Vision

• The ultimate goal is extreme simplicity, removing user fatigue from model picking and complex reasoning.
• The ideal interaction will be natural, conversational, and integrated into physical spaces.
• AI should empower creativity and serve as an artistic tool, rather than replacing human value.
• New grads and younger generations have an advantage due to their rapid learning and embrace of new technology.

The Evolving Role of Product Managers

• The core job of a PM is to bridge real-world problems with technology, but the pace of technological change (every two months) is challenging.
• The human side of problems doesn't change as fast; PMs need to focus on solving human problems while staying adaptable to new tech.
• The role is reverting to a more general problem-solver, akin to early product management, but with current scaffolding.
• PMs are essential for providing "connective tissue," ensuring all aspects of a project are covered, especially for diverse user bases (prosumers to enterprises).
• The role requires operational excellence and hasn't gone away; it's become increasingly important.

AI's Impact on Product Development

• AI (like Claude) can assist with tasks but cannot yet replace the human convenor role, bringing people and tools together.
• The speed of AI development expands what's possible, requiring strong judgment and relentless execution from PMs.
• Traditional skills like meticulously debating button placement are becoming obsolete; faster iteration and user testing are replacing them.
• PMs must embrace change and potentially discard deeply ingrained skills, adapting to new ways of working.
• The future involves humans and AI agents collaborating; product development needs to be "agent-native."
• Agent-native architectures aim for agents to perform all human tasks, unlocking emergent behaviors.
• Malleable interfaces, changeable by agents, are a key future development.

Building and Iterating with AI

• Companies need to build robust primitives to support agent-native software, enabling evolution over time.
• There's a balance between pushing the frontier with new AI capabilities and providing stable, understandable experiences for all users.
• Anthropic's approach is to "meet everyone where they are" and encourage experimentation, consolidating successful features later.
• Running parallel experiments is crucial, but infrastructure is needed to support them and avoid fragmentation.
• When evaluating new features or models, it's important to re-test concepts with updated models, as capabilities change rapidly.
• Parking projects that don't work with current models allows for future re-evaluation with advancements.
• The challenge is taking successful experiments and integrating them into coherent products, avoiding an overwhelming number of tabs or separate apps.
• Focusing on the "main tab" or core experience remains critical, with new features potentially serving as entry points.

Future Outlook

• The hope for the future is increased solo and small-team empowerment, making it easier to build and innovate.
• The goal is to close the gap between AI capabilities and user adoption, democratizing advanced AI usage beyond highly technical users.

AI and Productivity

• New AI models and techniques are improving, but it's unclear if they are leading to better products or teams.
• Obsession with "software factories" and scaling output predates AI.
• Automating repeatable tasks can save time, but over-reliance on AI might disconnect teams from learning.

The Value of Learning and Context

• Building products historically generates learning; this connection is at risk with increased automation.
• Great products are made by great teams with deep understanding, judgment, and taste cultivated through context.
• Context includes customer insights, product space knowledge, technology capabilities, and team history.

Shifting Focus in Product Development

• Teams should leverage time saved by AI to deepen customer understanding and exploration.
• AI can be a tool to build and manage customer context by aggregating feedback from various sources.
• Product organizations should focus on managing and learning from context rather than just execution.

Practices for Enhanced Learning and Quality

• "Quality Wednesday" trains teams to identify and fix defects, improving their eye for detail and shared learning.
• "Feature Roast" provides raw, critical feedback on new features to better anticipate user confusion.
• These collaborative practices foster shared understanding and improve product quality.

Context as the New Product

• Intuition is learned through experience and exposure to context, not a magical force.
• Context becomes the product; the focus shifts from output (code) to the decision-makers and the context they possess.
• Hiring for great products means seeking individuals who can create a trajectory of ideas, judgment, and taste, built on strong context.

Shipping Imperfect Products

• Shipping imperfect AI products is necessary for rapid iteration and learning from user behavior.
• The goal is to get functionality into users' hands quickly rather than waiting for perfection.
• A coherent product evolution story and transparency with users are key to managing change.

Product Development Constraints

• Focus on additive value: Is the product genuinely useful and unlocking new capabilities?
• Internal dogfooding: Products should be tested and show internal uptake and delight.
• Aim for 2-3 months ahead: Balance current capabilities with future potential, avoiding being too anchored or too futuristic.
• User absorption: Consider users' capacity to understand and integrate new AI capabilities.

The Age of Agents

• Debate on single vs. multi-identity agents: Centralized, versatile agents vs. specialized micro-agents.
• Human nature suggests grouping agents into bundles for easier management.
• Tactical considerations like data access, permissions, and memory behavior are crucial for agent design.

Ecosystem and User Experience

• AI platforms should offer layered capabilities, with tools and plugins as options.
• "Computer vision" (UI automation) can act as a fallback when other integrations fail.
• The ideal user experience is anticipatory and gentle, making users feel like guests.
• Avoid the "last mile" problem: Products that fail at the very end can be worse than non-starters.

Key Product Skills

• Classic PM skills like user empathy and systems thinking remain vital, but applied to AI.
• Relentless iteration and empirical testing are more critical than ever.
• Collaboration with research is new for many, requiring specific use cases and well-written evaluations.
• DMable PMs who are accessible to users are increasingly important for gathering nuanced feedback.

Future of AI Products

• Voice: Expected to be a major interface, feeling natural and intuitive, reducing tech support needs.
• Self-driving software: Products that can proactively assist users, solving the "empty input box" problem.
• Hardware: Devices that replace laptops, offering integrated AI experiences.

The Changing Role of Product Managers

• The perception of jobs disappearing due to AI is fading; instead, roles are overlapping and expanding.
• The core job of a PM remains finding product-market fit and building beloved, viable products, but the methods have changed with AI.
• PMs can now leverage AI tools to automate tasks like note-taking, action item follow-up, and launch communication.

AI's Impact on Product Development

• AI tools, particularly in the "AI builder" role, are transforming how products are created, even in large organizations.
• Atlassian uses a "teamwork graph" to provide organizational context to AI tools, enabling better insights and efficiency.
• PMs can focus on accelerating product development by combining AI intelligence with organizational context.

Case Studies at Atlassian

• Confluence (New Feature): A PM checked in code to fix UX issues, significantly accelerating development. PMs also improved evaluations, automated design bug fixes, and sped up test creation. Remix launched in 6 weeks, Confluence Slides in 8 weeks, a massive improvement over pre-AI timelines.
• Roclaw (0 to 1 Product): PMs and designers vibe-coded an alpha version before bringing in engineers. The PM later shifted from coding to steering to focus on prioritization and unblocking the team.
• Jira (Large Existing Product): To make Jira AI-first, PMs focused on streamlining prototyping (using Loom to generate work items and kick off coding agents) and triaging feedback automatically. This led to a 3x throughput and 22 user-facing features in 10 weeks.

Atlassian's Playbook for AI Adoption

• Atlassian focuses on making existing PMs "AI native" through training.
• The "AI Fluency Index" assesses skills like tool usage, prototyping, and technical literacy.
• "AI Builder Weeks" are quarterly, dedicated training sessions that include external speakers, internal training, and project work, resulting in new workflows and product enhancements.

Measuring Outcomes

• Measuring the impact of AI on product development is still evolving; Atlassian tracks deployed PRs, features delivered, and overall throughput.
• The speaker expresses optimism about the future of product management, emphasizing the opportunities for PMs to deliver more to customers.

The Shift in Career Paths

• The traditional career ladder equated impact with managing more people.
• This model is breaking; impact is now increasingly tied to shipping capabilities.
• Introducing the concept of a High-Impact Individual Contributor (HI-IC): someone who identifies problems, makes decisions, executes independently, ships, and owns outcomes.

The Role of AI

• AI (dubbed "Average Intelligence") acts as a powerful tool, augmenting individual capabilities across various specialties.
• This allows a single person to perform tasks previously requiring a whole team (ideation, building, shipping, learning).
• The cost of building is falling below the cost of coordination, necessitating changes in organizational design.

Enabling HI-ICs

• Information must be accessible to all; organizational layers that gate information need to be reduced.
• Authority must travel with accountability, allowing for independent decision-making and the ability to fail safely.
• Scope should not be confined by traditional function; HI-ICs can work across different areas.
• Pay and status should be decoupled from headcount, with HI-ICs potentially earning more than managers.

Personal Transition and Identity

• The speaker transitioned to an HI-IC role after being "fired" from management responsibilities, finding it a refreshing and impactful experience.
• This shift challenges deeply ingrained identities tied to titles and management.
• The ability to return to one's craft and directly impact customers is a key satisfaction of the HI-IC role.

The Future of Work

• AI's biggest impact is separating impact from headcount, not necessarily replacing jobs.
• Organizations must adapt their structure to leverage AI and the capabilities of HI-ICs.
• Management should be a chosen career path, not merely a promotion, and many managers may prefer returning to IC roles.

The Evolving Role of a PM

• The true value of a PM today lies in decision-making and taste, not just execution.
• AI assistants can now handle tasks previously requiring whole teams, shifting PM focus.

Chapter 1: Understanding People Deeply

• Focus on the fundamental "jobs to be done" that customers hire products to perform.
• Use deep, narrative-driven user interviews to uncover underlying needs (e.g., the bed example).
• AI can help scale this process by analyzing interview transcripts and simulating user interviews.

Chapter 2: Diagnosing Root Causes

• Rigorous analysis and iteration are key to finding product-market fit.
• Identify why users *aren't* doing something and systematically address those root causes.
• Examples: Instagram Stories' "Close Friends" feature (2 years to solve audience issues) and Reels (ephemeral vs. permanent content for entertainers).
• AI can analyze qualitative feedback to identify common pain points at scale.

Chapter 3: Craft and Finishing

• Craft is about the feeling a product evokes, indicating creator care.
• Perfection and lack of user pain are crucial.
• Delight and joy are achieved through intentional design details (e.g., blinking cursor, search box animation).
• AI can significantly scale the process of identifying and fixing product breakages and ensuring quality.

The PM Playbook

• A modern PM playbook involves deep user understanding, rigorous root cause analysis, and meticulous craft.
• AI enables these processes to be more accessible and scalable than ever before.
• The ultimate focus should always be on the humans behind the screen.

Original "Give Away Your Legos" Advice

• Molly Graham's 13-year-old advice: Grow your career by delegating projects and responsibilities to others as a company scales.
• The metaphor: Similar to kindergarteners building with Legos, resist the urge to hoard tasks; embrace sharing to create new opportunities.
• Core message: Change is inevitable and scary, but leaning into it and making yourself "irrelevant" (by delegating) allows for growth.

The Impact of AI on the Advice

• AI as a "Summer Intern": AI is not a super-intelligent replacement but more akin to a junior intern requiring guidance, context, and oversight.
• Oversight Burden: Delegating to AI doesn't eliminate responsibility; humans still own the oversight and final product, creating a mental tax.
• Grief and Loneliness: AI transition brings grief for lost roles (e.g., "rowing" vs. "steering" in engineering) and potential loneliness due to less human collaboration.
• "AI Slop": A growing issue is cleaning up AI-generated work that lacks human judgment, critical thinking, and accountability.
• Productivity vs. Efficiency: AI can increase productivity (more output) but not necessarily efficiency (better, more valuable output).

What Still Holds True and What's Different

• Still True: Change is inherently scary and hard; learning is more crucial than knowing; standing still guarantees falling behind.
• Different: The advice to "give away your Legos" is nuanced. You can't fully disconnect from tasks delegated to AI as you retain oversight.
• The Fear Narrative: The dominant narrative of AI taking jobs and causing mass unemployment discourages embracing change and delegation.
• Opportunity Exists: Despite fear, AI is creating new roles and opportunities, especially for those willing to reinvent themselves and shape the future.

Navigating the AI Transition: Advice and Insights

• Human Judgment is Key: Don't outsource tasks requiring judgment, trust, or defining "good." Humans are uniquely suited for these.
• Embrace the "Intern" Model: Treat AI as a junior intern, providing coaching and context rather than blindly accepting its output.
• Be Discerning: Critically evaluate what to delegate to AI. Keep tasks that are uniquely human or that you love and don't want to lose.
• Focus on Vision and Quality: Guide AI towards your vision, not just the easiest or most statistically optimal outcome. Aim for enduring, high-quality work.
• Managers Matter More: In times of change, managers are crucial for making people feel seen, supported, and for defining standards of good work.
• A Slow Takeoff: The current phase is a "slow takeoff," allowing time to adapt, learn, and shape the future of AI.

AI Building Boom Watchpoints

• AI excels at probable/popular answers, not originality or context-specific needs.
• AI's speed can create a premature sense of "done," masking underlying flaws.
• Ease of AI creation can lead to disposable work and abdication of responsibility.

Recommendations for Building with AI Care

• Have a Point of View: Define brand, user needs, and values to set standards; don't let AI dictate generically.
• Encode Standards into the Machine: Build robust design systems (beyond components to templates/flows) to guide AI and enable distributed/agentic construction.
• Refuse to Confuse Done with Good: Embrace the role of an editor to meticulously scrutinize AI output, focusing on user experience, coherence, and unexpected details.
• Unleash Creativity and Artistry: Use AI as a creative catalyst; invent new interfaces and aesthetics, improve inputs with specific prompts and source material, and push outputs beyond initial results.

The Importance of Craft and Intent

• Users care about solved problems and thoughtful details, not just the tools used.
• AI can amplify human abilities, but intentionality, point of view, and quality bar are crucial.
• Aim for a creative renaissance, not the digital equivalent of "zombie buildings."

Introduction and Core Principles

• Marty Cagan discusses his regrets regarding product development, focusing on core principles rather than fleeting trends.
• The job of product is to solve customer problems and achieve business outcomes.
• Technology waves (including AI) test but often don't invalidate durable product principles.

Key Regrets and Lessons Learned

• Business Viability: Underestimated its importance, burying it as a risk in early work. It's crucial for a solution to be marketable, sellable, serviceable, legal, compliant, and ethical, especially with AI.
• Problem Discovery vs. Solution Discovery: Should have emphasized spending less time on problem validation and more on solution discovery, where innovation truly happens.
• The "Why": Beyond "why are we working on this problem," the more critical question is "why are people not using our product?" This is key to unlocking innovation.
• Humility: The message of "CEO of the product" was counterproductive. Humility, admitting what you don't know, is vital and contributes to avoiding failed products.
• Predictability: The strong desire for predictability (via roadmaps and PRDs) is often at odds with innovation and outcomes. Roadmaps and PRDs are useful as communication tools when based on learned evidence, not arrogance.
• Politics: Naively believed good product work would suffice; politics are integral to companies and require proactive management.
• Product Leadership: Underemphasized the role of product leadership, leading many to mistakenly believe empowered product teams are sufficient without strong leadership and strategy.
• Corporate Governance: Recognized its importance but felt product couldn't influence it; painful lessons show how external forces can derail good product work.
• "Full Contact Blood Sport": Product development is intensely competitive, requiring solutions dramatically better than competitors, a fact not always conveyed by earlier content.
• Thinking vs. Process: Failed to sufficiently emphasize "thinking" as the foundation of product sense. Process, frameworks, and predictability are often used as substitutes for actual thinking, and this is a risk with AI too.

The Future of Product

• Despite regrets, Cagan is optimistic due to AI increasing focus on outcomes over output.
• Principles of the product model, product strategy, and product discovery are more important than ever.
• Distinguishes between "building to learn" (discovery) and "building to earn" (delivery).

Introduction: The Bottleneck of Speed

• The speaker uses a race car analogy to illustrate that speed in product development, like racing, isn't just about individual performance but about optimizing the entire system and removing bottlenecks.
• Just as a pit stop evolved from 67 seconds to 1.8 seconds through optimization, not harder work, product development speed comes from identifying and eliminating constraints.

The Shifting Bottleneck in Product Development

• With engineers automating much of their work, the bottleneck has shifted to product managers (PMs) and other roles involved in defining, collaborating, coordinating, shipping, testing, and releasing.
• This necessitates investing in and optimizing the "factory" (the product development process) itself.

Ramp's Five-Step AI Software Factory Process

• Identify: Sifting through customer feedback (Gong, surveys, emails) to find the core pain points. Ramp built an "customer insight agent" to aggregate and analyze data from multiple sources using ETL and vector search.
• Define: Using AI agents (like Ramp's "Glass") connected to company systems (data, user research, product strategy, codebase) to create specific product requirements and act as a "tech lead" for PMs.
• Build: Automating coding with AI agents (like Ramp's "Inspect") that understand the codebase and can generate deployable prototypes.
• Review & Test: Automating code reviews with AI (like "Review Buddy") that identifies the right human reviewer and understands context. Automating QA with browser-based agents (like "Testo") that test in numerous configurations.
• Coordinate: Using AI agents (like "Gadget") to manage human attention by answering common questions about project status, features, and launches, connecting to formal records and even generating content like help articles.

Embracing Constraints and Evolving PM Roles

• Measuring speed requires a culture that embraces challenges and allows experts to drive improvements.
• Constraints can force innovation (like Audi's focus on fuel efficiency); embrace them to find areas for world-class expertise, but not bottlenecks.
• The role of PMs will evolve into:
• Technical PMs: Building the AI "factory."
• Taste Makers: Providing the vision and quality bar.
• GMs: Owning broader business outcomes.

Key Takeaways

• Speed is about identifying and removing bottlenecks in the build process, not just coding faster.
• As one bottleneck is removed, another emerges; the goal is to move through them rapidly.
• Product leaders should focus on optimizing the "factory" for building products, not just the products themselves.
• The goal is continuous improvement, with a focus on building the "next product" through an evolving software factory.

Current State of Product Management

• Product management has fundamentally changed; execution capacity now exceeds idea generation.
• The bottleneck has shifted from "what can we build" to "what do we believe is worth building."
• AI and advanced tools enable rapid shipping, but this doesn't guarantee meaningful progress or revenue growth.

The Problem with Traditional Roadmaps

• Roadmaps made sense when engineering capacity was scarce, forcing prioritization.
• Now, with increased execution capacity, roadmaps can lead to three traps:
• Backlog Trap: Clearing a backlog doesn't equal meaningful business progress.
• Parity Trap: Competitors converge on similar ideas and products due to shared insights.
• Churn Trap: Shipping and abandoning features without learning or compounding.
• These traps accelerate the path to mediocrity.

Introducing "Roadmap Zero"

• "Roadmap Zero" signifies a state where every visible feature is plausible and buildable, rendering traditional prioritization obsolete.
• Buildability and effort are no longer meaningful proxies for what matters.
• AI factories can ship bad ideas at machine speed, making judgment and conviction crucial.

The Future: Ambition Over Velocity

• The focus should shift from rapid execution (velocity) to ambitious bets and discovering truth.
• The remaining constraint is not code, but "truth" derived from customer interaction and testing.
• Product management needs to focus on proving convictions rather than listing features and dates.

A New Approach: Durable Convictions, Disposable Features

• Build Convictions: Define a long-term vision and determine what evidence validates or invalidates it.
• Maintain a Factory: Retain the ability to build and test quickly, but place it strategically in the process.
• Allocate Based on Evidence: Invest based on what the market tells you.
• Embrace Disposable Features: Be willing to discard solutions while holding onto core convictions.
• Communicate Honestly: Differentiate between probes, experiments, and firm promises to manage customer trust.
• The goal is ambition, with fuzzy specifics and a high bar for quality and learning.

The Frontier Problem

• Building products on a "moving frontier" is difficult due to the conflict between exploration (divergent, trying new things) and execution (convergent, focusing on a roadmap).
• Customers are often unfamiliar with new technologies, so they rely on product leaders for direction.

The Labs Solution

• Organize product efforts like a research lab to separate exploration from execution.
• A "labs team" focuses on exploring new capabilities and running experiments, expecting to discard 90% of their work.
• The main product team focuses on improving and scaling existing features, adopting about 10% of what the lab produces.
• This structure harnesses "early adopters" on the team without distracting the core product team.
• AI makes this feasible even with a "labs team of one" due to the superpowers AI models provide.

Running a Lab Effectively

• Keep teams very small ("two slice team": 1-2 people).
• Pair "pirates" (obsessed with finding value) with "architects" (shaping messy systems into valuable ones).
• Prioritize "dogfooding" (using what you build yourself) for the tightest feedback loop.
• Run many experiments in parallel, even on the same problem, to map the unknown frontier.
• Find ways to make experiments ROI-positive, such as turning them into external content or feeding an early adopter program.

The Research Pipeline

• Establish a pipeline where lab experiments move progressively towards the product team for integration.
• Internal use by other team members is a key step before exposing to early customers.
• Clear decision criteria for pipeline progression include: user adoption and return, being 10x better than existing solutions, and affordability at scale.
• The ultimate goal is merging successful experiments into the main product.
• Examples like OpenAI's Codex (which became the foundation for ChatGPT) demonstrate this model's success.

Success Metric

• The true sign of success is welcoming new model releases with excitement rather than dread.

Team Organization

• Design teams like a "terrorist organization" with a strong ideological culture and clear decision-making structure.
• Focus on the cost of collaboration and ensure clear ownership ("single-threaded").

Talent Management

• Prioritize developing your best people ("spending time writing your best people into the ground") over improving average performers.
• "If somebody is strong and crushing it, I'm just handing them more and more rope to hang themselves with."
• Embrace "spiky talent" – individuals with unique, extreme skills – and build teams capable of managing them.

Product Management Profession

• Most product managers are "bad" and often net negative.
• The median PM is likely "pretty bad" due to the profession's structure: top performers become founders/execs, and incentives encourage staying in PM roles.
• Snap historically did not hire PMs, aiming for products that could operate without them.

Snap's Monetization Challenges

• Young user base (Gen Z, Gen Alpha) has lower ad CPNs and strict targeting/measurement constraints.
• Snap's core product (camera-first, creation-oriented) is a "hostile environment for advertising" unlike feed-based platforms.
• It's a messaging app, a format historically difficult to monetize effectively via ads.

Growth and Strategy

• Focus growth on the core business ("always money in the banana stand") and optimize for Daily Active Users (DAU).
• For consumer products, aim for high DAU/MAU ratios.
• Bet on new things when expanding from core strengths or when users organically adopt the product in unexpected ways.

AI and Product Development

• A key skill for PMs is pushing back on AI-driven additions to products.
• Taste is crucial, and a skill is knowing what to *remove*, not just add.
• AI has a hard time replicating the "restraint" and taste needed for great product curation.

Contrarian Takes

• Light Spicy: The most important career decision is your personal partner.
• Medium Spicy: Great taste means knowing when to stop engaging with a trend before it becomes "cringe."
• Heavy Spicy: Inalienable traits (gender, race, ethnicity, socioeconomic background) are essential for building certain consumer products, though not directly actionable in hiring.

Long-Term Thinking and Ambition

• "Long-term greedy" in ads means focusing on advertiser ROI today for future revenue.
• Develop "core product value" phrases with clear metrics to guide product decisions and onboarding.
• Embrace ambition; the goal is acceleration, not just speed or position.

Grok Bot Origins and Vision

• Vision: A team of AI bots to assist with both job and life tasks, acting as colleagues.
• Origin: A small, isolated internal team built Grok Bot from scratch in about a month.
• Goal: Create a knowledge work product to bring AI agents to the broader company.
• Success Driver: Moving quickly with micro-decisions in a focused, isolated environment.

Key Decisions and Features

• Separate Product: Decided to build Grok Bot as a new product, not integrate into Cursor, for a consistent vision.
• Cloud-Based: All workflows run in the cloud, creating a persistent, accessible "colleague."
• Bot's Own Computer: Each bot has its own environment, enabling interaction with tools and interfaces like a human.
• Simplified UI: Focus on progressive updates rather than showing internal mechanics to users.
• "Just Works" Philosophy: Aggressively simplified the product, removing unnecessary features and focusing on backend reliability.

Development and Launch Strategy

• Manual Onboarding: Onboarded 200-300 users manually to gather crucial feedback and identify product issues.
• Learning from Users: Observed emergent usage patterns, like the "chief of staff" bot role, without imposing them initially.
• Iterative Unshipping: Ruthlessly removed experimental or unneeded features to simplify the product before launch.
• Focus on Capabilities: Shifted from "Grok Bot now has X" to "Grok Bot can now..." framing, emphasizing capabilities over new UI elements.

Unique Insights and Learnings

• Computer Use Abstraction: The "computer" concept for bots will be abstracted away, becoming seamless.
• Long-Lived Agents: Bots are designed as long-lived agents that learn and retain state, not one-off sessions.
• Human Teammate Analogy: Decisions are guided by "what would you want from a human teammate?"
• Work/Personal Separation: Believes one product can serve both work and personal needs, with separation handled by different bots.
• OpenAI Inspiration: Inspired by Open AI's approach to bots as colleagues and access to tools, but focused on ease of setup and user experience.
• "Unshipping" Value: Removing features is as important as adding them for product simplicity and power.
• "Just Do It" Culture: Empowering individuals to take initiative and execute without needing permission.
• "Mores" are Discovered: Emphasizes building useful things today and pulling future capabilities forward, rather than planning Moats upfront.

Go-to-Market and Future Vision

• Targeting Businesses: Focus on team-based bot integration and enterprise systems, not just single-player use cases.
• Speed and Alignment: Maintaining a startup energy and clear vision despite company growth.
• Core Pillars: Coding (Cursor), General Knowledge Work (Grok Bot), and Model Development (SpaceX AI).
• "No Look Pass" Experience: Aiming for AI that handles 100% of a task, fundamentally different from 90% completion.
• Practical AI: Goal is useful AI, not abstract superintelligence, driven by an applied mindset.
• Information Consumption: Bots acting as "infovores" to process vast amounts of information and provide summaries or alerts.
• Proactive Agents: The next shift will be agents being more proactive than users reaching out.

AI and the Permanent Underclass Myth

• The fear of becoming a "permanent underclass" due to AI is a "dark fantasy" and not supported by current evidence.
• Technology amplifies agency and unbundles skill from desire.
• The tech landscape is more distributed now, with many competing players, unlike the "winner-take-all" era of network effects.
• Empirical data on job postings and economic indicators don't support widespread job displacement fears.
• True recursive self-improvement (RSI) in AI is not occurring; instead, autocatalytic effects are observed.
• The diffusion of AI's impact into daily life is slow, and many problems are not solely intelligence-bound.

The Rise of "Loops" in Company Building

• Company building is increasingly about creating and optimizing "loops" – cascading sets of agents and processes.
• These loops can exist at individual, team, and company-wide levels.
• Humans remain critical for intuition, out-of-distribution thinking, and setting direction.
• The opportunity lies in "loop make me happier," focusing on connection, love, progress, and fun, rather than just saving time.
• This is a product design challenge, not a model or capability challenge.
• AI can automate administrative tasks, allowing humans to focus on core, high-leverage activities.
• The growth loop example: AI generates and measures experiments, with humans intervening at local maxima for new strategic direction.
• Go-to-market teams can use AI (like Codex) to handle administrative tasks, freeing them for high-value interactions.
• AI can help PMs test more ideas, leading to better organizational health and the best ideas winning.

AI's Impact on Skills and Roles

• The "soft skills vs. hard skills" debate is shifting as AI excels at concrete, verifiable tasks.
• The future relies on skills that cannot be easily automated into loops.
• Humans are needed to coach agents when they get stuck, providing context and learning data.
• Companies should ask: "If AI were infinitely intelligent and cheap, how would we reorganize?"
• A split is emerging between functions using efficient open-weight models (e.g., legal, finance) and those using expensive frontier models for high-upside areas (e.g., sales, research, engineering).
• The "intelligence threshold" for many economically useful problems may have been crossed, making further AI intelligence in some areas less impactful.

The Future of Consumer Tech and Ambition

• The biggest opportunity is "loop make me happier," focusing on fulfilling basic human needs for connection and enjoyment.
• Consumers are more interested in spending time than saving it, making entertainment and social products powerful.
• AI can extend our "soul," not just our intellect, addressing a spiritual hunger.
• Startups have an advantage in exploring uncomfortable or disagreeable aspects of human existence with AI.
• Consumer AI is early (like iPhone 2010), with challenges in cost, interface (beyond chat), and focus beyond productivity.
• The future of consumer AI includes coding agents (like Wabi), personal agents (like Grok, ChatGPT Work), and creative/companionship tools.
• Durable moats are often discovered, not designed, and can include network effects, scale, brand, and proprietary data.
• Ambition is key; companies are shifting from "too ambitious" to "not ambitious enough" in their inception.
• Expensive consumer software is a new and important category.
• AI amplifies identity and agency, unbundling skill from desire and enabling greater individual expression and ambition.
• The focus should be on building "remarkably" to generate word-of-mouth growth.
• Distribution is a critical moat, but the best form is now grassroots word-of-mouth.
• The challenge is often a failure of imagination, not growth or product capability.

Lessons and Optimism

• Moats are often discovered, not designed; focus on shipping and engagement.
• Classic moats (network effects, scale, brand) still apply.
• Founders should build ambitious products, even if they seem "too small" initially.
• "Building is the new reading" – learning through execution and iteration.
• The "permanent underclass" narrative is fear-mongering; AI can drive productivity and ambition.
• AI can help make important things like healthcare and education cheaper and more accessible.
• The AI industry is evolving rapidly, with open-weight models challenging frontier models.
• The most exciting AI products offer joy and help solve human "jobs to be done" like improving connections or ambition.
• Companies are increasingly looking for "moonshot" ambition and are willing to invest heavily in ambitious ideas.
• Don't discover things through painful experience; learn from those ahead.
• For startups, pick one focus (product or platform) rather than trying to do both.
• Embrace building things, even if they are small or experimental, to develop intuition and skills.

AI Eras & Future of Work

• The first era of AI was chat, the second was agents, and the third is persistent AI coworkers.
• Product development in AI must target 2-3 months ahead, not current capabilities or a year out.
• The PM role is shifting from academic/theoretical to prolific and empirical, focusing on rapid user testing.
• The future of work involves "steering" (directing AI agents) more than "rowing" (executing tasks).
• Human brains will remain valuable for accountability, expression, and caring for each other.

OpenAI Culture & Product Strategy

• OpenAI is "open"; strategy and product ideas quickly become public.
• There's a thin distance between OpenAI employees and the market; they operate like founders.
• The focus is on shipping products quickly, valuing "done is better than perfect."
• Internal memes: "Is this maximally accelerated?", "Are you mainlining it yet?", and "Are we elevating our mission?"
• Building for AI requires a focus on model capabilities, not just current state, and getting out of the model's way.

Productivity & AI Tools

• Sites: Users can create dynamic websites/tools with prompts, realizing the dream of personal software.
• Visualize: Users can create amazing visualizations of their AI usage or data with simple commands.
• Writing as Thinking vs. Reporting: Automate reporting, but do thinking/briefs manually to sharpen one's own ideas.
• ChatGPT App (Work Mode): Integrates Codex capabilities for knowledge work, aiming to be a unified experience.
• Distinction between coding (output-oriented, testable) and knowledge work (process/input-oriented, requires collaboration).

Ambition & Human Value

• AI tools enable greater ambition by expanding what individuals can accomplish.
• The hardest part is expanding one's thinking to match AI's capabilities.
• Product Managers can elevate others' ambitions and remind them of possibilities.
• Human value lies in accountability, unique expression/artistry, and interpersonal care/collaboration.

Introduction to Enterprise Sales

• Enterprise sales is a complex, multi-step process, often involving around 15 steps, not the commonly assumed five.
• Successful enterprise sales prioritize understanding the buyer's needs and framing the solution as an "alpha" or unique advantage.
• Founders are often well-suited for early-stage enterprise sales due to their ability to communicate vision and pull on emotional strings.

Landing the First Meeting (Step 1)

• Target either the top executive (e.g., Chief Legal Officer) or an "N-1" individual (e.g., VP).
• Craft a concise, 2-3 sentence pitch focused on the "alpha" or what the solution unlocks, not just a problem solved.
• Employ the "pincher model": founder/exec targets the top, while an AE targets the N-1 to create convergence.
• Leverage tools for contact information but focus on a differentiated message to stand out.

The Crucial Intro Call (Step 2)

• This is the most important call; aim for a 30-minute, informal, one-on-one dialogue without demos or slides.
• Allow the prospect to speak first to gain maximum information and tailor your subsequent discussion.
• Focus on understanding their priorities, what needs to change, and their desired future state, rather than pitching.
• Do NOT record the call to foster vulnerability and openness.
• A successful intro call allows for qualification, with roughly 1 in 4 calls being a no-go due to maturity or fit.

Preparing for the Demo (Step 3 & 4)

• Conduct a short, 15-30 minute "follow-up intro call" to gather intel on what specific aspects of the product will resonate for the demo.
• Involve the champion in co-crafting the demo to make it feel like a collaborative effort, not just a product showcase.
• The goal of the demo is to make the prospect feel like the solution was built specifically for them.
• Focus the demo on the 20% of the product that delivers 80% of the value, aligned with their identified priorities.

Running the Demo and Post-Demo (Step 5 & 6)

• Ensure the right people are present for the demo; understand their roles and what each stakeholder cares about.
• Tailor the demo narrative based on prior conversations, incorporating specific questions or concerns raised by attendees.
• After the demo, immediately debrief with the champion to gather raw reactions and identify potential roadblocks or areas needing further attention.

Pilot and Pre-Pilot Planning (Steps 7, 8, 9)

• Identify a small group (3-4 users) for a 2-3 day pilot to experience the "magic" of the product.
• Define clear, measurable success criteria for the pilot collaboratively with the prospect.
• Before the pilot, work backward from the desired close date to map out procurement, legal, and security review timelines.
• Discuss pricing post-demo, providing a ballpark range and working with the champion to build an ROI case.
• Consider charging for longer pilots requiring integration, crediting the fee towards the final purchase.

Navigating the Sales Cycle and Closing (Steps 10-14)

• Recognize that traditional 5-step sales stages are for forecasting, not client interaction; enterprise sales involve many more nuanced steps.
• Post-pilot, gather feedback through surveys or one-on-one sessions, using the champion to address any user issues.
• A healthy enterprise win rate is 25-35%; higher rates may indicate prices are too low.
• Prepare "paper" (contracts) in Word format, offering to use the client's paper if it accelerates the process.
• Engage in live calls to resolve redlines and legal/procurement concerns, focusing on critical business impacts.
• Procurement is a process step, not inherently a deal killer; don't start work until contracts are signed.
• Ensure the correct signatory is identified before final paper routing.

Post-Sale and Expansion

• The "close" is often just the beginning, leading into expansion opportunities.
• Services revenue is a significant budget item and a viable path for early-stage companies to partner with clients.
• When advising buyers, be direct about timing or maturity issues to avoid wasting everyone's time.
• AI-generated sales content is often generic; focus on personalized, human-crafted communication for genuine connection.

Designers' Current Sentiment

• Designers are feeling unhappy, overwhelmed, and anxious due to uncertainty about their evolving roles.
• The traditional design process (prototype, mock, test, research, iterate) is being compressed by the rapid pace of AI development.

The Opportunity in AI for Designers

• This is the best time in history to be a designer due to vast opportunities and accessibility of tools.
• Starting as a designer today offers a potential advantage due to the early stage of AI integration.
• AI tools amplify designer productivity, allowing for rapid exploration of ideas and raising the overall bar for design quality.
• Key attributes for success include curiosity, adaptability, exploration, and creativity.

AI's Role in Product Design

• AI is already an incredible product designer, accessible to everyone.
• Human designers remain crucial for truly understanding user needs, inventing new concepts, and providing a unique point of view.
• Developing novel AI products requires human insight to create things that haven't existed before, as AI is trained on existing data.
• The human element is vital for evaluating good design and learning through iteration.

The Evolving Design Process

• The traditional linear design process is being replaced by more fluid, iterative, and experimental approaches.
• OpenAI embraces "building in public" for some features, allowing for quick swings and rapid learning.
• For more critical or foundational features, a more traditional, iterative process with deep iteration is still employed.
• Designers must be adaptable, as technology and capabilities change rapidly, sometimes within months.

Future of Design and AI

• AI will become more adaptive, proactive, and integrated into daily life.
• The interface will evolve beyond text, incorporating richer voice and visual outputs.
• Durable workflows and personalized experiences tailored to different user contexts are key future directions.
• The "blank box" challenge requires designing adaptable interfaces for AI that can serve diverse needs.

Skills for Future Designers

• Curiosity about AI and aptitude for learning new tools are essential.
• Prototyping skills remain highly valued.
• Strategic thinking, systems thinking, and understanding underlying primitives for composability are increasingly important.
• Designers need to embrace adaptability and focus on the ultimate product outcome rather than just process.

Understanding the "Funnel of Doom"

• Most companies recruit using a "funnel of doom" approach, where they start with a large pool of candidates and weed them out, leading to hiring "remainders" rather than top talent.
• This method is flawed because the initial pool isn't necessarily the best, and it leads to average hires over time.
• The mistake stems from treating recruiting like sales, which is transactional, whereas recruiting deals with irrational humans.

Building High Talent Density Teams

• Focus on a "pillar of excellence" by identifying the top 20% of candidates upfront and validating them through the assessment process.
• Treat every hire like an executive search:
• Scoping: Objectively define what "great" looks like for the role by stack-ranking skills and experiences.
• Market Mapping: Identify and relentlessly pursue the top 50 individuals globally for the role.
• Activation: Focus energy on engaging these specific individuals, not on broad sourcing.
• Avoid focusing on "logos" on resumes; instead, look for objective skills and transferable qualities.
• When seeking recommendations, ask specific questions about collaboration or translation skills, not just "who's the best."
• Use networks of trusted individuals and analyze company job postings for desired characteristics to map the market.
• Systems thinking, the ability to break down large problems into smaller, tactical steps, is a highly valued skill.

The "Relentless Pursuit" Tactic

• Engage candidates early and often, even if timing isn't perfect, by suggesting coffee or introductions to team members.
• Nurture relationships over weeks, months, or even years, planting seeds for future opportunities.
• Prioritize warm introductions and personalized messaging over generic outreach.
• "Caring is free": Demonstrate genuine interest in the candidate, making them feel valued and belonged.
• Focus on hiring "one" ideal person for the role, not just filling slots in a funnel.
• Be comfortable with bespoke and ad hoc hiring, tailoring the process to each candidate.
• The hiring manager's first conversation is crucial; it should be a 50/50 exchange to assess fit and motivators.
• Treat hiring as person-centric, not job-spec-centric.
• Humanizing activities like sharing meals and personalized gifts can be powerful closing tactics.

Assessing Candidates and Making Offers

• Work samples are the highest predictor of success; conduct long on-site experiences with projects.
• The on-site should be a two-way street, providing candidates with as much information and data as the company receives.
• Recruiters quarterback the process, with input from hiring managers and execution support from coordinators.
• Turn candidates into "net promoters" by ensuring a positive experience, even if they don't join.
• Work trials provide significant signal, even if they are resource-intensive.
• Hiring is manager-led, with input from the team, and decisions are made quickly (same day or next day).
• Focus on intrinsic motivations (role, team, people) over extrinsic factors (compensation) when closing offers.

Talent Trends and Team Building

• The market has a "tale of two cities" dynamic with high demand for some roles and struggles for others.
• Forward-deployed engineers (FDEs) are in high demand, bridging technical and customer-facing roles.
• Specialized technical roles are becoming less in demand as companies seek T-shaped individuals with broader skills.
• The rise of the "power IC" with strong taste, judgment, and problem-solving skills is evident.
• "Systems thinking" and "curiosity" are key attributes.
• Recruiters are a "confidence engine," not a decision-making engine; hiring managers own the hiring decision.
• Talent density is a collective nature of a team, not just individual 10Xers.
• A common mistake for early-stage companies is the "silver bullet hire" of a Head of Talent, collapsing system-building and hiring delivery.
• Key attributes for recruiters include curiosity, business focus, high motor, and a "chip on their shoulder."
• Build teams with excellent humans who love the craft, have a drive to prove themselves, and prioritize the team.
• The "talent engineer" role is emerging, where recruiters build their own tools.

Product Management Philosophy

• Whatnot's CPO Tom Verrilli famously stated, "We regret that product management exists," to emphasize hiring PMs only when a specific need arises, rather than assuming every team requires one.
• This perspective stems from the belief that engineering and design teams are capable of making product decisions if adequately informed, and that over-reliance on PMs can infantilize these functions.
• Product management is viewed as a "trade" or a "muscle" built through practice, and abstracting engineers and designers from this practice can lead to underdeveloped skills.

Hiring & Skills

• Whatnot received 31,832 PM applications and hired only one, indicating a highly selective process.
• Skills trending down in PM candidates include overemphasis on "driving alignment" and "stakeholder management," which can indicate a focus on politics over product.
• Skills trending up are macro and micro-thinking, the ability to be specific about past contributions, and a proactive, decision-making mindset rather than just babysitting existing products.
• Systems thinking is crucial; the advice is to "take one click back" to understand broader business context and potential consequences of decisions.

The Role of PMs & AI

• AI significantly enhances PM capabilities, particularly in data analysis (e.g., using Hex threads) and understanding codebase logic, reducing reliance on data scientists and engineers for initial exploration.
• AI allows experienced PMs to move faster by providing leverage, enabling quicker decision-making and prototyping.
• The trend is towards PMs being more hands-on "Individual Contributors" (ICs) rather than solely focusing on management and alignment, even at senior levels.

Whatnot's Team Structure & Culture

• Whatnot has a relatively small PM team (around 20) for its scale.
• PMs are loosely organized into buyer, seller, and trust/risk groups and are reassigned regularly to different projects, focusing on problems rather than fixed teams.
• Planning is done semi-annually, with leaders defining company objectives and then assigning DRIs (Directly Responsible Individuals), often PMs, to tackle those objectives.
• The culture encourages "know then go," meaning thorough upfront thinking about potential issues before proceeding, rather than being overly hindered by risk aversion.

Future of Product Teams & Skills

• The canonical product team may evolve to have more "engineering manager light" roles to incubate smaller teams.
• Core PM skills like identifying what to build, prioritizing, understanding business strategy, and communicating requirements are becoming increasingly valuable as AI handles more of the "building" aspect.
• There's a push for PMs to return to these core skills, moving away from "product theater" (e.g., excessive alignment meetings, framework presentations).
• The most successful model involves leadership being hands-on and deeply understanding the "ground truth," with AI enabling this at scale.

Key Learnings & Advice

• "Play the accordion" is a mental model for PMs: stretch out to understand the problem and context (pulling out), then build and learn from experiments (pushing in), repeating the cycle.
• Reliance on averages in data can be misleading; understanding individual user cases and the impact on them is crucial.
• Founder-led companies often succeed due to deep customer intuition, and product leaders must find a rhythm with founders, understanding when to step back and when to push.
• The advice for aspiring PMs or those looking to move back into IC roles is to focus on practical work, hone core skills, and demonstrate value through execution.

Anthropic's Early Days and Culture

• Anthropic started with a strong culture and a startup energy, exploring its identity beyond just technology.
• A key early moment was the "Golden Gate Bridge" experiment, showcasing rapid product iteration and user engagement.

Key Inflection Points in Model Development

• Developing Opus 3 was a major milestone, building trust and rallying teams towards a common goal.
• Identifying coding as a crucial use case for models like Opus 3 differentiated Anthropic early on.
• Opus 4 was magical due to the combination of a frontier model and a great product experience like Claude Code.

Product Development in the Age of AI

• The product role is evolving, with "evals" becoming the new PRDs for driving user value.
• There's an emphasis on "sweating the tokens as much as you sweat the pixels," encouraging deep model interaction.
• Users need to be more ambitious with AI tools due to their advanced capabilities.
• The product must adapt to the rapid pace of AI improvement, with adaptability and first-principles thinking being crucial.

Anthropic's Labs and Research

• Labs focuses on identifying and pursuing discontinuous, large-bet opportunities like Claude Code, Skills, and Claude Design.
• Culture, experimentation, and selecting for "zero-to-one" thinkers are key to Labs' success.
• Researchers have a vision for the future and focus on iterative improvements, with product managers bridging user feedback and research.

The Evolving Role of Product Managers

• First-principles thinking is essential, focusing on user value rather than just replicating past activities.
• "Evals" are critical for defining work, stemming from deep understanding of user pain points and model failures.
• PRDs are still valuable for aligning large groups and exploring ambiguous problems.
• Product managers must be hands-on, shipping with the technology and understanding "what good looks like."
• Joy and collaboration are key to avoiding burnout; experimentation is not an individual sport.

Future of AI and Human Value

• Hard-earned judgment, persistence, and proactivity are critical human traits that AI currently lacks.
• Subject matter expertise in areas like biology and life sciences will remain valuable as AI develops.
• Children should be encouraged to develop curiosity, persistence, and their own inner voice.
• The focus should be on developing AI that augments human thinking, not replaces it.
• Alignment research and safety focus make Claude more interesting and less compliant, leading to better outcomes.
• The goal is to make AI models inclusive and accessible, reducing reliance on niche access.

The AI Era and Evolving Roles

• AI is causing a "storming phase" where traditional roles blur (PMs coding, engineers productizing), leading to confusion but also opportunity.
• Functional expertise (engineering, data science, creativity) remains scarce and valuable, not obsolete.
• Netflix's culture of high agency, autonomy, and top-of-market pay aligns with top AI labs.
• "Excellence as an operating system" drives Netflix's approach: talent density, risk-taking, and avoiding bureaucracy.

Systems Thinking as a Key Skill

• Netflix is hiring more "systems thinkers" who can see across business domains and abstract building blocks needed for AI.
• This is crucial for creating preferred paths, common infrastructure, and guardrails in a complex AI landscape.
• Designers are increasingly needed for "design systems thinking" to ensure coherence in user experiences.
• To develop systems thinking: "step out one click" from a problem to question assumptions about the broader space.

AI's Impact on Functions and Content

• AI accelerates prototyping, data analysis, and information distillation, enabling faster hypothesis generation.
• Specialization is becoming less emphasized, with a shift towards generalists and adaptable individuals.
• AI is impacting content creation through pre-visualization, post-production (re-lighting, reframing), and localization at scale.
• Netflix's history with the Netflix Prize demonstrates early AI/ML adoption for personalization.

Maintaining Excellence and Talent

• "Excellence as an operating system" relies on talent density, comfort with risk, clear focus on consumer/business outcomes, and selflessness.
• Resisting the urge to add process when things go wrong is key; trust in people's ability to reflect and learn.
• The "keepers test" (Would I fight to keep this person?) is used both for performance evaluation and to celebrate extraordinary contributions.
• Attracting top talent involves highlighting the unique intersection of tech, entertainment, and consumer products at Netflix.

The Future of Entertainment and Engineering

• Entertainment is diversifying beyond film/TV to include games, live content, and podcasts, requiring seamless discovery.
• Netflix aims to enable creators with AI tools while respecting those who choose not to use them.
• Humanity will remain central to storytelling, with AI amplifying rather than replacing human creation and connection.
• Engineering will evolve to understanding complex systems and AI-generated code, not just writing code itself.

Tech Workforce Bifurcation

• The tech workforce is split: 50% feel amplified and energized by AI, while the other 50% feel unclear, destabilized, or diminished.
• This AI-driven bifurcation has an outsized impact on job sentiment, career optimism, burnout, and layoff worries, significantly more than other job factors.
• "Amplified" individuals feel they can do more and better work with AI, while the other half fall into groups feeling their roles are being redefined (27%), destabilized (14%), or diminished (5%).

Burnout and Optimism Decline

• Burnout has surged significantly, with over half of tech workers reporting high levels.
• Optimism about the future of roles and careers has fallen.
• This contrasts with previous years and suggests that increased velocity and AI adoption are leading to more work and exhaustion, not less.

Career Recommendation and Role Sentiment

• A striking majority of tech workers would not recommend their current role to someone entering the industry.
• Designers and researchers are the least likely to recommend their roles, followed by engineers, PMs, sales, and founders.
• While many enjoy their current work, there's a lack of optimism about the future, suggesting AI is perceived as a threat or destabilizing force in the long term.

Productivity vs. Quality and Cognitive Rot

• While 97% of tech workers feel AI makes them better at their job, this often means doing *more* faster, not necessarily *better* quality.
• A concerning trend is "cognitive rot," where individuals accept AI output without critical thinking, leading to a decline in their own skills and judgment.

Dominant Fears: Overwork, Not Replacement

• The primary fear among tech workers is not losing their job to AI, but the expectation to do more for the same pay and an unsustainable pace of work and technological change.
• This leads to feeling overworked, tired, and squeezed, contributing to burnout.

Ambivalence and Archetypes

• The tech industry is experiencing significant ambivalence, with a mix of positive and negative emotions.
• Positive emotions like curiosity and excitement are high, but so are feelings of being overwhelmed, conflicted, tired, and anxious.
• The concept of "smiling exhaustion" captures this duality: high engagement and excitement coupled with relentless pace and lack of rest.

Group-Specific Feelings

• Designers and researchers report the most negative sentiment, feeling destabilized, diminished, and worried about job loss.
• Founders and those in smaller companies report the highest optimism, lowest burnout, and least layoff worry, though even founders are not highly likely to recommend their roles.
• Burnout and negative sentiment increase linearly with company size.
• Manager effectiveness is a critical factor, with highly effective managers significantly boosting job enjoyment and reducing burnout, yet few managers are rated as highly effective.

Overall Industry Sentiment

• The industry is described as chaotic, fast-paced, unstable, and filled with hype, but also opportunities.
• Sentiment is evenly split between positive and negative descriptions, reflecting the polarized experience of AI's impact.
• Concerns about "AI guilt" exist, particularly among early-career professionals who feel leveraging AI is like cheating.

AI's Impact on Product Development

• Product teams are shifting to smaller, more generalist "pods" (4-6 engineers, 1 product staff) supported by specialists as needed.
• AI tools are automating mechanical data science tasks, allowing product staff to handle analyses previously done by dedicated data scientists.
• The lines between traditional roles (PM, designer, data scientist, researcher) are blurring, with "product staff" evolving to encompass broader skills.
• Less emphasis on purely specialized roles, with a focus on generalists who can leverage AI tools and drive projects end-to-end.

The Value of Taste and Human Judgment

• In a world of easier content creation (due to AI), "taste" and human authenticity become more critical.
• AI is good at building, but humans are needed to determine *what* should be built.
• Human judgment remains essential for strategy, vision, and understanding nuanced business context that AI cannot grasp.
• Creators and authenticity will be increasingly sought after as AI-generated content becomes abundant.

Instagram's Algorithm and Content

• Instagram's algorithm doesn't have a detailed semantic understanding of user interests; it uses correlations in embedding spaces.
• LLMs are enabling new ways to understand these embedding spaces, allowing for clearer topic descriptions and user agency in customizing their feed ("Your Algorithm").
• Algorithmic feeds generally perform better than chronological ones because they manage content volume and incentivize creators beyond just posting frequency.
• AI content is seen as a tailwind for Instagram, as people will seek out human creativity and authenticity amidst synthetic content.
• Instagram aims to label AI content but not to filter it out, focusing on the point of view and person behind the content.

Future of Work and Skills

• Key hiring traits include grit, quick learning, self-awareness, curiosity, and a willingness to try new things and make mistakes.
• Roles requiring large-scale organizational leadership may decrease, while smaller team leadership and generalist capabilities increase.
• AI is shifting the nature of many jobs; for example, engineering now involves more planning and code review than just writing code.
• The "reverse centaur" (AI controlling humans) is a feared outcome; humans should remain in charge, using AI as a tool.

Product Leadership and Development Learnings

• The best product leaders are often "curators" of people, ideas, and technologies, fostering environments for great ideas to emerge.
• Team chemistry and rapport are crucial for leadership teams to function effectively.
• Failures like Facebook Home and building Reels on top of Stories provided significant learning opportunities.
• Companies must be prepared for backlash when testing changes and have clear communication strategies.

Navigating AI and Screen Time

• The cost of AI models is a concern; while current costs are manageable, future token spend could rival engineer salaries, potentially requiring caps.
• AI is useful for creativity and learning, but parents need to set boundaries and educate children on responsible use, especially with AI tools.
• "Vibe coding" (using AI to build things like games) can be a way to teach kids about AI and creation.
• Companies are wrestling with how to detect and label AI content reliably as models improve.

Codex and OpenAI's Product Work Revolution

• Codex Adoption: 90% of OpenAI employees, not just engineers, use Codex weekly.
• Ambition for Codex: Intention to make Codex the best desktop app ever created, aiming for seamless integration into users' natural workflows.
• Usage Growth: Codex usage has grown 6x since January, with over 5 million weekly active users.

AI's Impact on Product Development

• Inverted Process: Implementation is no longer the expensive part; "taste" (curation, judgment, framing) is the new bottleneck.
• "90 Prototypes" Phenomenon: With cheap implementation, multiple teams simultaneously explore the same idea, leading to numerous prototypes instead of lengthy documents.
• Shift from PRDs to Prototypes: While prototypes are valuable for testing interactions, PRDs remain crucial for product clarity in vague areas. The key is choosing the right medium for the message.
• "Taste" Redefined: It encompasses aesthetic, systems thinking, strategic direction, and presentation, not just visual appeal.

AI and Design Challenges

• Grading Difficulty: AI struggles with design due to the subjective nature of human taste, making feedback loops more complex than for code.
• Cultural Nuance & Novelty: AI models tend to replicate existing patterns (like Linear's website), whereas design requires novelty and cultural understanding.
• Abstraction Layer: AI currently lacks the deep understanding of how design elements should interconnect within a codebase for cohesive updates (e.g., rebranding).

The Evolving Product Role

• Role Collapse: Teams like Codex, with engineers and PMs who can code, see significant role overlap and fluidity.
• "Average of Your Role": An individual's role is increasingly defined by the average of their activities rather than strict titles.
• Caution Against Extremes: Eliminating roles entirely can discard valuable specialized knowledge and best practices.
• "Zone Defense": Product managers aim for broad company coverage, identifying and filling gaps rather than working too closely together.
• High Agency, High Taste: The ideal candidate can take an idea from inception to completion with excellent judgment.

Planning and Ambition in an AI World

• Short-Term Precision: Planning requires more detail for the near future, while long-term plans must remain hazy due to rapid AI advancements.
• Model-Driven Features: Product success increasingly depends on AI model capabilities and timing, requiring flexibility in development.
• Iterative Releases: Products may need multiple releases, with the same core shape, to align with evolving AI capabilities.
• Ambition & Exploration: Encouraging exploration of ambitious ideas, even if not immediately feasible, allows for future adaptation as models improve.

Codex's Vision and Evolution

• From CLI to App: Codex evolved from a command-line tool to a desktop app, aiming to be a central "home base" for work.
• General Knowledge Tool: The goal is to make Codex a general tool for knowledge work, integrating seamlessly with existing applications (Excel, Premiere Pro) through connectors, computer use, and extensions.
• "Super App" Concept: While not explicitly named as such, the vision is a single place to start, end, and automate work, leveraging necessary tools.
• Learning from Failure: OpenAI embraces internal feedback (e.g., "2000 messages saying this sucks") to refine products.

AI's Impact on Engineering Productivity

• Anthropic engineers ship 8x more code per quarter than in 2021, demonstrating AI's impact on productivity.
• Coding is no longer the bottleneck; ambition and scope are now the limiting factors.
• The shift requires engineers to embrace AI, leading to increased agency and accountability.

Evolution of Software Engineering Tools and Practices

• Fiona Fung's career journey highlights the evolution from Vim and terminal debugging at IBM to modern IDEs and cloud-based tools.
• The shift from shipping software on CDs to online distribution transformed release cycles and planning.
• AI tools like Claude Code and Co-work are enabling non-engineers (designers, PMs) to contribute code, blurring disciplinary lines.

Managing and Maintaining Quality with AI

• Fiona uses Claude Code for visibility into team work, enabling conversations about impact and quality.
• The principle of "make new mistakes" encourages learning and rapid iteration over avoiding all errors.
• Routines automate feedback aggregation and PR generation, allowing managers to stay on top of increased output.
• Automated Claude Code Reviews, guided by defined frameworks, help maintain quality, evolving the concept of TDD.

Hiring and Team Culture in the AI Era

• Hiring focuses on "creative builders with product sense" and "deep systems experts" for critical areas.
• A growth mindset is crucial for adapting to rapid AI advancements; resisting change leads to frustration and fear.
• Taking initiative and having agency are key traits for thriving engineers, balanced with high accountability.
• The "player-coach" approach, where managers remain individual contributors, fosters product connection and team rapport.
• Maintaining team culture and fostering diverse, honest debate are critical during rapid growth.

The Future of Engineering and AI Adoption

• The future of engineering involves asynchronous workflows, fleets of agents, and higher levels of abstraction.
• Routines and AI agents can automate management tasks, allowing for asynchronous work and focused decision-making.
• The focus is shifting from measuring lines of code to measuring output that drives outcomes and solving problems.
• Fiona emphasizes "just-in-time" (JIT) planning, with monthly cycles checked weekly, and a continuous effort to automate planning processes.
• The "cave you fear contains the treasure you seek" motto encourages embracing scary changes for growth.

Bridging the AI Divide and Personal Reflections

• Fiona advocates for sharing AI knowledge to prevent a widening gap between AI-proficient individuals and others.
• Dogfooding products (using them personally) is essential for leaders to maintain a pulse on user experience and identify issues.
• The anecdote over data principle, exemplified by real-world product usage, is crucial for understanding user needs.
• Key challenges include defining verification processes for AI-generated work and managing context-switching load.
• Fiona's personal journey highlights the importance of continuous learning, embracing new tools, and fostering community.

Product Framework: Proven, Better, New

• Proven: Master existing successful products and features on the current platform for the target audience. Don't innovate on the core experience until you've earned the right.
• Better: Make small, incremental improvements that 10/10 users would agree are better. Focus on polish and power user features.
• New: Introduce a novel, "back of the box" idea that provides a reason to try the product. This is the riskiest element and is most likely to fail.

The "Moral Arbitrage" of Copying

• Innovating often means starting by copying what works. Define ambition through the consumer's eyes, not peer approval.
• Adding a small improvement (one inch better) can be more impactful than something entirely new.
• Masterful copying is done subtly, so users don't perceive it as derivative.

Being Less Ambitious for Greater Success

• Overly ambitious visions at the start can lead to missing product-market fit. Humble beginnings are often the path to massive success.
• Successful founders often start with small, "embarrassingly small" ideas and scale from there.
• The paradox: to build more ambitious products, start with humble, focused goals.

Kill Hope Before Hope Kills You

• Distinguish between belief (founded on data and experience) and hope (confidence without basis).
• Focus on "collecting winnings" (launching with high conviction) rather than "making bets" (hoping an MVP will work).
• Use AI for rapid testing and iteration, building "wrong" quickly to learn, rather than spending months perfecting one idea.

Zingga's Success Factors

• Core mission: Connecting the world through games.
• Focus on "invest, express, and connect" features within games.
• Primary metric: Retention (especially Day 365), not just virality.
• Developed "Active Social Network" (ASN) metric to track user engagement with friends.

Reinventing Social and Consumer Apps

• Identify "latent demand" – what consumers want but isn't readily available.
• Look for the "cocktail party" – a social gathering with energy and value (leads, connection).
• The next wave of social could involve AI agents brokering relationships and providing productivity, making the "cocktail party" rowdy again.

Distribution and AI Platforms

• AI is a powerful technology but not yet a consumer platform. We are still in the mobile/web era.
• Distribution must be integral to the product strategy from the start, not an afterthought.
• The "intelligence on tap" model with decreasing AI token costs presents an innovation zone.
• Future AI platforms may emerge from major LLM providers (OpenAI, Claude) to host agentic services.

Management and Leadership Principles

• Make everyone a CEO of their domain to foster ownership and reduce micromanagement.
• Stay "close to the metal" by remaining involved in product details, even as a founder.
• "Transfer vampire blood" by immersing key individuals in your passion and approach.
• The CEO's primary job is to be right about the product and strategy.

Parenting in the AI Era

• Meet children where they are, engaging human-to-human at their altitude.
• Foster critical thinking and usefulness over rote knowledge acquisition.
• Encourage generative online behavior over passive consumption.

Building Real Products

• Don't surrender to AI: While AI is powerful, humans must remain in control, applying critical thinking and taste to the process.
• Start from pain: Identify customer pain points and leverage new technologies to solve them innovatively.
• The "Why Now": Success hinges on combining a persistent pain with emerging technologies that make a solution feasible.
• Three Generations: Products often require multiple iterations: first to build, then to fix, then to build the business.
• Opinion-Based Decisions: For truly innovative 1.0 products, leadership must make strong, opinion-based decisions, not solely rely on data that may not exist yet.

The Role of Taste and Marketing

• Taste Makers: A small group with vision and "taste" are crucial for making key opinion-based decisions in product development.
• Marketing is Key: Consumers experience products through the lens of marketing; effective storytelling and context are vital.
• Focus on the "Why": Don't just explain what a product does; tell the story of why it matters.
• Customer Journey: Builders must consider the entire customer journey, from discovery to post-purchase, not just the product itself.
• Press Release First: Define the core message and value proposition (like a press release) before starting development.

Innovation and AI

• Hardware + Software: True innovation often lies in the integration of hardware, software, and data, not just software alone.
• AI's Role: AI can be a powerful tool for prototyping and generating ideas, but it requires human oversight for quality and long-term maintainability.
• Long-Term Vision: While AI is evolving, displays will likely remain necessary, possibly with voice becoming the primary interface.
• Ethical Considerations: Product builders must have strong principles and avoid designing for addiction or societal harm.
• Unintended Consequences: Products can have unforeseen impacts (like the iPhone and social media), requiring conscious effort to mitigate negative effects.

AI's Impact and Evolution

• Magnitude of Change: AI is viewed as a transformative technology on par with the internet or mobile, not necessarily more impactful than the Industrial Revolution, but still fundamentally significant.
• Analogy to the Internet: The current AI landscape is compared to 1997 internet adoption, with much potential not yet realized and widespread usage still developing.
• Job Market Transformation: Historically, new technologies automate some jobs while creating new, unforeseen ones. AI follows this pattern, with companies increasing headcount despite automation fears.

Understanding AI Adoption and Value

• Jagged Frontier: AI adoption and effectiveness vary widely, with some, like software developers, seeing immediate, radical change, while others are still figuring out its application.
• Professional Services Role: AI labs are investing in professional services firms because implementing AI solutions requires significant strategic planning and internal workflow redesign, a task for which external expertise is crucial.
• Task vs. Job: The hard part of a job is often not a specific task (which can be automated) but the overarching problem-solving, strategic thinking, and contextual understanding.
• Value Accrual: The true value may not lie with the foundational model providers but further up the stack in the applications and services built upon them, similar to how the internet and mobile ecosystems evolved.

Navigating Uncertainty and Sentiment

• Radical Uncertainty: The future of AI, especially concerning AGI, is highly uncertain due to a lack of understanding of intelligence and current AI models.
• Redefinition of Terms: Concepts like AGI and superintelligence are fluid, with definitions shifting as capabilities evolve.
• Anti-AI Sentiment: Growing negative sentiment stems from tangible concerns like energy consumption, but also from job anxieties, cultural shifts, and misinformation.
• Personal Adaptation: Individuals should engage with AI, understand its capabilities, and adapt rather than ignore it to remain relevant in the evolving job market.

Future Outlook and Practical Advice

• Distribution is Key: When core technology becomes commoditized, distribution channels and brand become critical competitive advantages.
• It's Probably Going to Be Okay: While acknowledging disruption and frictional pain, the overall trajectory historically suggests economic progress and adaptation.
• Embrace and Explore: The best approach is to dive into AI, understand its practical uses, and think about how to leverage it for personal and professional growth.

AI's Impact on Work

• The AI job apocalypse is unlikely; automation requires human oversight and new roles will emerge.
• AI commoditizes existing human competence, making it cheaper, while humans innovate with this new competence.
• Work will bifurcate: individuals will have personal agents for offloading tasks, and work will primarily occur within environments like Codex or Claude Co-work.

Future Work Surfaces & Tools

• Companies will likely adopt a "super agent" model (one per company) rather than individual agents, as maintaining personal agents is too labor-intensive.
• Work will increasingly happen within AI agent environments like Codex/Claude Co-work, which act as an operating system for tasks.
• SaaS tools will run within these AI environments, shifting the focus from building AI into SaaS to creating software for human-AI collaboration.
• CLIs are considered "over" as GUIs within agent environments offer a better user experience.
• The capability for AI agents to access and utilize applications within their own interfaces (e.g., in-app browsers) is a key emerging paradigm.

The Human Element in AI

• Automation does not eliminate work; it creates a need for humans to manage, maintain, and ensure AI systems function effectively.
• Benchmarks may overstate AI autonomy; humans are crucial for framing problems, adapting to new challenges, and guiding AI development.
• The "forward deployed engineer" role, focused on managing and optimizing AI agents, is becoming increasingly important.
• Humans excel at creating novel applications and expertise from AI capabilities, a skill that commoditized AI outputs cannot replicate.

Skills for the Future

• Product Managers (PMs) and full-stack designers are well-positioned for success due to AI's ability to amplify their skills in product sense and creation.
• Individuals should embrace and "ride the models" by actively using new AI tools and staying curious about their evolving capabilities.
• The "edge" of AI is where humans interact with it, driving innovation through practical application and discovery.

Predictions and Advice

• SAS stocks are a good investment, as agents will increase, not decrease, the user base for SaaS tools.
• Companies should prepare for agents to be users of their products, requiring software designed for both human and AI collaboration.
• The key to success is continuous learning, experimentation, and finding "moments of joy" with AI tools.
• While AI-generated writing and code will become commonplace, human oversight and creativity remain paramount for adding value and uniqueness.

Introduction to AI Hardware Boom

• AI acceleration is leading to a vertical surge, with the next frontier being the physical world: robotics, manufacturing, and industrialization.
• The VR industry's innovations (SLAM, depth sensors, human perception of visual data) are directly applicable to robotics and physical AI.
• AR glasses are seen as a future component, but current waveguide and micro-OLED technology isn't ready for mass production due to yield and cost issues.

Challenges in Hardware Development

• Hardware development has a significantly longer "compile" cycle (4-5 times a year) compared to software, demanding a more conservative approach.
• Part variance is a critical consideration; engineers must account for the widest and narrowest versions of components fitting together.
• The supply chain for crucial components like magnets and actuators is a significant bottleneck, with much of the expertise and manufacturing outsourced to Asia.
• Memory prices are a major concern, potentially doubling due to AI demand and supply chain constraints, impacting consumer hardware and robotics.

The Rise of Robotics and Humanoids

• There's a growing interest in robotics and hardware, with computer science enrollment shifting from traditional CS to hardware/robotics.
• Humanoid robots are a focus, but safety concerns exist regarding large, strong humanoids operating near people. Softer, lighter designs with compliant arms are safer.
• Humanoids are still largely in prototype phase; the next steps involve making them cheaper, easier to manufacture, higher yield, and safer.
• Dedicated robots designed for specific tasks (e.g., assembly in manufacturing) are more efficient than general-purpose humanoids for many industrial applications.

AI's Impact and Future of Hardware

• AI is beginning to impact hardware design, with potential for AI to assist with CAD and PCB layout, but it's not yet handling the core "meat and potatoes" of engineering.
• The development of "world models" might be key for AI to understand physics, friction, and other physical properties crucial for engineering.
• The biggest challenge for AI in CAD is the lack of accessible, high-quality training data, as CAD data is valuable proprietary IP.
• The future likely involves more specialized robots for various tasks (construction, electrical work, logistics) rather than solely humanoids.

Leadership and Team Building Lessons

• Learned from Sam Altman to "think bigger" (100x or 10,000x).
• From Steve Jobs, learned the importance of an unwavering bar for technical talent and excellence.
• From Mark Zuckerberg, learned about efficient company operations and making decisions at the lowest possible level for speed.
• Hiring strategy focuses on strong generalists who can adapt learned skills to new fields, combined with specialists in scaling and zero-to-one development.
• "AI native" younger individuals are crucial for teaching how to integrate AI into engineering processes from the ground up.

Insights on Hardware Development Principles

• Be clear on goals and stick to them, as hardware is less adaptable to mid-development changes.
• Design the hardest parts first to identify and address pinch points and risks early.
• Focus iteration on the parts the customer interacts with most (e.g., trackpad, keyboard).
• Embrace ruthless efficiency: do what you know needs to be done *now* because unexpected issues will arise.
• Use off-the-shelf components during prototyping to show proof of concept quickly, then move to custom solutions for mass production if KPIs demand it.
• The ability to define value ratios (e.g., weight vs. cost) is key for making trade-offs.

Failures and Future Outlook

• A key failure on the Quest 1 involved a misunderstanding of camera specifications, leading to a redesign that ultimately improved the product.
• The AI hardware boom is seen as an exciting opportunity for extraordinary progress and individual empowerment.
• Embracing AI tools daily and being creative is key to staying at the forefront of future advancements.
• The future of warfare may see more significant changes than consumer electronics due to AI and drone technology.
• Building a desirable future requires collective design and imagination, not just accepting a potentially dystopian technological trajectory.

Introduction & Core Problem

• Eric Ries, author of "The Lean Startup," discusses his new book "Incorruptible," which addresses how companies lose control and descend into mediocrity despite initial success.
• The core problem is a force that "no one controls but everyone obeys," leading to a decline in quality and loss of control, often driven by financial pressures.

The "Corruption" & Its Manifestations

• This corruption isn't always obvious; it can be tasted in declining restaurant quality or seen in beloved brands becoming worse (e.g., Vital Farms, which was acquired by BlackRock).
• Success itself becomes a liability, as the "golden goose" attracts pressure to "butcher" it for short-term gain.
• Founders often lose control due to standard governance practices, with only 20% remaining CEO three years after IPO.
• Legal and financial advisors often push for "best practices" that, paradoxically, lead to founders losing control.

The "Harder is Easier" Principle

• Ries advocates for "harder is easier": committing to quality, ethics, and integrity upfront, even when costly.
• This builds trustworthiness, which is an underrated business asset, leading to greater loyalty and lower acquisition costs.
• Cloudflare is an example: they incurred costs to offer free SSL encryption, believing "a better internet is an encrypted internet," which ultimately drove growth and trust.
• Contrastingly, Groupon's Groupon's decline is attributed to succumbing to pressure for more emails (ROI-driven decisions) over their core mission.

Ethos and Integrity: The Blueprint

• The solution involves two key components: Ethos (internal alignment, character choices) and Integrity (structural mechanisms to maintain alignment).
• Ethos: Companies must define their "purpose" or "who you'd rather die than betray." This purpose must be encoded into the management system to prevent profiting from betrayal.
• Integrity: This involves creating structural defenses against internal temptation, board-level betrayal, and external pressure.
• The Public Benefit Corporation (PBC) structure is highlighted as an easy, low-cost way to legally embed a mission beyond maximizing shareholder returns. Anthropic is cited as a successful PBC.

Practical Steps for Founders

• 1. Become a Public Benefit Corporation (PBC): Write a mission statement you're genuinely committed to. Test it by brainstorming ways to profit from violating it; if that makes you sad, it's the right mission.
• 2. Implement a Director's Oath: Mandate a "do no harm" principle for board members, similar to the Hippocratic Oath for doctors.
• 3. Secure Founder Control (with a plan for eventual mission stewardship): Utilize founder preferred shares and mission-protected provisions.
• The goal is "mission-controlled" companies, where the mission itself has sovereignty, not just investor or founder control.

Mission Guardianship & AI Alignment

• Anthropic's structure, with a non-profit board of trustees (mission guardians) overseeing the for-profit board, is presented as a robust example.
• This structure protects the company from short-term pressures and aligns with their safety mission.
• The human alignment problem in AI is linked to organizational design; flawed human values can imprint onto AI systems.
• Companies are seen as "emergent intelligences," similar to AI models, requiring careful stewardship.

The Invisible Leader & Lasting Trust

• Mary Parker Follett's concept of the "invisible leader" emphasizes that true leadership comes from instilling a common purpose that guides decisions even when managers aren't present.
• Cultivating this sense of purpose is crucial for enduring trustworthiness, as most consequential decisions happen "when no manager is present."
• The ultimate goal is to build companies that are resistant to corruption, create lasting value, and earn genuine trust.

The AI Era and Agency

• Skills are becoming less important than agency in the AI era.
• Agency is the belief that the world is malleable and you can change things.
• "Could you drive notion like it's stolen?" is a mindset to cultivate agency.

Product Building and Taste

• The first 10% of any project is now "free" due to AI.
• Building the first version of a startup takes minimal effort.
• Taste is the ability to predict what an in-group will like; it requires reps (like training a model).
• Great products have a tiny "superpower" core, not just incremental additions.

Malleable Software and User Experience

• Malleable software works closer to user interests than corporate interests.
• Users want ownership of their computing life, not just pre-defined apps.
• The "SAS apocalypse" is exaggerated; the "as a service" aspect (maintenance, expertise) is crucial.
• Tools will become more general (like 90s software) but remain as a service.
• Focus on usefulness and tinkerability, not just aesthetics.

Developing Agency and "Obviously Good" Products

• "The world is made up by people no smarter than you."
• Making things (tinkering) develops agency and awakens the idea that you can change things.
• Products should be "obviously good" – you know it when you see it.
• Incremental correctness and iterating are key to improving software quality.
• Great products have a tiny, exceptionally good core, not just many features.

The Future of Work and AI

• AI is accelerating "software eating the world."
• Coding agents are winning because they can build necessary skills.
• Token spend is a vanity metric; focus on ROI and utility.
• AI transforms roles by enabling users to build their own tools and workflows.

The Importance of Distribution

• Building a durable consumer social product is extremely difficult; many fail.
• Distribution is often overlooked, while product-market fit receives too much focus.
• TikTok succeeded through massive spending on customer acquisition and creator subsidies.
• Meta leveraged existing distribution for Threads.
• Snapchat's early distribution strategy focused on connecting users with their closest friends, not just the largest network.

Innovation and Moats

• Software is not a moat; AI is making this clear now, as was learned 15 years ago.
• Snapchat built moats through ecosystems (creators, AR developers) and hardware (Spectacles) which are harder to copy than software features.
• Network effects are important but not sufficient; building defensible platforms is key.
• Snap's design team, though small, constantly innovates, with a flat, non-hierarchical structure.

The Future of Computing and AI

• New platforms (like mobile in the past, AR glasses now) create opportunities for generational companies.
• Hardware, specifically AR glasses (Specs), aims to make technology more human and connect people, rather than isolate them.
• Snap's Specs aim to anchor digital content in the real world, offering a different AR experience than HUD glasses.
• AI is enabling designers to ship code and removing friction from the creative process.
• Snap uses AI for internal tools like Glean to help leaders understand company performance and identify priorities.

Humanity Over Technology

• A contrarian view is that humanity, not just technology, dictates adoption and comfort with AI.
• Societal pushback on AI changes is underestimated; a focus on advancing humanity's goals is crucial.

Snapchat's Innovation Culture

• Innovation thrives on having lots of ideas and a high velocity of work and critique.
• Snap models innovation on the dialogue between engineering and design, with a small, iterative design team.
• Design acts as a bottleneck to ensure a cohesive customer experience.
• New designers present work on their first day, emphasizing making things and iterative feedback.

Anthropic's Product Velocity

• Anthropic prioritizes removing barriers to shipping, reducing feature timelines from months to days.
• The key to AI-native products is rapid iteration and launching features weekly.
• Emerging PM skills focus on "product taste" – deciding what to build as code becomes cheaper.

Role of a PM at Anthropic

• Cat Wu (Head of Product, Claude Code) works with tech lead Boris on product vision and execution.
• Cat focuses on cross-functional alignment (marketing, sales, finance) and removing shipping blockers.
• The PM role requires shortening the idea-to-user launch time and defining core product tasks.

Shipping Effectively in AI

• Set clear goals: define target users, problems, and use cases (e.g., "professional developers" facing "permission fatigue").
• Ship features in "research preview" to reduce commitment and gather early feedback.
• Establish tight cross-functional processes (e.g., engineering, marketing, docs) for rapid launches.

Product Strategy and Principles

• Rely on rigorous metrics and weekly readouts to understand business drivers.
• Maintain a list of team principles (key users, their needs, trade-offs) for decentralized decision-making.
• PRDs are used for ambiguous features or those requiring heavy infrastructure.

Moving Faster with Advanced Models

• Shipping speed is driven more by process and team expectations than just access to frontier models.
• The goal is to empower every team member to take an idea from concept to launch within a week, sometimes a day.

Process Failures and Open Source

• A source code leak was due to human error in package release processes, now hardened.
• Prioritizing first-party products and APIs led to the decision to restrict free "open Claude" usage.

PM Team Structure and Evolution

• Anthropic has ~30-40 PMs across research, developer platform, Claude Code/Co-work, enterprise, and growth teams.
• Roles are merging: PMs do engineering, engineers do PMing. Hiring focus is on engineers with strong "product taste."
• Product taste is the most valuable skill, deciding *what* to build, not just *how*.

The Future of Product Management

• The value of skills shifts rapidly with AI advancements; adaptability is key.
• PMs need first-principles thinking to navigate the changing tech landscape and identify/fill gaps.
• Wearing multiple hats and having low ego are essential traits.

Human Value in the Age of AI

• Human brains remain crucial for common sense, understanding stakeholder dynamics, and EQ.
• Dealing with constant change requires embracing chaos, staying calm, and brutally prioritizing.

Sacrifices for Speed

• Product consistency is sometimes sacrificed for rapid feature iteration and testing multiple form factors.
• Users may find it harder to keep up with daily launches, requiring better onboarding and education (e.g., "/powerup" feature).

Anthropic's Success Factors

• A unifying mission (safe AGI for humanity) enables fast, unified decision-making.
• Strong focus and willingness for teams to sacrifice individual goals for the company's mission.

Product Usage and Co-work

• Claude Code: Use in the terminal for one-off tasks, latest features land here first.
• Claude Desktop: Ideal for front-end work (real-time preview), graphical interfaces, and a consolidated view of sessions.
• Web/Mobile: For kicking off tasks on the go.
• Co-work: For non-code outputs (Slack zero, decks, docs).
• Connect data sources (Slack, Calendar, Gmail, Drive) to Co-work for context.
• Co-work can generate polished drafts (e.g., slide decks) by synthesizing information from connected sources.

Key PM Skills for AI

• Defining product direction a month out in an ambiguous AI landscape.
• Eliciting maximum capability from current models, guiding users to their strengths.
• Asking models to introspect on behaviors to identify and fix gaps.
• Identifying trusted users for accurate feedback and building useful evals.

Claude's Character and Personality

• Claude's lighthearted, low-ego, competent, and positive personality makes it enjoyable to work with.
• This personality, developed through careful molding and feedback, is core to Claude's success.

Evolving Product Harnesses

• Newer models reduce the need for features like explicit to-do lists, as models naturally handle complex tasks.
• Prompt interventions are removed as models improve; new models unlock entirely new features (e.g., advanced code review).
• Build products that might not fully work yet, anticipating model capabilities to catch up.

Vision for Claude Code and Co-work

• Core building block: consistently achieving single-task success.
• Progression: multi-tasking, running hundreds of agents remotely, and self-improving infrastructure.
• Focus on seamless interfaces and robust verification for human trust.

Advice for AI Adoption

• Automate repetitive tasks using AI tools to free up time for creative work.
• Aim for 100% success rate in automations; the last 5-10% is crucial.
• Build AI apps you use daily to realize actual leverage and value.

The Changing Landscape of Product Management

• The role of a Product Manager (PM) is undergoing a significant transformation.
• Skills focused on "moving information" are becoming obsolete.
• There's a current "renaissance" for builders in product, with high compensation and more opportunities.
• However, this comes with increased stress, constant change, and a need for continuous learning (every 3 months).

AI's Impact and the Rise of Builders

• Companies are shedding staff and rehiring for "AI-first" roles, requiring new skill sets.
• Builders (those who love to create and develop) will thrive, while "information movers" are in trouble.
• AI is automating many of the tedious, mechanical aspects of product development.
• PMs are increasingly expected to focus on "judgment" – evaluating what to build and why.
• AI tools can now rapidly improve software, leading to higher quality and less tolerance for bugs.

Skills for Future Product Managers

• Judgment: Evaluating what is good or bad, making strategic product decisions, and ensuring sustainability and differentiation.
• Pace and Agency: The next 2 years require high energy, initiative, and a willingness to push forward.
• Building Mentality: A genuine love for creating and developing products is crucial.
• Obsoleting Oneself: Continuously learning and adapting to new tools and methods, similar to a great engineer.
• Egolessness: Being open to smaller roles or different paths to stay current and relevant.
• Long-Term Focus: Prioritizing staying modern and adaptable for future opportunities.

Challenges and Opportunities

• Half of current PMs, those who are not "builders," are at risk of becoming dinosaurs.
• Mid-career PMs face unique stresses due to family, aging parents, and career demands.
• There's a concern about a step back in diversity due to AI's geographic concentration and hiring biases.
• The value of established brand names on resumes is diminishing; modernity and current skills are key.
• The "deal" has changed: hard work and experience are not enough; continuous reinvention is necessary.
• Finding joy in the process, particularly through building with new tools, is the antidote to burnout and fear.

Advice for Thriving

• Embrace reinvention and prioritize staying current.
• Find moments of joy by using new tools to solve your own problems or build small projects.
• Increase your pace and demonstrate agency; bring your "best foot forward" in this evolving landscape.
• Swallow your ego and be open to roles that allow you to stay current, even if they seem smaller.
• Focus on the "skip" job or opportunity – what's next after the next move.
• Product Managers are becoming "agents of change" across industries, not just in tech.

Hiring and Team Building

• The most crucial lesson is that the team you build is the company you build.
• Focus on identifying, retaining, and promoting people with talent.
• Founders who can ruthlessly and accurately assess talent early on can go very far.
• Hiring is like a muscle; it needs to be exercised and improved through practice and learning.
• Be excellent at references; aim to exhaust references until you hit a negative one.
• When reference checking, ask the right questions to extract the most valuable information.
• For candidates, ask: "If you were CEO, what would you have done differently?" and "What would lead to this person being most successful, and what would be the primary root cause of failure?"
• Use a 30-day feedback loop after hiring to assess the decision's accuracy.

Barrels and Ammunition Framework

• A "barrel" is an individual who can independently drive an initiative from inception to success.
• Hiring more people without increasing the number of "barrels" leads to inefficiency and increased coordination tax.
• The ratio of "barrels" to "ammunition" (resources) dictates the number of initiatives that can be pursued.
• Barrels are characterized by strong agency, the ability to motivate, accumulate resources, and deliver outcomes regardless of obstacles.
• Taylor Francis, an intern, is an example of a "barrel" who solved the 9 PM smoothie problem.

Attracting Top Talent

• Selling the vision and mission is crucial.
• Convince top talent that their specific skills align with the company's critical blockers.
• Focus on hiring undiscovered talent rather than competing for already recognized individuals.
• Younger candidates may have less data, making them easier to assess for unique potential.
• Companies that thrive often skip hiring senior people and focus on developing talent internally.

The Role of the CEO and Performance

• The CEO's primary role is to offset complacency, especially as the company experiences success.
• When a company is struggling, be supportive and coach-like; when thriving, be critical to identify future problems.
• High-performance organizations are about winning, not necessarily psychological safety.

AI and the Future of Work

• AI will radically reorient careers; intellectual curiosity is key to thriving.
• The CMO is becoming a major consumer of AI tokens, bypassing traditional dependencies.
• The traditional Product Manager (PM) role may become obsolete as AI enables rapid adaptation and direct execution.
• The future PM, designer, or engineer needs CEO-like skills: understanding "what to build and why."
• Business acumen and understanding the company's business equation are crucial skills.
• Engineers with strong commercial instincts will be highly valuable.
• Design and code are merging; the alpha is in storytelling and how to compellingly frame concepts.
• AI content will eventually surpass human content, leading to a bifurcated market of curated human-created content and algorithmically ranked best content.
• Writing quality in AI is currently limited by token rationing, not inherent inability.
• The most impactful part of writing (like the first three sentences of a brief) requires significant human thought and distillation.

Customer Interaction and Insights

• For consumer, SMB, or micro-merchant products, avoid talking to customers; they often don't know what they want.
• Rely on instincts, experience, and foundational insights rather than customer feedback for these products.
• Customer feedback can be harmful and misleading for non-enterprise products.
• Enterprise customer development works because there are specific decision-makers.
• Trust your insights; the best companies often have a foundational insight that customers can't articulate.

Startup Philosophy and Investment

• Invest in ideas that others might laugh at; these are often "ugly babies" with high potential alpha.
• Look for founders with a non-zero chance of changing an industry or the world.
• Successful companies exhibit early speed and a high operating tempo, with rapid execution between problem identification and solution deployment.
• Look for companies building accumulating advantages and unfair advantages over time.
• Be wary of foundational AI labs becoming so proficient that they eliminate the market for other startups.

Criticism and Performance

• Criticize people in public to inform the entire team and foster a collaborative approach to problem-solving.
• This approach is about winning and ensuring the team is aware of and addresses issues collectively.
• High-performance machines prioritize winning over psychological safety.

Personal Philosophy and Habits

• "No days off" is a motto signifying a belief in avoiding excuses and maintaining consistent effort.
• Prioritize sleep and physical well-being, even when busy.
• Success requires embracing stress, not avoiding it.
• Watching historical documentaries like "Nuremberg" can offer valuable lessons.

Company Growth

• Anthropic experienced unprecedented growth, from $1 billion to $19 billion ARR in 14 months.
• Their revenue doubled in recent months, with 10x year-over-year growth.
• This growth is attributed to being an intelligence company first, with a top-tier research team, inference, and compute capabilities.
• The company culture emphasizes exponential thinking, with linear charts considered "not cool."

Getting Hired & Role of Growth

• Amole landed his Head of Growth role at Anthropic through a cold email to the Chief Product Officer, leveraging his expertise in cold outreach.
• The growth team focuses on acquisition, activation, and monetization, similar to traditional companies.
• Approximately 70% of Amole's time is spent on "success disasters" – firefighting issues arising from rapid scaling.
• The remaining 30% is dedicated to proactive growth initiatives, pricing, packaging, and new product launches.
• A key growth move was enabling memory import from ChatGPT to improve user activation.

Product & Activation Strategies

• Activation is a critical challenge in AI products, requiring users to quickly understand the product's value.
• The importance of early activation (Day 0/1 experience) has exponentially increased.
• Capability overhang is a challenge, where rapid model improvements outpace product integration.
• "Good friction," or adding steps that help users understand the product and its relevance, can improve conversion and retention.
• Onboarding at Anthropic involves asking users about their interests to recommend relevant products and features.

Organizational Structure & Strategy

• The growth team at Anthropic comprises around 40 people, structured with platform/monetization horizontals and audience-focused pods (e.g., B2B, Claude Code).
• The team prioritizes larger bets over smaller optimizations, reflecting the company's focus on exponential growth.
• The core value proposition of AI products is expected to increase exponentially, justifying larger bets.
• The company emphasizes a "freedom through constraints" philosophy, using limitations to drive focus and innovation.

AI & Automation in Growth

• Anthropic is automating growth experimentation through an initiative called "CASH" (Claude Accelerates Sustainable Hypergrowth).
• This involves using Claude to identify opportunities, build features, test, and analyze results, aiming for higher win rates.
• While human oversight is still needed for brand and alignment, AI is increasingly handling tasks like copy changes and minor UI tweaks.
• The "notebook channel" feature facilitates transparency and knowledge sharing, helping scale leadership's beliefs and views.

Product Development & Collaboration

• AI is significantly augmenting engineering productivity, potentially creating bottlenecks for PMs and designers.
• Anthropic is exploring deputizing engineers as "mini-PMs" for smaller projects (<2 weeks of engineering time).
• PMs are encouraged to focus on higher-leverage activities like identifying opportunities and improving strategic direction, rather than solely shipping code.
• Documentation is de-emphasized in favor of rapid prototyping and direct communication (e.g., Slack).
• AI tools are being used to identify misalignments and streamline cross-functional coordination.

Company Culture & Mission

• Anthropic operates as a Public Benefit Corporation (PBC), legally prioritizing public benefit alongside shareholder value.
• The company's mission is to ensure the transition to powerful AI is beneficial for humanity, even at a commercial cost.
• There's a strong emphasis on AI safety and alignment, influencing product decisions and experimentation.
• The company culture is described as mission-driven, with high talent density and a high degree of openness and transparency.
• Leadership actively invests in culture, fostering a sense of togetherness and encouraging open debate.

Personal Journey & Resilience

• Amole experienced a severe traumatic brain injury, requiring extensive recovery and impacting his ability to work.
• He also suffered a re-injury while at Mercury, highlighting the challenges of recovery and the importance of managing health.
• These experiences have fostered resilience, adaptability, and a focus on well-being, including meditation and breaks.
• Amole's past failure in founding and shutting down a startup taught him valuable lessons about long-term perspective and investor relations.
• He emphasizes the importance of adaptability and discarding old playbooks when entering new environments.

Advice for Future Careers

• Stay on top of AI tools (e.g., Claude, Co-work) and model releases to improve productivity and product sense.
• Lean into unique interdisciplinary skill sets (e.g., founder background, finance, sales) for competitive advantage.
• Be adaptable and willing to discard past operating methods when entering new, rapidly evolving fields.
• Focus on becoming the best at a specific skill set rather than trying to be average at many.
• For AI-first product roles, embrace larger bets and an exponential mindset.

AI State of the Union & Inflection Point

• The year 2025 saw a significant shift with AI models (like Claude Code and OpenAI's GPT 5.1, Claude Opus 4.5) becoming exceptionally good at generating code.
• This improved capability crossed a threshold where AI-generated code often works as intended, unlike previous versions that required extensive debugging.
• Software engineers experienced a realization in early 2025 that AI could now produce functional code in large volumes (e.g., 10,000 lines a day).
• This advancement positions code generation as a bellwether for other knowledge work fields, highlighting the challenges of verifying AI output.

Agentic Engineering & What's Possible

• Vibe Coding: A hands-off approach where users describe what they want, and the AI builds it without the user necessarily looking at the code. This democratizes creation but carries risks for non-personal use.
• Agentic Engineering: The professional practice of using AI coding agents to build production-ready software, emphasizing depth of experience and understanding of both software and agent capabilities.
• Individuals can now perform complex tasks on their phones, like writing significant amounts of code while walking.
• AI can rapidly generate prototypes, making ideation and exploration much faster (e.g., prototyping three versions of a feature in the time it used to take for one.

The Dark Factory & Software Automation

• Dark Factory Pattern: A futuristic concept where software is built and deployed with minimal human oversight, akin to automated factories operating without lights.
• Companies are implementing policies where engineers do not type code directly, relying on AI agents instead.
• Testing is being reimagined with "swarms of agent testers" simulating end-users to rigorously test software, even for security-sensitive applications.
• This involves simulating complex systems (like Slack and Jira) using AI to create realistic testing environments.

AI & The Future of Software Engineering

• AI is becoming increasingly capable in security penetration testing, surprising security researchers.
• The bottleneck is shifting from code writing to idea generation and validating those ideas.
• AI excels at the initial, obvious brainstorming phase, while humans are still crucial for combining ideas and finding novel directions.
• Experienced engineers with deep expertise are amplified by AI, becoming more valuable.
• Junior engineers benefit from AI assistants for faster onboarding.
• Mid-career engineers may face the most significant challenge as they lack the experience to amplify or the beginner's advantage of AI assistance.
• Advice for mid-career professionals: embrace AI, focus on skill amplification, learning, and taking on ambitious projects.
• Working with AI can lead to increased intensity and mental exhaustion, even if it means more free time.
• The ability to rapidly prototype and build with AI is making personal ambition a key driver for what can be achieved.
• The value of "artisanal," human-written code might increase as a signal of quality and trustworthiness.
• Data labeling companies are reportedly seeking pre-2022 code (before widespread LLM adoption) for training models.
• It's predicted that 50-95% of engineers' code could be AI-generated by the end of the year, though cultural differences in AI adoption exist.

Agentic Engineering Patterns & Best Practices

• Code is Cheap: The core idea that code generation is now vastly accelerated, shifting focus to ensuring code quality and preventing technical debt.
• Prototyping is Nearly Free: AI enables rapid creation of multiple prototypes, fundamentally changing product design and exploration.
• AI Stack: Claude and GPT 4.5/5.4 are primary tools, with Claude Code for web favored for its phone accessibility and reduced local risk.
• "YOLO Mode" (Dangerously Skip Permissions): Disabling safety checks allows agents to run with less interruption, but is inherently unsafe.
• AI as Search Tool: AI models with search integration are often preferred over direct Google searches for research.
• Pelican Riding a Bicycle Benchmark: A humorous test showing a correlation between an LLM's ability to generate an SVG of a pelican on a bicycle and its overall quality.
• Hoarding Knowledge: Building a personal backlog of solved problems, techniques, and code snippets (stored in GitHub repos or notes) to leverage later.
• Test-Driven Development (TDD): Crucial for AI agents. Prompting agents with "red/green TDD" encourages them to write tests first, ensuring code works and doesn't break existing features.
• Starting Templates: Using well-structured boilerplate code helps AI agents adhere to preferred coding styles and patterns.

Prompt Injection & The Lethal Trifecta

• Prompt Injection: A vulnerability in AI applications where malicious instructions embedded in user input can override the system's original prompt, leading to unintended actions. This is a software, not model, vulnerability.
• Lethal Trifecta: A specific, dangerous subset of prompt injection involving three conditions: access to private information, exposure to malicious instruction, and a mechanism for data exfiltration.
• Solutions are difficult because LLMs struggle to distinguish between trusted instructions and malicious input text.
• The "normalization of deviance" (similar to the Challenger disaster) occurs as developers take increasing risks with AI due to the lack of headline-grabbing failures so far.
• A potential solution involves splitting agents into privileged and quarantined components, with human oversight for high-risk actions, though practical implementations are still emerging.

Open Source & The Future of AI Assistants

• Open Claw (Clawbots): A popular open-source project enabling personal AI assistants with broad access capabilities, demonstrating immense user demand.
• The rapid development and adoption of Open Claw highlight the desire for personal digital assistants, even with significant security risks.
• Building a safe and secure version of Open Claw presents a major opportunity.
• The term "Claw" is becoming a generic term for these AI assistants, with "Hello World" for AI engineering potentially being building one's own Clawbot.
• The Spider-Man 2 reference to "AI claws" (Doc Ock's mechanical arms) is noted as a relevant connection.

Simon's Work & Advice

• Simon is focused on building open-source tools for data journalism, aiming to help journalists uncover stories using data.
• He sees AI as a valuable tool for journalism, treating AI as another "unreliable source" that journalists are equipped to handle.
• His goal is to contribute to Pulitzer Prize-winning journalism through his software.
• He is also writing a book/project on "agentic engineering" and his blog is becoming financially self-sustaining.
• He practices "zero deliverable consulting," offering focused, short-term advisory calls.
• Excellent news: A successful breeding season for the rare Kakapo parrot in New Zealand is highlighted.

Initial Skepticism and Transformation

• Claire Vo was initially a skeptic of OpenClaw, spending 8 hours on setup and losing her family calendar.
• Despite the rocky start, she recognized its potential due to the "joy and utility" it offered.
• Now, she's a "breathless OpenClaw bro," running eight agents and finding it life-changing.

The Power of Multiple Agents

• A key unlock was realizing OpenClaw's strength lies in using multiple, specialized agents rather than one for all tasks.
• Trying to assign too many diverse tasks to a single agent leads to frustration due to context overload.
• Claire now manages a team of agents (Polly, Finn, Max, Howie, Sam, Kelly, Holly, Sage, and Q) across three computers.

Practical Use Cases

• Personal Assistant: Managing complex family schedules (kids' activities, school, appointments).
• Salesperson (Sam): Automates CRM sweeps, identifies prospects, drafts initial emails, handles enterprise leads, and cleans up the pipeline. This saved Claire 10 hours/week previously paid to a human.
• Meeting Prep (Howie): Provides reminders, relevant links, and context for podcast recordings and other meetings, making the user "look good."
• Family Logistics (Finn): Manages ad-hoc scheduling conflicts (e.g., basketball games vs. soccer), pings about kid pickups, and sends timely reminders for appointments.
• Course Project Management (Sage): Assists with launching a new course by project managing, drafting marketing posts, and organizing research content.

Setup and Security Recommendations

• Dedicated Machine: Recommended to start with a clean, dedicated machine (old laptop, Mac Mini, or cloud instance) to avoid security risks and interference with personal/work computers.
• Separate Accounts: Create a dedicated local admin account and a separate Gmail account for each OpenClaw agent.
• Progressive Trust: Grant access gradually, similar to onboarding a human assistant. Start with calendar access, then email, and cautiously expand.
• Privacy by Default: OpenClaw's default is personal use; agents are designed to work with the user, not in group chats.
• Model Choice: Opt for more advanced models (Opus, Sonnet, GPT-4) for better security and performance, despite higher costs.
• Communication Channel: Telegram is suggested as a beginner-friendly way to interact with agents, though other options like voice notes, email, and Slack are available.

Overcoming Challenges

• Browser Unreliability: The web is hostile to bots; APIs are preferred. If using the browser, dedicate specific browser profiles per agent and accept trial-and-error.
• Memory Issues: Focus on managing context and using agent-specific "memory files" or prompting the agent to save key information.
• Tool Usage: Carefully review and potentially manually edit the `tools.md` file to ensure agents correctly understand and use their available tools.
• Mac Mini Setup: Utilize Screen Sharing or Remote Login (SSH) to access headless Mac Minis without needing a dedicated monitor/keyboard after initial setup.
• Google Workspace Integration: Use the GOG tool for seamless integration with Google Workspace (Docs, Sheets, Email) for agent task management.
• Agent Project Management: Have agents assign tasks to *you* (e.g., creating Linear tickets) to help manage your own to-do list.
• Prompting: Use voice notes for "rambling" input during onboarding for higher bandwidth and more natural interaction.
• Code Execution: For complex issues, consider using a tool like Claude Code to debug or manage OpenClaw configurations.

The "Soul" and "Heartbeat" of Agents

• OpenClaw agents feel "alive" due to their encoded identity ("soul"), personality, and scheduled tasks (heartbeat).
• The "soul" defines the agent's purpose, personality, and operational guidelines (e.g., security protocols, communication style).
• The "heartbeat" allows agents to proactively check for tasks at set intervals (e.g., every 30 minutes).
• This structured identity and proactive scheduling enable agents to function collaboratively and feel more like proactive team members.

The Future of AI and OpenClaw

• OpenClaw is a fast-growing open-source project, seen by some as the "new computer."
• The current state, while imperfect, offers immense potential for personalization and agentic workflows.
• Claire believes the ability to "own and craft" these agents is empowering, foreshadowing the next wave of AI products.
• The success of OpenClaw highlights the importance of management and organizational skills in effectively deploying AI agents.

The Importance of Influence

• Influence is the single most important leveraged skill for product leaders, especially as AI capabilities grow.
• Great products are built by building momentum and gaining buy-in from key stakeholders and executives.
• Failing to influence leaders is the product leader's responsibility, not the leader's fault.

Understanding Executive Decision-Making

• Executives have extremely busy calendars with constant context switching; your problem is not their primary focus.
• To influence them, help them get into the right mindset by providing context at the start of meetings.
• Executives optimize for a global maximum, not the local optimum you might be focused on.
• Use curiosity and empathy, skills typically reserved for users, when interacting with executives.
• Frame executive conversations as discovery interviews to strengthen your ideas.

Tactics for Effective Influence

• Align with Executive Goals: Understand their incentives, goals, and how they are measured. Connect your pitch to their success criteria.
• Ask Better Questions: Instead of "What's top of mind?", ask "What is the board pushing you on?" or "What pressures are you facing?"
• Go in to Learn: Approach conversations with a learning mindset, not just to get approval.
• Leverage AI Tools: Use tools like Slackbot or custom GPTs trained on past reviews to anticipate pushback and identify weaknesses.
• Offer Options: Present multiple options (e.g., the "Goldilocks" approach) to show thorough consideration.
• Prepare for Deep Dives: Have detailed information (e.g., in an appendix) ready if executives want to explore the process.
• "Stuart Plus Two More": A tactic where you do what's asked, plus two other versions, to foster discussion and debate.
• Understand Communication Preferences: Tailor your presentation style (doc, presentation, data focus) to the individual executive.
• Start with the "Why": Explain the company goals and user outcomes your proposal supports.
• "That's so interesting. What led you to believe that?": A phrase to understand the executive's reasoning and co-create solutions.
• Take the Reins: Act like a CPO, come with solutions, and follow up on subtle cues from executives promptly.
• Shrink the Change: Break down large, scary ideas into smaller experiments or proof-of-concepts to build trust and momentum.
• Kill Things: Deprioritizing or killing initiatives that aren't working is a sign of senior thinking and builds trust.
• Red Teaming: Apply an outsider's perspective to your ideas to avoid getting too attached and recognize potential failure.
• Manage Certainty: For initiatives with uncertain outcomes (especially AI-native products), establish clear check-in points for certainty.
• Broaden Your Context: Understand the executive's broader context, including what other teams are working on and company-wide discussions.
• Think Like a Business Owner: Consider the company's overall goals and success, not just your feature or team's objectives.
• Build Trust Through Results: Demonstrate impact, ship great products, and communicate those successes back to leadership.
• Ask About Urgency: Clarify how strongly executives feel about a request to gauge its priority.
• Context Setting: Start meetings with a brief (30-60 seconds) overview of the topic, previous discussion, and today's goals.

Influence vs. Politics

• Politics is manipulating people for personal gain; influence is increasing the odds that good ideas survive.
• Focus on genuine learning and strengthening ideas through stakeholder conversations.

How AI is Changing Influence

• AI excels at execution tasks (data analysis, note-taking, experimentation), shifting the PM's role to idea generation and influence.
• The core skills of user empathy, curiosity, and influence become even more critical.
• AI empowers faster V1 development, making influence crucial for funding subsequent versions (V2, V3, etc.).
• AI can act as a smart colleague, helping to poke holes in ideas and provide corporate context.
• Strategy clarity is paramount in an age of AI-driven rapid development to guide efforts effectively.
• Agents can be trained on product philosophy and historical context, mirroring the need to influence them with our own insights and guardrails.

Personal Growth and Authenticity

• Influence is not about being manipulative but about genuine connection and understanding.
• Be authentic to your personality type; your strengths are your superpower.
• Show up as a strategic leader by broadening your perspective beyond your immediate domain.
• Product citizenship—mentoring, sharing best practices, and connecting work to company goals—is key for career growth.

Negotiation Fundamentals

• Mistake: Hiding behind email for negotiations, losing control of tone and reception.
• Common Fear: Appearing greedy or causing the deal to fall apart.
• Core Philosophy: Clearly articulate the pain you solve for the company and why your compensation reflects that value.
• Value Discrepancy: Companies often gain 5-100x more from employees than they pay them.
• Negotiation is Not Confrontational: It's a collaborative process focused on mutual value exchange.

Compensation Benchmarks & Growth

• "What's the chance there could be more?" Simple pushback can yield a 20% increase.
• Average Target: Aim for 40% movement on compensation increases.
• Breaking Bands: Salary bands are not always rigid; challenging them collaboratively can lead to significant gains.
• Introverts vs. Extroverts: Product, engineering, and design roles (often more introverted) tend to negotiate less effectively than marketing and sales roles.
• Beyond Base Salary: Negotiate creatively with performance incentives, milestone triggers, stock, or cash bonuses tied to company growth.

Tactical Negotiation Strategies

• Negotiation Starts Early: Public perception (LinkedIn, headshots, shared narratives) influences how you're valued.
• Avoid Email Negotiations: Opt for video calls or in-person meetings to control tone and read body language.
• Negotiate with Decision-Makers: Go directly to the person who controls the P&L or budget, not just recruiters.
• Control the Time & Place: Choose meeting times when you are most effective and consider "home field advantage" by meeting outside the office.
• Gratitude and Enthusiasm: Start by expressing appreciation for the offer to signal commitment.
• The "Vacation" Analogy: Help the company visualize a positive future state achieved with your help to sell your value.
• Information is Power: Companies have significant information advantages; gather as much as possible.
• Never Split the Difference: This can lead to missed opportunities; instead, ask clarifying questions.
• Patience is Key: Slow down the process to gather information and build a compelling case.
• Leverage Emotion (Tactical Empathy): Appeal to logic, credibility, and emotion for a stronger negotiation.
• Collaboration, Not Confrontation: Frame discussions as a joint problem-solving effort.
• "We" vs. "Me": Frame requests in terms of mutual benefit or company-wide improvements.
• Get Creative: Explore non-salary compensation like company cars or other perks if budgets are capped.
• Don't Overpromise, Overdeliver: Be confident but realistic in your proposed solutions.

Mindset and Overcoming Fear

• Value Exchange: Understand the immense value you create for a company.
• "Failing Forward": Over-negotiating and being "slapped down" can still lead to growth.
• Authenticity is Key: Negotiate in your authentic voice; attempting to impersonate others can backfire.
• Confidence Boosters: Reframe the job search as a sales or product development process; remind yourself of past successes.
• Take Chances on Yourself: Even failure is learning and leads to growth.
• Wealth is Not Inherently Bad: Don't fear wealth; understand and potentially influence it.

Specific Scenarios & Nuances

• Recruiter Questions: If asked for your number early, deflect by focusing on understanding the role and value first.
• If an Offer is Rescended: Approach with honesty, ownership, and transparency.
• Gender & Cultural Differences: Negotiation tactics need to adapt to individual and cultural nuances.
• IC vs. Leadership Roles: While pay may differ, the negotiation approach can be similar; focus on value and use objective criteria.
• When Things Go Sideways: Take ownership, be honest, and try to reset the conversation.
• Information Asymmetry: Companies negotiate far more often than individuals, highlighting the need for preparation.

Newsletter and Podcast Success

• Lenny Rachitsky's newsletter has over 1.2 million subscribers and his podcast is consistently in the top 10 tech podcasts.
• His success stems from practical, experience-based advice from practitioners, often featuring guest posts.
• He believes the best advice comes from those "doing the thing for real."

Origin of the Newsletter

• Lenny initially pursued a traditional startup path but found himself drawn to writing about his learnings.
• A key turning point was a conversation with a VC friend who encouraged him to pursue writing because he enjoyed it and people valued it.
• He committed to a weekly newsletter on Substack for nine months, leading to the realization he could sustain it long-term.
• The introduction of a paywall was prompted by financial uncertainty during COVID-19, and it proved successful.
• A profound psychedelic experience in Joshua Tree, where he felt a strong internal message of "I have wisdom to share," solidified his confidence.

Maintaining Fulfillment and Dealing with Stress

• Lenny finds his work fulfilling and interesting, enjoying the process of extracting wisdom.
• He acknowledges the "treadmill" aspect of consistent content creation but emphasizes that it's part of the process.
• He attributes his relatively low stress levels to a combination of genetics and actively working on his mindset, focusing on not taking things too seriously.
• A transformative experience was a University of Pennsylvania online course on the psychology of happiness, which taught him to increase his baseline happiness through positive thinking.

Wife's Interview and Her Work

• The interview is conducted by Lenny's wife, Michelle Rial, who is releasing her third book, "Charts for Babies."
• Michelle creates popular, shareable charts that synthesize life experiences, often making her laugh or feel something deeply.
• Her charts go viral due to their simplicity, ease of digestion, and emotional resonance.
• She finds inspiration by living life, observing, and meditating, which helps her notice patterns in her own thinking.
• Michelle's process for creating charts involves a "bomber peak" concept with coffee, leading to genius ideas but also requiring her to manage the subsequent panic.
• She emphasizes the importance of experiences and observation in generating ideas, noting that a children's book written before having children was less successful than one written after.

Past Projects and Personal Insights

• Lenny previously ran "atheistpot.com," a Reddit-like site for atheist news, which was monetized through ads for religious dating sites.
• He was also involved in "Tutorials," a platform for user-generated how-to guides, considered ahead of its time.
• His startup "Local Mine" allowed users to ask questions about places via Foursquare/Gala integration, but was ultimately deemed unnecessary for a sustainable business.
• Lenny's real name is just "Lenny," derived from his parents changing his given name Leonid to Lenny upon becoming US citizens.
• He admits to having face blindness, making it difficult to recognize people, which can be challenging when people approach him.

Challenges and Stressful Moments

• A significant business stressor involved a product launch with an overly generous offer that attracted fraudsters, requiring extensive work with Stripe and Substack to resolve.
• A deeply personal and stressful event was his wife's complicated childbirth, where an epidural went awry, leading to an emergency C-section and intubation.

Creative Process and Advice

• Michelle's creative process for charts involves observing life, noticing details, and visualizing ideas mathematically.
• Lenny's newsletter writing process involves extensive iteration (around 50 times per post) and refinement, followed by editing and design.
• Both emphasize that the best advice comes from practical experience ("doing the thing").
• Simplifying complex ideas is crucial for effective communication.

About Applied Intuition and Qasar Younis

• Applied Intuition is a $15 billion, under-the-radar AI company that adds AI to vehicles like cars, tractors, planes, and submarines.
• 18 of the top 20 automakers are customers, along with major construction, mining, trucking companies, and the Department of Defense.
• Qasar Younis, co-founder and CEO, grew up on a farm in Pakistan and started his career as an engineer at GM and Bosch.

Vision for AI's Impact

• AI is poised to bring about an "industrial revolution" of benefits, similar to the past, leading to broader access to healthcare, goods, and services.
• Net human suffering should decrease significantly due to AI advancements.
• Physical AI will bring autonomy to industries like farming, mining, and construction, which are facing labor shortages due to an aging workforce.
• AI can democratize access to mobility, making self-driving cars accessible to everyone, potentially freeing people from disabilities and poverty.

Addressing AI Anxiety

• The root of fear surrounding AI is misunderstanding; learning about its limitations can alleviate anxiety.
• Videos of advanced robots (like nunchuck-wielding ones) can be misleading, often representing pre-programmed machinery rather than sentient beings.
• The anxiety around robots in entertainment is often greater than for robots in familiar industrial settings (like car factories) because the underlying technology is less understood.
• The true impact of technological shifts, like the advent of AI, can be both positive and negative, but society can guide its development for good.
• Investors' reactions to AI stocks are often driven by market speculation and misunderstanding of the technology's long-term viability, not necessarily societal fear.

The Future of Physical AI and Robotics

• AI will be integrated into existing physical systems, rather than necessarily leading to humanoid robots taking over all tasks immediately.
• Self-driving cars are already significantly safer than human drivers and will become more ubiquitous, reducing injuries and deaths.
• The impact of AI will be profound in industries like farming, mining, construction, and trucking, addressing labor shortages and improving safety.
• While humanoid robots are visually striking, the more immediate and pragmatic impact of AI will be in enhancing existing machines and vehicles.
• The evolution of AI in vehicles is similar to the progression of mobile technology, with advanced capabilities emerging rapidly once enabling hardware and infrastructure are in place.

Applied Intuition's Philosophy and Values

• Applied Intuition's core values are "radical pragmatism" and "our best work is done alone and quietly," inspired by companies like Berkshire Hathaway.
• Qasar's philosophy, influenced by his background, emphasizes focusing on product and customers over public promotion, especially for early-stage companies.
• Key company values include speed, never disappointing the customer, technical mastery, high output, and "laugh a lot" for perspective and grounding.
• "Half the work is follow-up" is another crucial operating principle, highlighting the importance of execution.
• The company emphasizes a "cleaning zen" where everyone participates in maintaining the workspace, fostering a sense of shared responsibility and attention to detail.
• Applied Intuition has operated without spending raised capital, a testament to its efficient and pragmatic approach.

Advice for Founders and Leadership

• Successful companies tend to show traction early; founders struggling after two years should consider if the core foundation (co-founders, market, or personal commitment) needs resetting.
• Founding a company is a craft that improves with practice; the first few years should be viewed as a learning process, not necessarily an immediate success.
• Founders should be humble, learn from diverse experiences (including working in large organizations), and seek out perspectives beyond their immediate industry.
• It's crucial to encourage dissent and diverse viewpoints within a company to ensure the best ideas surface and that the company doesn't lose its way due to momentum or a fixed vision.
• Leaders should strive to make decisions based on rational analysis rather than emotion, focusing on the objective best course of action and then managing the human element.
• Founders must be right; the ultimate evidence of success is a sustainable, standalone business, not just a vision or rapid fundraising.
• Taste in leadership is developed through broad life experiences and the ability to discern good ideas and judgment, not just technical expertise.

The Design Process is Dead

• The traditional design process, once treated as gospel, is now considered dead due to the rapid pace of engineering enabled by AI.
• Designers no longer have the time for extensive mockups; the focus has shifted.

The Evolving Role of Designers

• A significant part of a designer's role is now supporting engineers and teams in execution, rather than just handing over designs.
• Mocking and prototyping now constitute a smaller portion (30-40%) of a designer's work, down from 60-70% previously.
• The remaining time is spent collaborating closely with engineers, providing feedback, and even implementing polished features ("last mile" work).
• Design visions are now shorter-term (3-6 months) and often take the form of prototypes guiding direction rather than elaborate decks.
• Human brains remain valuable for making final decisions, establishing accountability, and discerning what truly matters.

AI's Impact on Design Workflow

• Engineering advancements, like the ability to spin up multiple agents quickly, are forcing design processes to adapt.
• AI tools like Claude Code assist in idea generation and can even help with execution.
• The non-deterministic nature of AI models makes traditional mockups less effective; real-world testing with actual users is crucial.
• Designers are increasingly working within the AI stack, using tools like Claude Chat, Claude Co-work, and Claude Code (integrated with VS Code).
• Figma remains valuable for exploring diverse options and refining visual/interaction details, as current coding tools are more linear.

Maintaining Quality and Trust

• In a fast-paced environment, launching "research previews" with acknowledged flaws is acceptable if the core value is evident and iteration is promised.
• Building trust is achieved through speed, responsiveness to feedback, and demonstrating continuous improvement.
• This approach of rapid iteration and user feedback is crucial for maintaining brand integrity.

The Future of Human Value in Design

• AI will likely improve in areas like taste and judgment, but humans will still be needed to make final decisions and be accountable.
• The hardest parts of building software often involve human disagreements and decision-making, which AI cannot fully resolve.

New Interfaces and Human-AI Interaction

• A combination of traditional UIs and conversational interfaces (like chatbots and terminals) will persist.
• Widgets and interactive elements offer efficiency, while chat provides flexibility and infinite ways to interact with models.
• Conversational interfaces scale well across different levels of intelligence.

Management and Team Building

• Managers need to remain close to the work, potentially through IC rotations, to understand evolving processes and tools.
• Effective management involves providing direction and people management, creating an environment for the team to do their best work.
• "Low leverage" tasks for managers can be high leverage if they involve deep product engagement, bug reproduction, or showing care for the team.
• Psychological safety, fostered by comfort in poking fun and not fearing the leader, is key to high-performing teams, balanced with high standards.

Hiring and Key Designer Archetypes

• Key traits to look for in designers include resilience and adaptability.
• Valuable archetypes include:
  • Strong Generalists: "Block-shaped" individuals with strong core skills in multiple areas, allowing them to flex across roles.
  • Deep Specialists: Individuals with exceptional expertise in a niche area.
  • Craft New Grads: Humble, eager, and wise early-career individuals with a "blank slate" for learning new approaches.
• Aspiring designers should build actual things and showcase their work.
• Learning to use coding tools is beneficial for designers, even if not becoming full-time coders.
• AI is not yet a "hireable" designer, lacking the nuanced skills of a strong generalist, specialist, or new grad.

The Legibility Framework

• This framework assesses founders and ideas as legible or illegible.
• Illegible ideas are on the frontier, not yet fully understood, but can be valuable opportunities.
• Designers can act like VCs internally, identifying and translating illegible ideas through storytelling and UX.

AI's Role in Humanity's Survival

• AI is critical for humanity’s survival due to declining birth rates and an aging population that will require care.
• AI can help address the potential for widespread human suffering if there aren't enough people to care for the elderly.

AI as a Mega Trend and Transformation at Cisco

• AI is identified as a mega trend, a foundational movement in human history, not just a hype cycle.
• Cisco is undergoing a significant transformation to become an AI-forward company.
• Leaders should prepare for the future by fast-forwarding six months and anticipating upcoming changes.

Leadership and Team Dynamics

• A key principle is to establish enough trust within a team for open critique and debate in public.
• Stamina and persistence (hunger) are more crucial than intellect for success.

Cisco's Role in AI Infrastructure

• Cisco is a critical infrastructure company for the AI era, addressing constraints in power, compute, and network bandwidth.
• They provide networking, optics, safety, security, and observability solutions to connect GPUs and data centers.
• Cisco addresses the trust deficit in AI by ensuring safety and security, and the data gap by facilitating the use of proprietary enterprise and machine data.

Transforming Cisco into an AI-First Company

• Innovation is a choice; companies can choose to be creative and innovative regardless of size.
• Cisco committed to being AI-first, going "all in" rather than hedging, and aligning individual success with AI adoption.
• The company shifted from a conglomerate of acquisitions to a platform company with tightly integrated products that work seamlessly together.
• Cisco operates in an open ecosystem, comfortable partnering with competitors to serve customer success.

The Concept of "Permission to Play" and "Right to Win"

• Companies must have permission to play in a market and a clear route to market to achieve mass distribution.
• Focusing efforts on areas where Cisco has a natural advantage and logical entry points (like networking GPUs) yields better returns.
• Cisco avoids consumer tech because they lack the necessary distribution channels and "permission to play."

Lessons on Leadership and Communication

• Don't delegate storytelling; leaders must be the custodians of the company's message to avoid lossiness.
• Maintain the intensity of the message from top to bottom, treating employees as adults and being direct.
• Clarity of thought leads to clarity of communication; emphasize the "why" behind initiatives.
• Praise in public, criticize in private is a flawed model; directness in public and building trust in private is more effective.
• Infrastructure work doesn't always get glory but can receive blame; focus on ecosystem success and customer outcomes.

Building Great Companies: A Six-Part Framework

• The framework, in descending order of importance, includes: Timing, Market, Team, Product, Brand, and Distribution.
• Timing is paramount; a great product or team can fail if the market timing is wrong.
• A large enough market, captured in manageable chunks, is crucial.
• A well-rounded team that complements each other's weaknesses is essential.
• Product is the soul of the company, and a mediocre product is unethical.
• Brand, once lost, is very difficult to resurrect.
• Distribution is key because "if you build it, they will not come."

Navigating Trends and Future Preparedness

• Differentiate between mega trends (like AI) and hype cycles (like Web3, which was hard to understand).
• Leaders must anticipate future states (e.g., AI in 6 months) and not be biased by current assumptions or over-reliance on experience.
• Inexperience can bring fresh ideas; companies need a combination of experience and inexperience to innovate.

Key Takeaways and Advice

• Stamina trumps intellect; hunger, curiosity, and persistence are teachable/learnable, but hunger is innate.
• Business is a team sport; solving hard, important problems attracts the best talent.
• Be prepared to learn and unlearn; don't be intellectually lazy.
• The platform you choose and the quality of problems you solve determine your path.
• Don't be stingy with words; express appreciation and love explicitly.
• Be useful, as Arnold Schwarzenegger advises.
• Pay it forward and help the next person.

Claude Code's Impact and Future

• 100% of Boris Cherny's code is AI-generated, with no manual edits since November. He ships 10-30 pull requests daily.
• Productivity per engineer has increased 200% due to AI tools like Claude Code.
• The speaker predicts that coding is largely solved and in a year or two, learning to code may not be as critical.
• The future vision is a world where everyone can program and build software easily.
• Claude Code's growth is accelerating, with daily active users doubling monthly.
• The initial hackathon project, Claude Code, has transformed software engineering and is expanding to other functions.
• Claude Code is now estimated to be responsible for 4% of all GitHub commits, with predictions of reaching 20% by year-end.
• Senior engineers, including Boris, are no longer writing code manually.

The Genesis and Evolution of Claude Code

• Claude Code started as a "little hack" on the Anthropic Labs team, alongside other projects like MCP and the desktop app, following a trajectory of coding, then tool use, then computer use.
• The initial Claude Code prototype, ClaudeCLI, demonstrated the model's ability to figure out how to use tools (like a batch tool) to answer questions without explicit instructions.
• The terminal-based interface was chosen for ease of development initially, and its ability to keep up with rapid model improvements.
• Despite a slow initial external reception, Claude Code's daily active users grew rapidly once users understood its potential.
• The principle of "latent demand", where users find surprising or unintended uses for a tool, was key to Claude Code's success.
• Claude Code's success led to its integration into various platforms like iOS, Android, desktop apps, IDE extensions, Slack, and GitHub.
• User feedback has been crucial for Claude Code's continuous improvement and development.

The Shifting Landscape of Software Engineering

• Predictions from a year ago about AI writing 100% of code are now becoming reality.
• Boris predicted in May 2025 that an IDE might not be necessary by year-end, a prediction that was met with surprise but proved accurate for his personal workflow by November.
• The exponential growth of AI capabilities, a core belief at Anthropic (evidenced by co-founders' work on scaling laws), suggests continued rapid advancement.
• Innovation requires psychological safety for experimentation, with an acceptance that many ideas may not succeed.
• Boris emphasizes the importance of pulling on a thread when you feel you're onto something, even if it's not immediately obvious.
• Boris now writes 100% of his code using Claude Code and has not edited a line manually since November.
• While code is AI-generated, human review is still necessary for correctness and safety, with Claude also performing automatic code reviews.

The Next Frontier Beyond Coding

• Claude is evolving to be more proactive, analyzing feedback, bug reports, and telemetry to suggest bug fixes and new features, acting more like a "co-worker."
• Coding is considered "largely solved" for many types of programming.
• The focus is shifting to adjacent areas and general tasks that can be automated, with Claude used for tasks like paying bills and project management.
• Claude Code and Co-work are being used to analyze feedback channels like Slack threads to identify actionable insights.
• AI's ability to improve rapidly means that gains made through specific scaffolding or fine-tuning can be quickly surpassed by more general, capable models.

Productivity, Innovation, and AI at Anthropic

• Engineering productivity has seen a 200% increase with Claude Code, a gain considered "insane" compared to previous industry improvements of a few percentage points.
• The rapid pace of AI advancement has normalized unprecedented change in tech.
• Users need to adapt to newer models, as skills and approaches developed for older versions may become outdated.
• A key principle is to let AI handle tasks, as demonstrated by a newer engineer using Claude Code to debug a memory leak more effectively than Boris.
• The advice to "underfund things a little bit" at the start encourages teams to rely on AI and find efficient solutions.
• Encouraging speed and allowing individuals to ship quickly is paramount, with AI as a tool to achieve this.
• When building AI products, it's recommended to give engineers unlimited tokens for experimentation, optimizing for cost later.
• Some engineers are spending hundreds of thousands of dollars a month on tokens, indicating significant AI usage.

The Changing Nature of Programming and AI Adoption

• Programming has historically evolved from hardware to software, and now to AI-driven generation.
• Boris doesn't worry about his own skills atrophying, viewing programming as a continuum of evolving tools.
• The historical analogy of the printing press is used to describe the democratizing and transformative potential of AI in programming.
• The shift is from writing code to describing desired outcomes to AI.
• Boris views programming as a practical tool for building things, not an end in itself, though acknowledges some enjoy the art of coding.
• AI is expected to impact roles adjacent to engineering, such as product management, design, and data science, and eventually any computer-based work.
• The term "agent" refers to an AI that can use tools and act in the world, not just converse.
• Concerns about AI's impact on jobs are acknowledged, but the focus is on increased enjoyment and productivity for many.

Building and Using AI Products

• Key advice for building AI products includes not boxing in the model, providing tools and goals, and letting the AI figure out the execution.
• The "bitter lesson" suggests betting on more general models over highly specific or fine-tuned ones, as general models tend to outperform in the long run.
• Building for the model six months in the future, rather than the current model, is a strategy for long-term product success.
• Assumptions for future models include improved tool use, longer execution times, and greater autonomy.
• For using Claude Code: use the most capable model (Opus 4.6) with "maximum effort" enabled, as it can be more token-efficient.
• "Plan mode", which prevents immediate code generation and allows for interactive planning, is highly recommended.
• Experimenting with different interfaces (terminal, desktop app, mobile, Slack) is encouraged.
• Competition in the coding agent space is seen as beneficial for driving innovation.
• Anthropic's approach prioritizes user feedback and building a good product over closely monitoring competitors.

Safety, Research, and the Future of AI

• Anthropic's work involves studying AI safety at three levels: alignment/mechanistic interpretability (internal model workings), evals (laboratory settings), and real-world behavior.
• Mechanistic interpretability aims to understand the specific functions of neurons within AI models.
• Early release of products like Claude Code is partly for studying their real-world safety and behavior.
• Anthropic open-sources research and tools (like the Claude Code sandbox) to promote safe AI development across the industry ("race to the top").
• Anxiety about agents not working is acknowledged, but Boris mitigates this by running multiple agents concurrently.
• The speaker is from Odessa, Ukraine, and shares a personal connection with the interviewer, also born in Odessa.
• Boris's future plans post-AGI include making miso, a long-term, patient process that contrasts with rapid AI development.
• The core belief at Anthropic is that AI development progresses through coding, tool use, and computer use, which is key to understanding safety.
• Despite rapid growth, AI adoption is still considered early (1% done).