To accelerate AI adoption, Block intentionally dismantled its siloed General Manager (GM) structure, which had given autonomy to units like Cash App. They centralized into a functional organization to drive engineering excellence, unify policies, and create a strong foundation for a company-wide AI transformation.

Block's CTO reveals a counterintuitive lesson: reorganizing from a GM-based structure to a functional one (where all engineers report to one org) was the key to their AI transformation. This structural change had a greater productivity impact than any specific AI tool they implemented.

Platform teams risk building generic solutions that don't truly solve anyone's problem. Square avoids this by having its platform organization also own and be responsible for specific product surfaces. This structure forces them to stay close to customer outcomes and build practical tools.

To maintain agility and deep expertise at scale, Andreessen Horowitz restructured into independent, specialized teams for sectors like bio, crypto, and AI. Each sub-team operates like the original firm, preventing large, unproductive group decisions and enabling focused expertise.

Recoiling from Flipkart's complex leveling system (which spawned an "SD 2.5" role), PhonePe's CTO implemented a flat hierarchy with minimal titles. This structure aims to focus engineers on impact and capability growth, rather than chasing promotions and labels.

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.

Block restructured from divisional GMs to a functional organization (Engineering, Product, Design) across all brands. This creates a single shared roadmap and forces alignment, enabling cross-unit collaboration that was difficult when incentives were siloed in separate P&Ls.

The idea that you need a massive framework to scale agility is a lie. Agility doesn't scale; bureaucracy does. To increase speed and responsiveness, you must relentlessly de-scale the organization by breaking down silos into smaller, cross-functional, autonomous units.