Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To prevent over-indexing on internal user needs, Anthropic tests new products internally while concurrently offering them to external customers in early access. This dual-feedback approach ensures the platform remains broadly applicable and avoids becoming a niche internal tool.

Related Insights

Anthropic validates products internally before any external release. A feature is only considered ready for public launch once it achieves a critical mass of daily active users within the company. This rigorous dogfooding process ensures the tool provides real workflow value, moving beyond simple feedback to proven adoption.

To handle the "fire hose" of user feedback, Anthropic's PMs use Claude itself. The AI clusters feedback, identifies top themes, and even generates synthetic data based on user problems. This dogfooding creates a powerful feedback loop, turning qualitative data into actionable insights for model improvement.

Vercel's validation framework starts with "Customer Zero"—themselves, relying on internal taste and needs. They then move to "Customer One," a select group of close design partners for external pressure testing before a wider release. This balances internal conviction with external feedback.

Salesforce operates under a 'Customer Zero' philosophy, requiring its own global operations to run on new software before public release. This internal 'dogfooding' forces them to solve real-world enterprise challenges, ensuring their AI and data products are robust, scalable, and effective before reaching customers.

By creating a distinct, less-polished tab for Cowork, Anthropic sets user expectations that it's an evolving feature. This strategy allows them to ship daily, gather feedback on a "bleeding edge" product, and avoid disrupting the core, stable chat experience.

For core product changes, Granola eschews quantitative A/B testing in favor of qualitative gut feel from intensive internal use. By building prototypes and having the entire team use them in their own chaotic workdays, decisions are made based on collective intuition about what *feels* better.

Instead of prioritizing a problem and then designing a solution, leading companies build prototypes for multiple problems simultaneously. They then productionize the problem-solution pair that proves most effective through internal testing, a concept called "product shaping."

Anthropic relies heavily on internal users for early feedback, finding them more honest and focused on crucial interaction design details. This "bleeding edge" internal signal on UI polish is often more valuable than external feedback on broader user flows.

Anthropic has flipped the traditional development process. Instead of debating quality at the mock or discussion stage, they push teams to build a working version first. Quality decisions are then made based on hands-on usage of the live product, which provides much richer and more accurate feedback.

The rapid evolution of AI makes traditional product development cycles too slow. GitHub's CPO advises that every AI feature is a search for product-market fit. The best strategy is to find five customers with a shared problem and build openly with them, iterating daily rather than building in isolation for weeks.

Anthropic Avoids Bias by Dogfooding New Features Alongside External Customer Previews | RiffOn