Dynamic Reteaming: The Art and Wisdom of Changing Teams

Visualize the future org publicly and invite feedback before locking it in.

At Spotify and Procore, leaders rolled whiteboards with proposed team structures, missions, open head-count, and every employee’s name; people corrected mistakes and lobbied for new roles in real time.

Why: Early visibility converts fear into agency, surfaces blind spots, and distributes career opportunities equitably.

"I really like it when there's transparency in reorgs... people had the opportunity to see opportunities within their own company that they might say, hey, I’m interested in this."

Use the RIDE model to clarify who Requests, gives Input, Decides, and Executes any change.

RIDE (Request, Input, Decide, Execute) prevents ambiguity and resentment by spelling out decision rights up front.

Why: Clear roles reduce anxiety and allow people to engage appropriately—whether offering input or accepting final authority.

"being clear on who the decision maker is in a change is really important... it's like R-I-D-E."

Expect endings, neutral zone, and new beginnings in every reteaming.

William Bridges’ transition model helps leaders acknowledge the emotional limbo between old and new states and to paint a compelling picture of the future.

Why: Normalizing the emotional journey lowers resistance and speeds adaptation.

"He talks about endings, neutral zone, and new beginning... once I learned about that transition framework, going through any subsequent changes myself became a lot easier to grasp."

Shield a small team with process freedom and executive air-cover to incubate new products.

Expertcity’s pivot to GoToMyPC, SecureDocs at AppFolio, and even the Chicken McNugget at McDonald’s succeeded because the teams were physically and bureaucratically separated from the mothership.

Why: Fast iteration loops and single-threaded leadership compress time-to-market for existential bets.

"taking a team off to the side, giving that team process freedom... it was a privilege... we got to deploy more frequently."

Build pairing and regular switching into daily work so no one person becomes a single point of failure.

Menlo Innovations and AppFolio rotate pairs weekly; critical systems like rent-payment processing stay safe even when experts leave.

Why: Redundancy reduces bus-factor risk and makes future reteaming painless.

"switching also helps build that knowledge redundancy in your company... if someone leaves, they don't leave with all the information in their head."

Split teams when meetings drag, decisions stall, or stand-ups lose focus.

Typical indicators: 13 people where five once thrived, divergent work streams, and visible disengagement.

Why: Communication overhead grows quadratically; splitting restores cohesion and delivery cadence.

"some signals that teams might bring up... the meetings are taking longer... No one's paying attention in the standups so much anymore."

Run a “Story of Our Team” timeline exercise when groups combine.

Each legacy team lines up by tenure, records milestones and proud creations, then shares with the new merged entity to create shared history.

Why: Shared narratives accelerate trust and surface complementary strengths.

"each team makes a timeline... they tell each other about it... we get to learn about each other."

Frame every re-org as a marketplace of new roles rather than a threat.

Transparent plans let ambitious employees opt into emerging missions before external hiring fills them.

Why: Retention rises when people see growth paths without leaving the company.

"it often leads to the biggest career opportunities because there's new roles to be filled... position themselves in a way where like, okay, cool, there's a new position."