How to Reorg After AI Changes Everything | Block's Owen Jennings on the a16z Show

· Source: a16z · Field: Technology & Digital — Artificial Intelligence & Machine Learning, Software Development & Engineering, Corporate Strategy & Leadership · Depth: Intermediate, long

Summary

Owen Jennings, Business Lead at Block, discusses the company's recent 40% workforce reduction, attributing it primarily to a "binary change" in AI capabilities around late November/early December, specifically with models like Opus 46 and Codex 53. These models dramatically increased productivity, enabling one or two engineers to achieve 10-100x more output, particularly with complex existing codebases. Block had already been developing internal agentic tools like Goose since early 2024. The company restructured from a hierarchical, functional model to small, flexible squads of 1-6 people, significantly reducing management layers. Internally, tools like Builderbot autonomously merge PRs and build features up to 85-100%. Block also uses AI for deterministic workflows in customer support, product operations, and risk operations. Externally, AI drives generative UIs for products like Moneybot and ManagerBot, creating personalized and dynamic user experiences.

Key takeaway

For CTOs and VP of Engineering evaluating AI integration, Block's experience demonstrates that a "big bang" organizational restructuring, rather than incremental cuts, can be necessary to fully capitalize on AI's productivity gains. Your teams should focus on building internal agentic platforms and tools, and prepare for a shift from linear workflows to managing multiple AI agents, which will fundamentally alter product development and team composition.

Key insights

Advanced AI models fundamentally alter software development and organizational structures, enabling massive productivity gains.

Principles

Method

Block implemented a "big bang" 40% RIF, driven by AI productivity, focusing cuts on development. They rebuilt the org around small, flexible squads and agentic workflows, prioritizing reliability, compliance, and durable growth.

In practice

Topics

Best for: CTO, VP of Engineering/Data, Director of AI/ML

Related on AIssential

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by a16z.