Heidi Helfand on Dynamic Reteaming, the Five Patterns of Team Change, and Transparency in Reorgs
Source: Lenny’s Podcast Speaker: Heidi Helfand Link: Episode
Overview
Heidi Helfand is the author of Dynamic Reteaming: The Art and Wisdom of Changing Teams and a consultant and workshop facilitator on org change. After twenty years in SaaS startups (15th employee at Expertcity/GoToMyPC; 10th at AppFolio), she became fascinated with the patterns of team change that happen regardless of whether organisations plan for them. The episode covers her five-pattern taxonomy of reteaming, the anti-patterns that make change painful, how to run transparent whiteboard-based reorgs, what makes isolation teams succeed or fail, and how switching builds knowledge redundancy before a crisis forces it.
Key ideas
- Five patterns of reteaming. Heidi identifies five patterns covering all team change: one by one (people joining or leaving the company), grow and split (a growth pattern — teams outgrow coordination capacity and divide, signalled by longer meetings, divergent work, and standups where people disengage), merging (the shrinking pattern — teams or companies consolidate), isolation / innovation by isolation (a beneficial silo with process freedom for new products or emergencies), and switching (lateral movement between teams for learning, fulfilment, and knowledge redundancy). “Reorg” is a separate, more loaded term — it implies top-down, involuntary, large-scale change; reteaming covers all five at every level.
- Isolation pattern success factors. The Expertcity/GoToMyPC pivot is the canonical example: a failing marketplace was killed and a small isolated team given process freedom to build GoToMyPC — it saved the company. Success requirements: (1) separate location or claimed workspace region; (2) a senior leader explicitly tells others not to disturb; (3) knowledge redundancy built first through pairing so the isolated person can fade out safely; (4) process freedom — no imposed sprint cadence; (5) reporting to a senior decision-maker with real authority whose decisions do not get reversed; (6) relief from heavyweight bureaucracy. Historical precedent: the Chicken McNugget was saved by an isolated team at McDonald’s working in a separate plant, reporting to a senior executive.
- Whiteboard reteaming. Surface proposed team structures — names, missions, and open hiring slots — on whiteboards to the whole affected team before finalising. People identify design mistakes, spot internal opportunities, and gain a sense of agency. Inspired by Christian Lima at Spotify; replicated at Procore with ~80 people. Must be time-boxed, biasing shorter. The spectrum runs from closed back-room planning (fastest, least buy-in) through whiteboard reteaming (mid-spectrum) to Redgate Software’s open self-selection events (team pitches, people choose their team).
- Anti-patterns. Three concrete failure modes: the percentage anti-pattern (fractional resource allocation across concurrent efforts — percentages do not add up under context-switching costs); “poof, they’re gone” (changes made without communication, leaving the team without the neutral zone transition they need); spreading high performers (Jon Walker’s AppFolio experiment — splitting a high-performing team to distribute chemistry across other teams did not work; team chemistry is emergent, not portable).
- RIDE and Transitions. Pat Wadors’ RIDE framework (Request, Input, Decider, Execute) gives decision clarity in reorgs — knowing who the Decider is prevents ambiguity and frustration, especially in changes where employees have no input (acquisitions). William Bridges’ Endings → Neutral Zone → New Beginning maps the emotional arc of any change; naming the neutral zone as expected and temporary makes subsequent changes easier to navigate.
Related
- Dynamic Reteaming — concept page for the five-pattern framework
- Hari Srinivasan on LinkedIn, Skills-First Hiring, and Managing Ecosystem Complexity — parallel on RAPID vs RIDE decision frameworks for managing complex org decisions at scale
- Claire Hughes Johnson on Scaling People and the Company Operating System — complementary on codifying people operations as a company scales
- Camille Fournier on PM-Engineering Dynamics, Rewrites, and Platform Engineering — parallel on engineering org design and managing teams through growth