Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

To move quickly without sacrificing craft, organizations should assemble lean pods featuring one senior strategic lead and a small bench of individual contributors. Removing intermediate management layers preserves context and unblocks teams to ship with speed.

Related Insights

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.

Snap's former product chief advocates for teams with a powerful shared mission ("ideological culture") and a clear hierarchy for decision-making. This structure minimizes collaboration overhead and empowers autonomous, high-speed execution by creating trust and alignment.

AI tools dramatically reduce the resources needed for idea validation. Leaders should restructure teams by creating small, nimble 'discovery' pods (1-2 people) for rapid idea generation and validation. Successful ideas are then passed to larger, traditional 'execution' teams for scaling and implementation.

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.

To adapt to AI-driven productivity, Block abandoned large, static feature teams for small squads of 1-6 people that can flexibly move between products. This structure, combined with cutting management layers by over 50%, allows for faster information flow and rapid, AI-powered development cycles.

The true purpose of a flat organization is to enable rapid information flow and collaboration, preventing data silos. It allows any junior engineer to directly communicate with senior leadership, accelerating decision-making and problem-solving across the company without having to funnel information through managers.

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.

To avoid bureaucratic bloat, organize the company into small, self-sufficient "pods" of no more than 10 people. Each pod owns a specific problem and includes all necessary roles. Performance is judged solely on the pod's impact, mimicking an early-stage startup's focus.

To maintain speed in a large organization, ignore the formal org chart. Instead, structure work around small, empowered 'work chart' teams (squads). Give them a clear DRI, full context, agency, and a direct 24-hour escalation path to leadership to remove blockers.

To achieve massive output with a small team (~127 people), Kalshi relies on a few core principles. The founders set a relentless work pace, maintain a flat organization with many direct reports, and dynamically assign talent to the company's biggest problems rather than adhering to a rigid org chart.