Jan 18, 2024 · 1h 10m · lennys-podcast
The art and wisdom of changing teams | Heidi Helfand (Author of Dynamic Reteaming)
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
Organizational consultant Heidi Helfand joins Lenny Rachitsky to unpack 'Dynamic Reteaming,' sharing practical frameworks, five core reteaming patterns, and participatory leadership techniques that turn disruptive reorganizations into deliberate opportunities for team resilience and career growth.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. Lenny holds 20.3% of the talking time here. How this is scored →
Lenny as informed peer 3.7 Guest teaching 5.4 Guest disagreement 0.8 Lenny pushing back 0.8
speaking balance: gold is Lenny, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 58:15 Challenging the assumption that all change is good
Heidi gently pushes back on the absolute premise shared by Sheryl Sandberg that organizational churn and constant change are universally positive.
Hardest push from Lenny ▶ 11:56 Host challenges transparency as potential chaosLenny pushes back against open reorg planning, arguing that involving employees directly risks creating massive distraction, panic, and consensus gridlock.
Biggest teaching moment ▶ 13:00 Educating on the RIDE decision frameworkHeidi educates Lenny on structured change management, breaking down the RIDE framework (Request, Input, Decide, Execute) to resolve ambiguity around transparent reteaming.
Lenny holds their own ▶ 47:02 Framing org design as continuous problem tradingLenny brings strong domain expertise by summarizing that org design is never about perfection, but rather choosing which set of problems you are willing to trade for.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Lenny as informed peer | Guest teaching | Guest disagreement | Lenny pushing back | Why |
|---|---|---|---|---|---|---|
| Embracing Team Change and the Human Dimension | 4 | 4 | 1 | 1 | Lenny opens by asking Heidi why she chose to study dynamic reteaming, sharing an anecdote from Airbnb. Heidi explains her career path and contrasts conventional management dogma about static teams with real-world startup evolutions. | |
| Promoting Transparency and Whiteboard Reteaming | 3 | 6 | 1 | 1 | Lenny asks how employees can leverage reorgs for career advancement. Heidi redirects the conversation toward organizational transparency and details case studies of whiteboard reteaming and self-selection. | |
| Transition Models and the RIDE Framework | 5 | 7 | 1 | 4 | Lenny pushes back from an executive viewpoint, questioning if transparency leads to decision paralysis and widespread panic. Heidi counters with structured transition models like William Bridges' framework and Pat Waters' RIDE model. | |
| Overview of the Five Reteaming Patterns | 4 | 6 | 1 | 1 | Lenny asks for a breakdown of the core five reteaming patterns and clarifies the difference between a reorg and reteaming. Heidi succinctly lays out the patterns and debunks the negative corporate connotation of reorgs. | |
| Case Study on Isolation: The Genesis of GoToMyPC | 3 | 7 | 1 | 0 | Lenny invites Heidi to share the origin story of GoToMyPC. Heidi narrates the emotional and structural journey of moving to an isolated team to save Expert City from failure. | |
| Best Practices for High-Impact Isolated Teams | 4 | 6 | 1 | 1 | Lenny asks how to make internal skunkworks teams succeed when they so often fail in larger companies. Heidi delivers concrete best practices, including executive sponsorship, process freedom, and pair switching for fault tolerance. | |
| Sponsor Message: Ahrefs Webmaster Tools | 3 | 5 | 1 | 1 | After the sponsor break, Lenny clarifies a point of confusion regarding the one-by-one pattern. Heidi clarifies the distinction between onboarding individuals and switching team members across units. | |
| Navigating Grow and Split: Signals and Trade-offs | 3 | 6 | 0 | 0 | Heidi explains the operational indicators that signal a team should grow and split, as well as the mechanics of team merging and historical onboarding exercises. | |
| The Switching Pattern and Knowledge Redundancy | 3 | 6 | 1 | 0 | Heidi details the switching pattern and how pairing rotations eliminate single points of failure in technical architecture. She highlights Tuckman's missing stage of stagnation. | |
| Evolutionary Org Design and Participatory Leadership | 6 | 4 | 0 | 1 | Lenny contributes a key managerial insight about org design being an ongoing exercise in trading problems. Heidi enthusiastically agrees and connects it to the Toyota Kata and participatory leadership models. | |
| Key Reteaming Anti-Patterns to Avoid | 5 | 5 | 1 | 0 | Lenny prompts Heidi on anti-patterns and brings up the mistake of spreading high performers across teams. Heidi validates Lenny's point with a case study from AppFolio. | |
| Corporate Lifecycles and Appreciating Growth | 5 | 4 | 2 | 1 | Lenny shares Sheryl Sandberg's framing that rapid reorgs and constant change are inherently positive signs of hypergrowth. Heidi gently tempers this by pointing out that not all change is inherently good. | |
| The Art and Levels of Active Listening | 2 | 7 | 0 | 0 | Lenny asks Heidi about her listening skills on behalf of John Cutler. Heidi provides a masterclass on the three levels of active and global listening taught by the Co-Active Training Institute. | |
| Lightning Round: Books, Culture, Thrifting, and Fun | 2 | 3 | 0 | 0 | Lenny conducts the lightning round covering recommended books, vintage thrifting, life mottos, and the culture of fun at AppFolio. The interaction is warm and conversational. |
Statements from this episode (19)
Helfand: Fast-growing companies must embrace dynamic reteaming instead of static structures
“A lot of the books I would read on teams And the advice that I would get from people would be, ah, you know, you really want to keep your teams the same. You want to go for that forming, storming, norming, performing kind of thing. And I had thought about that…”
Helfand: Companies should include employees in organizational change decisions
“The reality is we're humans together, and there's a lot of opportunity to build companies that delight people, where they're excited to be included in decision-making about how the organization grows and changes or shrinks.”
Rachitsky: Corporate reorgs often create the biggest opportunities for career advancement
“What I find with reorgs and change is that it often leads to the biggest career opportunities because there's new roles to be filled. If things aren't changing, there's not going to be all of a sudden, Hey, we have this new role that we want for you. And a lot…”
Helfand: Redgate Software conducts open self-selection team reorganizations
“Redgate Software in Cambridge, UK, Chris Smith is a colleague of mine, and they do regular open self-selection reteaming activities when they're changing their strategic priorities.”
Helfand: Collaborative reteaming should be kept short to avoid organizational distraction
“Make a schedule, right? Bias towards shorter as opposed to longer. You don't want to deliberate on this forever because especially as you include more people, you know, it can be distracting. So you want to like proceed as expediently as you can.”
Helfand: Creating isolated teams with process freedom catalyzes new product lines
“Isolation is, or innovation by isolation, start a new team off to the side, a beneficial silo, give that team process freedom. Great for catalyzing new product lines within your existing company. Also great for emergencies”
Helfand: Reorgs imply top-down mandates, unlike dynamic reteaming patterns
“I think reorg, you know, again, it's true that reorganization is a traditional word and implies on the large, it implies Top down changes that you have no say in. It's just, it's something different than what I consider reteaming, which is these five patterns …”
Helfand: Expert City would not have innovated fast enough without team isolation
“If we would have stayed within our teams and we would have had to Develop with pixel perfect mockups done in Photoshop. Like, here you go. I don't think we would have been fast enough. I don't like that was not good for the innovation that we needed.”
Helfand: McDonald's saved the Chicken McNugget using an isolated SWAT team
“The Chicken McNugget was saved by an isolated team, SWAT team. There's a book called Teamwork. It's an old book from, I think the seventies I have in my bookshelf here. And there's a story of the Chicken McNugget that you can read about where they brought in c…”
Helfand: Pair programming and switching pairs prevents bottleneck single ownership
“You want people pairing and switching pairs. So they're not single owners of the system. So when they have an opportunity to do something that could be really important to the company, like be on one of these isolated teams, they can kind of fade out and not b…”
Helfand: Isolated innovation teams often leave unmaintainable technical debt for others
“I, I've seen isolated teams within companies where someone has the opportunity to sell something and they talk to their friends who are the engineers who build the feature for them, but then it leaves something for other people to maintain later and they weren…”
Helfand: Having new hires talk about themselves boosts retention and connection
“So you need to pay attention to the new hires that are joining, help them feel a sense of belonging, get them to talk about themselves, which is said to increase their sense of connection and retention. There's some research in the book, The Culture Code by Da…”
Helfand: Splitting teams creates new dependencies and shared role bottlenecks
“Sometimes splitting, though, can create dependencies that weren't there when you were together as one team. So you inherit other problems, or you might inherit challenges like, all right, the team decides it's more effective if they split into two or three, bu…”
Helfand: Menlo Innovations mandates regular pair rotation across all roles
“They built their company Menlo to have people work in pairs, not just the software engineers, team members work in pairs and they switch pairs at a regular cadence.”
Helfand: Org design is continuous Toyota Kata problem trading
“A lot of it is problem trading. You know, we have this challenge today. We decide, oh, there's a few ways we could handle this pros and cons of each solution. And let's, you know, it's like the kata. It's like the Toyota kata, you know, like grasp the current …”
Helfand: Fractionally allocating people across multiple projects fails due to context switching
“A lot of the times the percentages don't add up. It's very hard for people to multitask and be involved in like multiple efforts at once. It's hard for the brain with all the context switching that, that needs to happen in that case.”
Helfand: Splitting high-performing teams to distribute their talent destroys their chemistry
“He had this thought that, you know, maybe if like we had this one team that was like, I guess they were delivering at this cadence that they love and they were building this stuff and there's this energy and you can almost feel it. Like, let's just spread the …”
Helfand: Co-active coaching defines three levels of listening from internal to environmental
“I'm trained as a co-active coach, which involves different levels of listening. So you have level one, which is internal listening. Like if you and I are talking, but I'm thinking about like, what am I going to have for lunch? I'm in level one. I've got to red…”
Helfand: Cross-Team Events Ease Future Reorgs by Building Relationships Early
“You could work with different people, build these larger relationships, which, you know, later makes it easier for reteaming because then later if you reteam, you're not strangers with people. So you want to cultivate the community.”