💡

InsightHunt

Hunt the Insights

H

Heidi Helfand

Episode #119

Author & Consultant

Dynamic Reteaming

👥Team & Culture🎯Product Strategy🚀Career & Leadership

📝Full Transcript

11,864 words
Heidi Helfand (00:00:00): Reteaming is hard. Reorgs are hard. You can't lump them all into one thing with oh, it's all great all the time. No, it's not. If we could just build the software, deliver to the customer, get the product market fit, hey, have we delighted them or not? If only it could be that easy. No, we have the people layer, so let's focus there too. Lenny (00:00:25): Today my guest is Heidi Helfand. After two decades in the tech industry, Heidi became fascinated with how teams are organized, how org structures change and how to set teams up for success through that change. She now teaches workshops and runs courses and consults on how to effectively reorganize your teams. And in her book Dynamic Reteaming, Heidi delves deep into why change is actually good for your teams, why you're better off not having super stable teams, how to effectively execute reorgs, and through that, how to reduce attrition, stagnation, and knowledge silos. In our conversation, Heidi shares the five types of reteaming, anti-patterns to avoid when making org changes, what sort of team structure is most conducive to creating totally new products, why being transparent about your reorg plans is definitely worth considering. Also, how Heidi became such a great listener with a lot of really interesting insights and advice there and so much more. Huge thank you to John Cutler for introducing me to Heidi. With that, I bring you Heidi Helfand after a short word from our sponsors. (00:01:29): This episode is brought to you by productroadmap.ai and Ignition. Productroadmap.ai is the first AI roadmapping suite. It helps ensure roadmaps drive revenue by instantly aligning product with your sales and marketing teams to capture upsell opportunities. Built by early leaders from Rippling and Craft, it automatically identifies feature gaps from your CRM data and your customer conversations, adds them to shareable roadmaps easily prioritized by revenue impact, and then seamlessly closes the l...

💡 Key Takeaways

  • 1Reteaming is inevitable in growing companies; focus on mastering the transition rather than fighting for stability.
  • 2Involve team members in reorg decisions (Whiteboard Reteaming) to increase buy-in and reduce fear.
  • 3Use the 'Isolation' pattern to catalyze new products or solve crises, but grant the team process freedom.
  • 4Avoid the 'percentage allocation' anti-pattern where people are split across multiple projects.
  • 5Build redundancy through pair programming and rotation to prevent knowledge silos and make reteaming easier.

📚Methodologies (3)

👥 Team & Culture

A structural framework identifying the five distinct ways teams change. Understanding which pattern you are experiencing helps leaders choose the right facilitation techniques and set correct expectations.

Core Principles

  • 1.One-by-One: Managing the flow of individuals joining or leaving a team (onboarding/offboarding).
  • 2.Grow and Split: Breaking a large team into smaller units when communication breaks down due to scale.
  • 3.Merging: Combining teams or departments to reduce silos or align with business consolidation.
  • +2 more...

"If we could just build the software... no, we have the people layer, so let's focus there too."

#patterns#dynamic#reteaming
View Deep Dive →
Innovation by Isolation

by Heidi Helfand

🎯 Product Strategy

A deliberate strategy to spin off a dedicated team to work on a high-stakes problem or new product. This team is physically or digitally separated and exempt from standard corporate bureaucracy to iterate faster.

Core Principles

  • 1.Process Freedom: The team must not be forced to use the main organization's legacy workflows (e.g., Waterfall vs. Agile).
  • 2.Executive Protection: A senior leader must provide 'air cover' and strictly tell other teams not to disturb the isolated unit.
  • 3.Clear Decision Making: Report directly to a decision-maker to avoid 'death by committee'.
  • +1 more...

"The Chicken McNugget was saved by an isolated team, SWAT team... they didn't work in their same plant."

#innovation#isolation#strategy
View Deep Dive →
🚀 Career & Leadership

Instead of planning reorgs in a back room, leaders visualize the future state (e.g., on whiteboards) and invite team members to influence the outcome. Clarity is maintained using the RIDE model.

Core Principles

  • 1.Visualize Options: Show the new team structure, missions, and open slots clearly to everyone.
  • 2.RIDE Decision Model: Clarify who Requests, Inputs, Decides, and Executes the change.
  • 3.Managed Transparency: You don't have to vote on everything (e.g., acquisitions), but give agency where possible (e.g., team selection).
  • +1 more...

"If we normalize the idea that it's okay for teams to have input into their future structures, maybe they'll bring it up."

#participatory#reteaming#framework)
View Deep Dive →