To create an integrated product suite, Cisco dismantled divisional silos and restructured into a platform-based organization. An org chart directly dictates product architecture, so leaders must design their organization to produce the desired integrated outcome, not just individual products.

A new operating model separates long-term product maintenance (handled by Product Owners) from initial development. For new features, a temporary "swarming" team of Program Managers (strategy) and Product Ops (execution/tools) is assembled, creating a flexible, expert-driven approach to innovation.

Meta is shifting from 12-person specialist teams to 6-7 person "pods." These are led by a "Product Staff"—a PM generalist who also handles design and data tasks—supported by generalist engineers. This structure increases speed by reducing coordination overhead.

The V0 team operates with minimal product management oversight, empowering product-minded engineers (often ex-founders) to make 95% of product decisions directly. This sacrifices potentially "perfect" choices for a dramatic increase in development velocity.

PostHog manages its 16+ product suite by assigning small, autonomous teams of roughly three engineers to each product. This "compound startup" approach allows them to go wide, competing with multiple point solutions while remaining flat and avoiding bureaucracy. The small team structure fosters ownership and rapid development.

To combat slow decision-making from having too many stakeholders, Robinhood reorganized from functional departments to business units led by General Managers. This structure puts product, engineering, compliance, and operations on the same team, streamlining ownership and accelerating progress.

Rippling structures teams into business units led by GMs who oversee product, sales, and implementation. This is driven by the belief that a unified team focused on a specific customer problem (e.g., IT) delivers a superior end-to-end experience compared to a traditional matrixed organization.

In a multi-product company, horizontal teams naturally prioritize mature, high-impact businesses. Structuring teams vertically with P&L ownership for each product, even nascent ones, ensures dedicated focus and accountability, preventing smaller initiatives from being starved of resources.

Having product, engineering, design, and data under a single CPTO allows for rapid decision-making. When an experiment reveals a promising new direction, the leadership team can pivot resources across different squads and tribes within days, a process that would take weeks or months in a siloed structure.