We scan new podcasts and send you the top 5 insights daily.
IBM's core product leadership team consists of design, product management, and engineering. Success in this model requires breaking down traditional silos. The lines blur to the point where designers are expected to understand the product technically well enough to explain it during a client user interview, fostering a deeper, shared understanding and trust across functions.
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.
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 historical separation between product management, design, and engineering is dissolving. AI assistants handle the coding, allowing a single person to define the product (PM), ensure high-quality aesthetics and UX (designer), and direct the technical implementation (engineer), thus converging the three roles.
The traditional product team structure is evolving as roles blend. Product managers might write requirements that directly generate code, and design will become more central. The focus will shift to a unified 'builder' identity that values cross-functional craft and agility over rigid role definitions.
While AI tools create more overlap between product, design, and engineering, the core responsibilities will remain distinct in larger organizations. It's difficult to find one person who excels at rallying teams, crafting user experiences, and ensuring technical soundness, so specialized roles will persist.
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.
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.
Product management at IBM transformed from a rigid, process-driven function focused on moving tasks between steps into a market-facing discipline. By adopting a "design thinking" framework centered on client outcomes, the goal shifted from process completion to creating a "wow" factor and genuinely delighting customers.
The convergence of product, engineering, and design roles into a unified "builder" identity is a massive opportunity. This shift fosters deeper collaboration and empowers teams to move faster and more cohesively across the entire product lifecycle, treating everyone as a builder.
Wealthsimple's VP of Design found that prioritizing relationships with product and engineering leaders was more impactful than focusing solely on her design reports. This cross-functional 'first team' prevents silos and enables outsized collective impact.