Merge Two Teams After a Restructure
Team & Leadership · 2–4 weeks · Advanced
The job
Integrate two teams brought together by restructure, merger, or reorg.
What the sponsor gets
Each canvas and map from this playbook — Culture Map, Team Canvas, Stakeholder Map, OKR Canvas, Retrospective Canvas — exports as a PDF, or as PowerPoint on Pro, straight from the session, and the whole run exports as one PowerPoint for the sponsor. Nothing is redrawn.
The method
Listen before designing
Interview members of both teams individually. Understand their concerns, their pride in what they've built, what they fear losing, and what they hope to gain. Don't skip this — announcing a new structure without listening first creates resistance.
Tip: People from the "absorbed" team will assume they're second-class citizens — address this directly and early.
Map both team cultures
Create a Culture Map for each team, then compare them side by side. Where do they align naturally? Where will they clash? Understanding cultural differences prevents the assumption that one team's way is "right."
Tip: The clashes will be about small things — meeting norms, communication channels, decision-making speed — not big things. Small things compound.
Build a shared Team Canvas
Bring both teams together to create a new Team Canvas. Don't reheat either team's old one — start fresh. This signals that the merged team is a new entity, not a takeover.
Tip: Have each team present what they're bringing to the new team (skills, relationships, knowledge) — it reframes the merge as additive, not subtractive.
Map the new stakeholder landscape
Create a Stakeholder Map for the merged team. Both teams bring relationships — map them so nothing falls through the cracks during transition.
Tip: The biggest post-merge risk is key stakeholders feeling abandoned because their old point of contact is now "on a different team."
Set shared objectives
Create OKRs that require cross-team collaboration. Shared objectives build shared identity faster than any team-building exercise.
Tip: Pair people from different legacy teams on each OKR — forced collaboration creates real relationships.
Establish new rituals
Design the merged team's meeting cadence, communication channels, and social rituals. Take the best of both teams' practices and add one new tradition that belongs to neither.
Tip: The new ritual matters more than you think — it gives the merged team a shared experience that neither legacy team owns.
60-day integration retrospective
Run a retrospective at 60 days. Has the merged team formed a genuine identity? Where is integration working and where does it still feel like two teams sharing a Slack channel?
Tip: If people still say "we used to do it this way on my old team" at 60 days, integration isn't done — revisit the cultural norms.
The canvases and maps
- Culture Map
- Outcomes across the top, the behaviours that produce them beside their enablers and blockers, and values and rituals underneath, so culture becomes something you can change, not just describe.
- Team Canvas
- Purpose, goals, roles, values and norms on one sheet, so a team agrees how it works together before it argues about what to do.
- Stakeholder Map
- Power against interest in four quadrants, so engagement effort goes where it matters and nobody important is handled by accident.
- OKR Canvas
- One objective, three key results and the initiatives beneath them, so ambition and measurement sit on the same page and no initiative floats free of a result.
- Retrospective Canvas
- What went well and what to improve, then start, stop and continue, so reflection ends in actions rather than a list of complaints.
What it doesn't do
It doesn't run the room for you or decide for the client. The steps, canvases and duration are a starting point you adapt; the judgement stays yours.