The Five Patterns of Dynamic Reteaming
Every team change is one of five patterns — name it, then manage it deliberately.
- Difficulty
- Moderate
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 95%
Heidi Helfand argues that team change is inevitable in any growing or shrinking company, and that fighting for permanently stable teams is a losing battle. Instead of the catch-all word 'reorg', she classifies all team change into five observable patterns: one-by-one, grow-and-split, merging, isolation, and switching. Once you can name which pattern you are in, you can apply the specific tactics that make that pattern go well before, during, and after.
Origin
Developed by Heidi Helfand across two decades in fast-growing SaaS startups (Expert City/Citrix Online, AppFolio, Procore) and codified in her book Dynamic Reteaming. It was a direct reaction against the standard advice she kept reading — Tuckman's forming/storming/norming/performing and the 'keep teams stable' orthodoxy — which did not match her lived experience of going from the 10th employee to a company of thousands.
Core principles
- 01Reteaming is inevitable — get good at it rather than trying to prevent it.
- 02'Reorg' carries top-down baggage; most team change is smaller, more frequent, and more participatory than that word implies.
- 03Change happens at multiple levels simultaneously — individual, team, team-of-teams, department, company (panarchy).
- 04Every pattern has 'balconies and basements' — an upside and a way to screw it up.
- 05There is no perfect org structure, only the best idea you have at the time plus systems to catch its downsides.
How to run it
- 1
Diagnose the pattern: one-by-one
Someone joins or leaves the company. Tactics: give the joiner a first-day pair rather than a lonely desk, get them talking about themselves to build belonging, and visualize hiring plans so existing staff are not blindsided by a new arrival — especially a new manager above them.
Pro tip Coach the incumbents through the change too, not just the new hire — they are often the ones who did not get a say.
- 2
Diagnose the pattern: grow-and-split
A team grows too big and splits into two or more. Watch for the signals: meetings are taking longer, decisions are harder than when there were five of you, the work has diverged, and nobody is paying attention in standup anymore.
Pro tip Normalize teams having input into their own future structure — then they will raise the split themselves before it becomes painful.
Watch out Splitting creates dependencies that did not exist before, and shared roles (one PM, one designer, one QA person) suddenly have to be divided. Splitting trades one problem for another.
- 3
Diagnose the pattern: merging
Two or more teams combine — through downsizing, consolidation of leadership, or one company acquiring another. Run a shared-history ritual so the merged entity has a common story instead of two rival ones.
- 4
Diagnose the pattern: isolation
Pull a small team off to the side as a deliberate, beneficial silo with process freedom. Use it to catalyze new product lines inside an existing company, and for emergencies like incidents or a performance crisis.
Watch out An isolated team can build something nobody else agreed to maintain. Work the hand-back out with the larger organization up front.
- 5
Diagnose the pattern: switching
Move people between existing teams, at short or long cadences. Switching is tied to learning, variety, and fulfillment — it is the antidote to the phase Tuckman forgot: stagnating. It also builds knowledge redundancy across systems.
Pro tip Switching can feel like a new job inside the same company, extending the lifespan of great employees.
Watch out Do not haphazardly rotate people every two weeks with no say in the matter — forced switching destroys the fulfillment it is supposed to create.
- 6
Apply pattern-specific tactics before, during and after
Once the pattern is named, choose deliberate tactics for each phase of it rather than treating all change as one undifferentiated 'reorg' event. Accept that the structure you pick is provisional and will need to change again as conditions do.
In the wild
Helfand was employee 15 at Expert City, building a marketplace for remote tech support. The CEO killed the product because it had earned roughly six dollars in a month and told her to go to the beach rather than start work that would need maintaining. She was then invited onto a small team off to the side, freed from waterfall development and running fast iteration loops.
→ That isolated team built GoToMyPC — the pivot that saved the company and led on to GoToMeeting and GoToWebinar.
AppFolio's first team grew and split into two or three teams. Some engineers who had been pair-programming together felt the loss and started their own regular rotation between the new teams.
→ The engineers restored the collaboration they valued without reversing the split — learning, joy and fulfillment inside the new structure.
Common mistakes
Treating all team change as a 'reorg'
The word implies large, top-down change you had no say in. Calling one person moving teams to learn web operations a 'reorg' triggers fear that the situation does not warrant, and it hides the four other patterns entirely.
Fighting for permanently stable teams
In a fast-growing or shrinking company, team change is the natural evolution. Trying to freeze teams both fails and forfeits the learning, redundancy, and career opportunity that change creates.
Is it for you?
Best for
Founders, engineering leaders and people-ops leads at fast-growing or contracting startups where team boundaries keep moving and 'reorg' has become a dirty word.
Not ideal for
Small, static teams in a stable business with no growth, no attrition and no new product bets — there is nothing to reteam.
From the transcript
“the five uh patterns of raming one by one someone joins your company or someone leaves your company grow and split it's a growth pattern…”
“isolation is or innovation by isolation start a new team off to the side a beneficial Silo give that team process Freedom”
“the meetings are taking longer you're in that case where it's harder to make decisions it was easier when there were like five of us…”
From the episode
The art and wisdom of changing teams
Heidi Helfand (author of Dynamic Reteaming)