Dynamic Reteaming:
The People Layer of Growth

Heidi Helfand

Author, Dynamic Reteaming; Engineering Leader

RETEAMING

The Core Idea

Why Teams Are Always Changing

"Reteaming is inevitable. We might as well get better at it because we're going to have to deal with it."

Teams at fast-growing companies are constantly changing, it's not a bug, it's a feature
The "five patterns" of reteaming happen at all levels: individual, team, org-wide
Focus on the people layer alongside product delivery
Most leadership books ignore this reality; reteaming requires active skill-building

The Five Patterns

How Teams Actually Change

One by One: Hiring and departures at the company level
Grow & Split: One large team divides into multiple focused teams
Merging: Multiple teams consolidate (shrinking pattern)
Isolation: Create a "beneficial silo" with process freedom for innovation
Switching: Individual movement between teams for learning and growth

Reorg vs. Reteaming"Reorg" implies top-down, one-time organizational change. "Reteaming" is any team pattern change at any level, happening continuously, not just once a year.

The Expertcity story

Isolation at its best: A team built SecureDocs in isolation at AppFolio, given complete freedom. It became its own successful product line, later acquired.

Whiteboard transparency

At Procore, visualizing team structure on whiteboards (with names, missions, open roles) helped 80 people self-select into new positions and spot design flaws.

Making Change Stick

Frameworks for Leading Reteaming

Transitions (Bridges): Every change has endings, a neutral zone, and new beginnings. Don't skip the emotional middle.
RIDE Framework: Clarify who's Requesting, who gives Input, who Decides, and who Executes. Not all change is democratic, be clear on decision-making.
Time box ruthlessly: "Make a schedule biased towards shorter as opposed to longer." Deliberation fatigue kills momentum.
Story of our team: When teams merge, have each create a timeline of their milestones. Share history. Build belonging.

Grow & split signals

Meetings longer • Decisions slower • Work diverges • Standup attendance drops

Isolation best practices

Give process freedom. Report to one decision-maker. Shield from interruption. For sustainability: plan exit strategy with larger org.

One-by-one wins

New hire onboarding: Use peer pairing, not solo desk. Existing team: Coach through changes they didn't decide. Transparency matters.

Key Principle

Involve, Don't Impose

People want agency. Show them future team structure early (via whiteboard, visual, or pitch event).
Let them give feedback. They'll spot design flaws you missed.
Let them self-select. People are delighted by work others don't expect them to want.
Be clear on what's negotiable. Business decisions (acquisitions, downsizing) aren't. Team design often is.

Pat Wadors wisdomDecision clarity via RIDE prevents friction. When everyone knows their role in change, reteaming becomes enablement, not chaos.

Heidi's Contrarian Moves

Reteaming Myths vs. Reality

✗Keep teams together foreverINSTEAD →✓ Normalize team change at every level. Static teams miss growth opportunities.

✗Plan reorgs in secret, then announceINSTEAD →✓ Transparency + early feedback = better design + higher buy-in + fewer blind spots.

✗Reteaming is disruptive overheadINSTEAD →✓ Reteaming enables learning, fulfillment, and competitive advantage. It's core work.

✗One framework fits all team changesINSTEAD →✓ Five different patterns require five different playbooks. Match the tactic to the pattern.