We scan new podcasts and send you the top 5 insights daily.
John Deere replaced its traditional matrix org chart with teams dedicated to specific crop 'production systems,' like a 'corn team' or 'soybean team.' This structure forces employees to focus exclusively on a single customer's entire workflow, fostering deep domain expertise and creating a competitive moat.
As its product suite and customer base grew, Plaid’s org structure evolved from generalists, to segments by company size, to industry verticals, and finally to a matrix of vertical-focused 'quarterbacks' supported by horizontal product specialist teams.
To accelerate decision-making, John Deere 'delayered' its corporate structure from 11 to 7 levels. This change was inspired by the lean, two-layer structure of an AI company they acquired. It is a deliberate strategy to reduce bureaucracy and enable a 190-year-old industrial firm to operate at a faster pace.
Instead of focusing on building the 'best planter,' John Deere's strategy targets farmers' biggest pain points, like seed cost. By using technology to deliver quantifiable financial value (e.g., better crop placement), they make their customers more profitable, moving from a product-centric to an outcome-centric model.
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.
Counter to typical scaling patterns, Square reverted from a business-unit model back to a functional one. They believed the General Manager structure diluted deep domain expertise, and a functional organization better preserves the "craft and excellence" within disciplines like product and engineering.
Chamath models his company's structure on a circuit board, not an org chart. Each department is a "chip" (e.g., Marketing) with explicit inputs (money, content) and outputs (leads). This "system on a chip" model forces functional clarity and minimizes hierarchy-driven politics.
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.
Adobe moved away from channel-based silos and redesigned its marketing organization around specific customer groups. These core teams are supported horizontally by centers of excellence, creating a "teams of teams" structure that maps directly to the company's technology stack and ensures customer-centricity.
Unlike the common model of a separate, consultant-heavy value creation team, Premira integrates specialists like ex-operators directly into its sector teams. This ensures deep industry expertise is applied to drive top-line growth, not just cost-cutting.
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.