Learning Brief — 2026-07-02

What we covered

• AI news: AI Developments: New Tools and Custom Chips Shape Future Products
• PM news: Kent Beck on Building Trust in Software Engineering
• PM learning: The Cognitive Biases That Shape Product Decisions

Mental model

Challenge your assumptions regularly to avoid cognitive biases that can misguide product decisions.

Summary

Anthropic's Fable 5 has set a new record for automating freelance work, showcasing its enhanced capabilities in task automation. This model is being highlighted for its performance, though experts caution it still can't fully replace human workers. Meta has launched Pocket, an experimental AI app that allows users to create and share interactive mini games through text prompts. This marks a significant step in user-generated content, leveraging AI to enhance creativity in gaming. Anthropic is in discussions with Samsung to develop a new custom AI chip, following OpenAI's recent partnership with Broadcom for a similar initiative. This move indicates a growing trend toward tailored hardware solutions that can better support AI applications.

In a recent reflection, Kent Beck, a pioneer in the Agile movement, shared his insights on the evolving landscape of software engineering, especially as we transition into an AI-driven era. He emphasized that while coding skills remain crucial, the future will increasingly hinge on building trust among teams and stakeholders. Beck pointed out that successful product development isn’t just about delivering features; it’s about creating a collaborative environment where team members feel empowered to innovate and address challenges. This trust-building is particularly vital when integrating AI into products, as it often requires a shift in mindset for teams accustomed to traditional development practices. For product managers, this insight reinforces the importance of fostering a culture of openness and collaboration. As you lead your teams, consider how you can create spaces for honest dialogue and experimentation. Encourage your engineers to share their thoughts and feedback on AI integrations without fear of judgment. This approach can lead to more innovative solutions and a more engaged team. Remember, as Beck suggests, the real value lies not just in generating code but in nurturing relationships that drive product success. This matters to you as a PM because in today's competitive landscape, the ability to build trust and foster collaboration can set your product apart and lead to more successful outcomes in your projects.

Here’s the thing: as product managers, we often fall prey to cognitive biases that can warp our decision-making. Shreyas Doshi lays out four key beliefs that underpin a fundamental cognitive bias for product builders, and understanding these can help us navigate our roles more effectively. The insight here is that our biases can blind us to the needs of our users and the realities of our market. What that means in practice is that if we’re not aware of these biases, we risk building products that don’t truly resonate or solve the right problems.

The move here is to actively challenge our assumptions. Think about it like this: imagine you’re cooking a new dish. If you just follow the recipe blindly without tasting as you go, you might end up with a meal that doesn’t appeal to anyone—too salty, too bland, or just not what your guests expected. Similarly, in product management, if you don’t question your biases, you’re cooking without tasting.

For example, one of the biases Doshi highlights is the "sunk cost fallacy"—the tendency to continue investing in a project because of the resources already spent, rather than its current viability. This can lead to sticking with a failing product simply because you’ve put so much into it. The key here is to develop a habit of regularly revisiting your product decisions with fresh eyes and real data. This might mean setting aside time each week to review your metrics, gather user feedback, and question whether your product is still aligned with user needs.

This approach connects to strategic decision-making as well. By acknowledging and addressing your cognitive biases, you are more likely to make informed, unbiased decisions that lead to better product outcomes. So, what’s one specific action you can take this week? Start a bias-checking exercise in your next product meeting. Encourage your team to voice assumptions and challenge them with data and user insights. This practice not only helps in making better decisions but also fosters a culture of openness and continuous improvement.

Remember, the best products are built on a foundation of understanding, not assumptions.