The art and wisdom of changing teams | Heidi Helfand (Author of Dynamic Reteaming)
Executive Summary
Heidi Helfand discusses visible team-change plans, decision authority, onboarding, team splits and shared histories for merged teams. Selected third-party transcript coverage excludes detailed company anecdotes, transition psychology, isolated innovation teams, listening advice and closing recommendations. Organization examples are her accounts, unverified here. Untimed editorial topics are not video chapters.
Key Takeaways
Make the starting plan visible
Helfand describes showing a proposed team structure and inviting people to identify problems and opportunities. A visible starting point gives people something concrete to respond to. Transparency is not the same as pretending every participant has final authority.
Name who decides
She says clarity about the decision maker matters when teams change. Some decisions allow participation and some do not. State the actual opportunity for input and who will make the final call so involvement does not create false expectations.
Set a bounded process for change
Helfand favors a schedule that does not leave the organization deliberating indefinitely. Wider participation can be distracting if the process has no end. Choose enough time for useful input, then make the decision and explain the next steps.
Help both newcomers and existing members
In one-by-one changes, she considers belonging for the person joining and the experience of people already there. A new hire or leader should not simply arrive as a surprise. Explain what is changing and help the team build working relationships.
Use signals to assess a split
Longer meetings, harder decisions and divergent work can signal that a growing team needs a different structure. Helfand does not present headcount alone as the answer. Ask what the team is experiencing and whether a split would address the actual difficulty.
Account for the dependencies a split creates
Splitting can solve one problem while adding coordination needs, especially when teams share a PM, designer or other specialist. Helfand calls this problem trading. Compare the new structure's costs with the old one rather than treat reorganization as a clean cure.
Give merged teams a shared history
Her story-of-our-team exercise lets groups share milestones, work they are proud of and events that shaped them. This helps a newly merged team learn about itself before looking forward together. Preserve useful context rather than assuming a new org chart creates a shared identity.
The Conversation Breakdown
Make the starting plan visible
⏱ Untimed topicHelfand describes showing a proposed team structure and inviting people to identify problems and opportunities. A visible starting point gives people something concrete to respond to. Transparency is not the same as pretending every participant has final authority.
Name who decides
⏱ Untimed topicShe says clarity about the decision maker matters when teams change. Some decisions allow participation and some do not. State the actual opportunity for input and who will make the final call so involvement does not create false expectations.
Set a bounded process for change
⏱ Untimed topicHelfand favors a schedule that does not leave the organization deliberating indefinitely. Wider participation can be distracting if the process has no end. Choose enough time for useful input, then make the decision and explain the next steps.
Help both newcomers and existing members
⏱ Untimed topicIn one-by-one changes, she considers belonging for the person joining and the experience of people already there. A new hire or leader should not simply arrive as a surprise. Explain what is changing and help the team build working relationships.
Use signals to assess a split
⏱ Untimed topicLonger meetings, harder decisions and divergent work can signal that a growing team needs a different structure. Helfand does not present headcount alone as the answer. Ask what the team is experiencing and whether a split would address the actual difficulty.
Account for the dependencies a split creates
⏱ Untimed topicSplitting can solve one problem while adding coordination needs, especially when teams share a PM, designer or other specialist. Helfand calls this problem trading. Compare the new structure's costs with the old one rather than treat reorganization as a clean cure.
Give merged teams a shared history
⏱ Untimed topicHer story-of-our-team exercise lets groups share milestones, work they are proud of and events that shaped them. This helps a newly merged team learn about itself before looking forward together. Preserve useful context rather than assuming a new org chart creates a shared identity.
Core Frameworks & Ideas
Visible starting plan
Present a concrete proposed structure, invite useful input, and make decision authority clear.
Problem-trading review
Assess both the difficulty a team change addresses and the dependencies or costs it creates.
Story of our team
Let merging groups share milestones and work they are proud of to build a shared history before looking forward.
Actionable Next Steps
- ✓Show a proposed team structure and explain which parts are open for input.
- ✓Name the decision maker and the end of the input period.
- ✓List the communication problems a split would solve and the dependencies it could create.
- ✓Ask merging teams to share a timeline of milestones and work they are proud of.
Notable Quotes
“And being clear on who the decision maker is in a change is really important.”
“Make a schedule biased towards shorter as opposed to longer.”
“Sometimes splitting though can create dependencies that weren't there when you were together as one team.”
The One Thing to Remember
Explain the plan and who decides, then assess what each team change solves and what new problems it creates.