We scan new podcasts and send you the top 5 insights daily.
In Anthropic's small (3-5 person) AI pods, traditional roles are fluid. A team member's title merely indicates a specialty, not a boundary. Designers push code to production and engineers contribute to design, fostering a shared responsibility that accelerates development.
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.
The traditional handoff model is obsolete. AI-powered tools create a fluid environment where designers work in code for final polish and engineers iterate directly in design tools. This fosters a new, more integrated "builder" role, breaking down historical silos between disciplines.
The most effective team structure for new AI products involves a "co-founder" pairing. One person is a designer who can also build and rapidly prototype ideas. The other is a traditional software engineer who follows behind, ensuring the underlying architecture is robust and scalable, effectively "paving the trail."
AI's productivity gains mean that on a lean, early-stage team, there is little room for purely specialized roles. According to founder Drew Wilson, every team member, including designers, must be able to contribute directly to the codebase. The traditional "design artifact" workflow is too slow.
As AI handles coding, traditional tech roles will merge. At Anthropic, PMs, designers, and engineers all code. The future is a generalist "Builder" who can handle multiple disciplines, making role specialization obsolete.
The traditional tech team structure of separate product, engineering, and design roles is becoming obsolete. AI startups favor small teams of 'polymaths'—T-shaped builders who can contribute across disciplines. This shift values broad, hands-on capability over deep specialization for most early-stage roles.
With AI coding assistants, the barriers to shipping software are eroding. At Ramp, designers and customer support agents are now shipping code to production. This suggests a future where the traditional, siloed Engineering, Product, and Design (EPD) team structure becomes obsolete.
AI development makes identifying the right use case and wrangling data the new bottlenecks, not coding. This flattens traditional hierarchies. The most effective teams are integrated 'tiger teams' where UX designers manage RAG files and developers talk to customers, valuing adaptability over rigid job descriptions.
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.