Article · Alliances
Two alliances, one team: the first 30 days
Agreeing to merge is the easy part. The real work begins when two established groups try to become one.
Series Alliance Leadership Part 15 of 21
Published · 2 min read
Before the move: agree on the basics
Confirm how many members can transfer, the expected activity level, event times, communication approach and leadership arrangements. Be honest about limited places and the eight R4 positions.
Day 1: Welcome properly
Introduce incoming players and officers. Explain where to find schedules, whom to ask for help and how the alliance operates. Do not assume everyone knows your habits.
Week 1: Play together
Encourage mixed participation in rallies and events. Ask established members to help newcomers settle in. Make sure incoming players are included in ordinary conversation.
Week 2: Fix friction
Check whether event times, expectations or communication are causing problems. Handle misunderstandings privately rather than letting old-alliance labels become insults.
Week 3: Recognise contribution
Celebrate useful participation from both groups. Reinforce that R3 is a respected rank and R4 is a responsibility, not a badge of superiority.
Week 4: Review honestly
Look at retention, activity, Alliance Duel, event participation and member feedback. What improved? Who feels excluded? Which arrangements need changing?
The test
If people still refer to “our lot” and “their lot” whenever something goes wrong, the merger is not finished.