We scan new podcasts and send you the top 5 insights daily.
Unlike function-specific associations (e.g., for engineers), the Product Development and Management Association (PDMA) was created in 1976 to unite people across all roles and industries who are involved in the process of innovation. This cross-functional philosophy remains its core strength.
P&G institutionalized cross-functional learning through 'communities of practice.' These informal, topic-based gatherings, like lunchtime talks, expose employees to diverse projects and thought leaders, fostering collaboration and sparking new ideas that might not emerge from formal project work.
Product development has evolved beyond its traditional core of engineering and product management. Creating great products today requires a collaborative fusion of four disciplines from the start: engineering, product, design, and data science. The elevation of design and data science to core partners is a critical shift.
The core job of a Product Manager is not writing specs or talking to press; it's a leadership role. Success means getting a product to market that wins. This requires influencing engineering, marketing, and sales without any formal authority, making it the ultimate training ground for real leadership.
If a company creates a siloed "innovation team," it's a sign the main product organization is stuck in "business as usual" maintenance. Innovation should be a mindset embedded across all teams, not an isolated function delegated to a select few.
Job titles like "Product Manager" are less important than ensuring key accountabilities are met. A successful product engine needs someone who prioritizes outcomes, someone who investigates the problem space, and someone who prevents cross-team collisions. Assign these roles regardless of titles.
The common product development process is a sequential handoff model. A better approach is a "jazz band" model where cross-functional teams collaborate harmoniously from the start. This fosters creativity and reduces rework by including engineers in early ideation, rather than treating them as a final step.
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.
The best products are built when engineering, product, and design have overlapping responsibilities. This intentional blurring of roles and 'stepping on each other's toes in a good way' fosters holistic product thinking and avoids the fragmented execution common in siloed organizations.
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.
A truly product-driven culture involves everyone, not just designers and product managers. At Amo and Zenly, a deep connection between all teams was crucial, with many innovative product ideas originating from unexpected places like the backend engineering team, who were deeply involved in shaping the user experience.