Dynamic reteaming: how and why to embrace team change

Executive overview

Most advice tells you to keep teams stable — but in any growing or shrinking company, teams inevitably change. Resisting that change creates silos, stagnation, and attrition; working with it builds resilient, engaged organisations.

Heidi Helfand maps five patterns by which teams change and offers concrete tactics for each. The goal isn't perfect org structure — it's developing the habit of navigating change well.

Team change is inevitable; the only question is whether you handle it deliberately or reactively.

The five patterns of reteaming

1. One by one — someone joins or leaves the company. Distinct from switching because it affects headcount, not just assignment.
2. Grow and split — a team grows until coordination breaks down, then splits into two or more focused teams.
3. Merge — two or more teams consolidate, often driven by downsizing, acquisition, or leadership consolidation.
4. Isolation — a small team is placed off to the side with process freedom to innovate or handle emergencies.
5. Switching — individuals move between teams, short- or long-term, for learning, fulfillment, or knowledge redundancy.

One by one: joining and leaving

• When someone joins, give them a first pair — avoid leaving new hires isolated on day one.
• Communicate hiring plans visibly; it's destabilising to discover a new manager was hired without warning.
• Coach existing team members through the change, not just the new hire.
• Departures consolidate knowledge risk — pairing and shared ownership reduce that risk before it materialises.

Grow and split

• Signals: meetings take longer, decisions stall, standup attention drifts, work has visibly diverged.
• Normalise team input into structure decisions — teams that can raise a split themselves often do it at the right time.
• Splitting creates new dependencies and shared-resource problems (one PM, one designer). Every solution trades one problem for another.

Merge

• Common in downsizing, consolidation, or post-acquisition integration.
• Use the "story of our team" exercise: each team builds a timeline of when people joined, milestones, and things they're proud of, then shares it with the newly merged group.
• Shared history accelerates trust-building in merged teams.

Isolation: innovation and emergencies

• Isolate the team physically or spatially — claim a region, make it theirs.
• Tell other teams explicitly not to pull them into other work; this needs to come from a leader.
• Give the team process freedom — let them iterate faster than the rest of the org.
• Report line should go to someone with real decision-making authority, so decisions don't get reversed or bogged down.
• Build shared ownership in the main codebase before pulling people out, so no one is a single point of failure.
• Works for emergencies too: convene, solve, disband.
• Failure mode: isolated team builds something others must maintain without being consulted.

Switching

• Driven by learning, fulfillment, and knowledge redundancy — not just logistics.
• Regular pair-switching prevents single owners of systems; reduces risk when people leave.
• Short- or long-term rotations can extend the tenure of strong employees by giving them new challenge within the company.
• Failure mode: mandatory switching with no agency destroys motivation.

Transparent and collaborative reteaming

• Visualise the planned structure publicly — whiteboards with team names, missions, headcount, and people's names.
• Invite input before the plan is final; people catch mistakes and identify better fits.
• Employees can self-identify for roles they want rather than waiting to be assigned.
• Time-box the process: bias toward shorter deliberation, not longer.
• Use the RIDE framework for decision clarity: who is Requesting, who gives Input, who Decides, who Executes.
• Some decisions (e.g. acquisition) are not up for input — be clear about which is which.

Anti-patterns to avoid

• Percentage allocation — splitting one person across five projects at 10–20% each. Context-switching costs negate the benefit.
• Sudden appearances and disappearances — reteaming with no communication. People need to know what's happening.
• Spreading high performers — splitting a high-chemistry team to "distribute" the performance rarely works; the chemistry is the performance.
• Treat all patterns as having "balconies and basements" — each can be done well or badly.

Accepting that no org structure is permanent

• Every structure is the best available answer to current conditions, not a permanent solution.
• Change accelerates when companies grow fast; that is a sign of health, not dysfunction.
• Use the Toyota Kata cycle: grasp current condition → identify target condition → experiment → repeat.
• Appreciate high-performing team moments; they are temporary by nature, and that is normal.
• Company life cycles (Adizes model) apply to teams too: birth, growth, maturity, disruption, renewal.

Listening as a leadership skill

• Level 1 — internal listening (thinking about yourself while someone talks). Redirect attention outward.
• Level 2 — focused listening; full attention on the other person.
• Level 3 — environmental listening; noticing body language, tone shifts, what's unspoken.
• Listening is a trainable skill — Coactive coaching framework (Coactive Training Institute) is one structured path.