The definition of "cross-functional" is shifting from coordinating between departments to embodying multiple skills. To increase speed, modern PMs must directly perform tasks in design, user research, and even coding, rather than acting as a 'glorified cross-functional secretary.'

Related Insights

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.

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.

Figma's data shows nearly two-thirds of its users identify with two or more roles (e.g., design, product, engineering). This suggests a shift away from rigid professional lanes. People increasingly see themselves as generalist "product builders," requiring tools that facilitate cross-functional collaboration rather than catering to a single title.

The 'CEO of the product' metaphor is misleading because product managers lack direct authority. A better analogy is 'the glue.' The PM's role is to connect different functions—engineering, sales, marketing—with strategy, data, and user problems to ensure the team works cohesively towards a shared goal.

In an organization still running in project mode, the 'Product Manager' title is misleading. The role is often relegated to organizing work and scheduling tasks for engineering. A true product model requires empowering these roles with the mandate, skills, and market access to make strategic decisions.

To maximize speed, V0 operates with a "no handoffs" philosophy. Everyone, including designers and product managers, is expected to contribute code and submit their own pull requests. This "full-stack PM" model minimizes the coordination costs and wasted cycles of explaining changes.

Contrary to the popular belief that it's always detrimental, for product managers, context switching is a core strength. Fluidly moving between customer, engineering, and marketing conversations is essential for integrating diverse perspectives to bring a product to life.

AI tools are collapsing the traditional moats around design, engineering, and product. As PMs and engineers gain design capabilities, designers must reciprocate by learning to code and, more importantly, taking on strategic business responsibilities to maintain their value and influence.

AI's rise means traditional product roles are merging. Instead of identifying as a PM or designer, focus on your core skills (e.g., visual aesthetics, systems thinking) and use AI to fill gaps. This 'builder' mindset, focused on creating end-to-end, is key for future relevance.

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.