Post-Merger Integration at a Retail Bank
Meridian Bank, a fictional Lagos-based retail bank, has acquired Alpha Trust Bank, a smaller competitor. The combined group has 2,400 staff, 18 overlapping branches and two incompatible core banking systems. Nine months after completion, the IT integration has slipped by a further six months, customer attrition has reached 7% in the acquired bank's retail segment, and the union has threatened a strike over branch closures. Alpha staff say decisions are being made by Meridian without consultation; Meridian managers say Alpha staff are resisting standard processes. Only three of the top 40 leaders have been retained from Alpha. The board wants cost synergies within 12 months and has asked you to lead the integration review.
1. Diagnose integration readiness and recommend a sequenced change plan for the first 100 days.
Read the worked answer
Diagnosis. The merger has a clear strategic rationale but weak change readiness. Eighteen overlapping branches create job fear; the nine-month IT delay removes a visible symbol of progress; 7% customer attrition shows that uncertainty is already affecting service. A union strike threat and culture differences between the larger Meridian and smaller Alpha mean that a top-down closure plan will trigger resistance. Losing 37 of Alpha's top 40 leaders removes informal networks and customer relationships. Staff will watch what leaders do, not what they say.
Sequencing. First, form an integration steering committee with leaders from both banks and a clear decision-rights map. Build a stakeholder map covering the union, top 40 leaders, customer-facing staff, regulators and large customers. Communicate an honest vision: what will not change for customers, what will change for staff, and the timetable. Second, resolve branch overlap decisions early but announce support through redeployment, severance and retention bonuses for critical IT and relationship staff. Third, engage union representatives before announcing closures. Fourth, create quick wins: stabilise IT incidents, protect top customers and publish a simple service promise. Fifth, set a weekly integration dashboard and escalation route. Do not launch culture programmes before basic job and system uncertainty is addressed.
2. Design a dashboard to track integration success and advise whether branch closures should be delayed until IT integration is complete.
Read the worked answer
Dashboard. Use leading and lagging measures: customer attrition by segment and branch; NPS and complaint resolution; staff turnover and voluntary attrition of critical roles; union grievances and days lost; IT incident volume, system availability and migration milestones; branch productivity and cost-to-serve; synergy realisation; loan and deposit growth; and regulatory issues. Review operational metrics weekly and board metrics monthly.
Closure decision. Delay full closures until IT integration is stable, but do not freeze all branch decisions. The 7% attrition and IT delay mean closures could compound service failure and give competitors an opening. Use a gated approach: stabilise core banking and customer data; run a pilot closure or merger of two branches; measure attrition, complaints and staff redeployment; then proceed branch by branch. If the pilot shows service deterioration beyond agreed thresholds, pause. The board should approve the gates and thresholds in advance. This balances synergy pressure with customer and staff risk.