Get your free personalized podcast brief

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

Instead of assigning designers to narrow features (e.g., "code review"), teams are structured around broader personas (e.g., "developer"). This ensures designers consider the entire user lifecycle and avoid optimizing for a specific metric at the expense of the overall experience.

Related Insights

High-performing teams are creating small 'pods' with a product manager (business context), a designer (UI/UX), and an engineer (technical execution) who work together in shared AI coding sessions. This collaborative model ensures features are viable, usable, and well-built from the start, breaking down traditional silos.

AI will make the traditional "product pod" structure obsolete for design. Designers, empowered to learn contexts faster and cover more ground, will operate in a more fluid, centralized team. They will be deployed across entire user journeys that span multiple teams, rather than being calcified within a single product area.

AI tools are dissolving the traditional boundaries between product, design, and engineering. This shift makes functional silos archaic. The future of organizational design is smaller, cross-functional groups that own a customer problem end-to-end, rather than being grouped by capability like "the engineering team."

Instead of siloing roles, encourage engineers to design and designers to code. This cross-functional approach breaks down artificial barriers and helps the entire team think more holistically about the end-to-end user experience, as a real user does not see these internal divisions.

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.

AI is democratizing development and design, erasing the distinct boundaries between product, design, and engineering. This trend favors a return to a more generalist "problem solver" or "builder" archetype, where team members contribute across traditional functional lines to ship products faster.

To avoid teams getting stuck in local optimizations, Suno expects product managers and designers to spend 80% of their time on their core focus and 20% on broader ideas. This structure fosters shared context and prevents rigid divisions, enabling bigger, long-term breakthroughs.

Leveraging frameworks like Human Design transforms team collaboration. By understanding archetypes (e.g., a fast-executing Manifesting Generator vs. a guiding Projector), team members can anticipate and accommodate different work styles, turning potential points of friction into a complementary partnership.

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.

In fluid, AI-powered teams, job descriptions are obsolete. A person's role is defined by the center of gravity of their contributions鈥攚hether they skew towards code, product specs, or design. This allows for more overlap and agency, moving away from rigid "lanes."