Get your free personalized podcast brief

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

To iterate faster, Lightfield's 40-person team operates without functional swim lanes. At a daily stand-up, anyone free takes the highest priority task, regardless of role. This generalist culture, enabled by shared context from AI tools, is key to their speed.

Related Insights

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.

AI collapses development cycles, making the linear waterfall process obsolete. The new model is a 'jazz band,' where product, design, and engineering specialists collaborate dynamically, riffing off each other's work without a fixed leader or rigid sequence.

At OpenAI, teams of just one or two engineers leverage AI agents to own entire product lines. This model reduces human collaboration overhead and empowers engineers to make most micro-decisions autonomously, increasing speed and ownership.

AI tools allow traditional product team roles to overlap. Product managers can prototype and deploy code, while engineers can independently handle UI tasks. This fosters smaller, faster, and more ambitious teams where individuals have broader capabilities and fewer dependencies.

Meta is shifting from 12-person specialist teams to 6-7 person "pods." These are led by a "Product Staff"—a PM generalist who also handles design and data tasks—supported by generalist engineers. This structure increases speed by reducing coordination overhead.

To adapt to AI-driven workflows, Microsoft's LinkedIn combined product managers, designers, and engineers into a single "full stack builder" role. This structural change eliminates communication bottlenecks and empowers individuals to leverage AI tools for end-to-end product development, drastically increasing speed.

To adapt to AI-driven productivity, Block abandoned large, static feature teams for small squads of 1-6 people that can flexibly move between products. This structure, combined with cutting management layers by over 50%, allows for faster information flow and rapid, AI-powered development cycles.

In an AI-driven world, product teams should operate like a busy shipyard: seemingly chaotic but underpinned by high skill and careful communication. This cross-functional pod (PM, Eng, Design, Research, Data, Marketing) collaborates constantly, breaking down traditional processes like standups.

At the AI-native company Cursor, roles are "really muddy." Team members contribute based on individual strengths—like visual design or systems architecture—and use AI agents to bridge skill gaps and tie work together. This creates a more fluid and efficient team structure.

The traditional "assembly line" model of product development (PM -> Design -> Eng) fails with AI. Instead, teams must operate like a "jazz band," where roles are fluid, members "riff" off each other's work, and territorialism is a failure mode. PMs might code and designers might write specs.