By embedding product teams directly within the research organization, Google creates a tight feedback loop. Instead of receiving models "over the wall," product and research teams co-develop them, aligning technical capabilities with customer needs from the start.
The traditional, linear handoff from product (PRDs) to design to dev is too slow for AI's rapid iteration cycles. Leading companies merge these roles into smaller, senior teams where design and product deliver functional prototypes directly to engineering, collapsing the feedback loop and accelerating development.
Google is moving beyond AI as a mere analysis tool. The concept of an 'AI co-scientist' envisions AI as an active partner that helps sift through information, generate novel hypotheses, and outline ways to test them. This reframes the human-AI collaboration to fundamentally accelerate the scientific method itself.
Instead of a linear handoff, Google fosters a continuous loop where real-world problems inspire research, which is then applied to products. This application, in turn, generates the next set of research questions, creating a self-reinforcing cycle that accelerates breakthroughs.
The traditional PM function, which builds sequential, multi-month roadmaps based on customer feedback, is ill-suited for AI. With core capabilities evolving weekly, AI companies must embed research teams directly with customer-facing teams to stay agile, rendering the classic PM role ineffective.
To avoid choosing between deep research and product development, ElevenLabs organizes teams into problem-focused "labs." Each lab, a mix of researchers, engineers, and operators, tackles a specific problem (e.g., voice or agents), sequencing deep research first before building a product layer on top. This structure allows for both foundational breakthroughs and market-facing execution.
Siphoning off cutting-edge work to a separate 'labs' group demotivates core teams and disconnects innovation from those who own the customer. Instead, foster 'innovating teams' by making innovation the responsibility of the core product teams themselves.
Stripe's Experimental Projects Team discovered that embedding its members directly within existing product and infrastructure teams leads to higher success rates. These "embedded projects" are more likely to reach escape velocity and be successfully adopted by the business, contrasting with the common model of an isolated R&D or innovation lab.
Large labs often suffer from organizational friction between product and research. A small, focused startup like Cursor can co-design its product and model in a tight loop, enabling rapid innovations like near-real-time policy updates that are organizationally difficult for incumbents.
While a tight product-research link is beneficial, it creates a management challenge where teams get so excited about implementation they neglect the next big research question. The research leader's role includes making the difficult judgment call to shift focus back toward long-term discovery, even amid product success.
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.