APMG Change Management Foundation study materials
APMG Change Management Foundation study resources

Merger, middle managers and a nine-month big bang

APMG Change Management Foundation · Put your knowledge to work in context.

All case studies

Merger, middle managers and a nine-month big bang

A 1,200-person insurer is merging two claims functions after an acquisition. Site A (700 staff) uses a team-based, high-autonomy culture; Site B (500 staff) is process-driven with central quality checks. The integration targets £6m annual savings and 120 role reductions over 18 months. Three other change programmes are already running; engagement in claims is 54% versus 71% company-wide. Middle managers say they learned of the new structure from a leaked slide. The executive has approved a 'big-bang' move to one operating model in nine months and wants a communication campaign. The integration director asks whether to proceed big-bang or use pilots, and what organisational elements must align first.

1. Should the integration director proceed with a nine-month big-bang move to one operating model, or use pilots? Give a recommendation and the reasoning that would change it.

Read the worked answer

Recommendation: Do not run a pure big bang. Use a staged move with decision gates, beginning with one claims type or one site, then scale. A nine-month big bang assumes alignment that the evidence does not support: low engagement in claims, three concurrent programmes, excluded middle managers, and two different control cultures. It also combines structural change, role reductions and cultural integration in one hit, which raises the risk of losing critical claims expertise.

Why pilots help here: They generate operational evidence on quality, cycle time and manager workload; they build credible local champions; and they allow the operating model to be refined before 120 role decisions are locked. The cost is delay to some savings and a temporary two-speed operation, which must be managed explicitly.

What would change the recommendation: If the target model were already proven elsewhere, savings depended on a single cut-over date, or the pilot would create unacceptable customer risk, a compressed big bang could be defensible. Even then, I would stage by process or site and keep go/no-go gates.

Judgement: The choice is not 'big bang good or bad'. It is whether the organisation has the alignment and capability to absorb the change at that speed. Here it does not.

2. Using an organisational alignment model, identify the most serious misalignments and their implications for the change approach.

Read the worked answer

Using a 7S-style lens:

  • Strategy vs structure: The strategy is cost reduction and one operating model, but the two sites have different structures and quality-control logics. Choosing one model without deciding the quality/autonomy balance will create conflict.
  • Systems vs style: Site B's central quality checks reward compliance; Site A rewards team autonomy. Metrics, rewards and decision rights must be redesigned together, or managers will optimise locally.
  • Staff and skills: 120 role reductions create survivor anxiety and competition. Critical claims knowledge may leave before it is transferred.
  • Style and shared values: Middle managers were bypassed by a leak. That undermines trust and their ability to lead the change.

Implications: Start with design principles and role clarity, not a communication campaign. Sequence the work: agree the target operating model and quality approach; align metrics and decision rights; equip middle managers; then move roles in waves with knowledge transfer. A communication campaign cannot compensate for unresolved structural choices.

3. What should be done about the middle managers and the leaked slide?

Read the worked answer

Acknowledge the leak directly rather than pretending it did not happen. The issue is not the slide; it is that middle managers learned about their future from an uncontrolled channel. They now need both information and a role in shaping the transition.

Actions:

  • Brief middle managers first, with the same facts as the executive and an explicit statement of what is decided and what is not.
  • Involve them in design workshops for role clarity, quality checks and transition sequencing.
  • Give them conversation tools for their teams: what changes, what does not, what is unknown, when decisions will be made.
  • Hold a short, visible repair conversation with the executive sponsor.
  • Set expectations that they lead local communication, and support them with FAQs and escalation routes.

Judgement: Do not over-promise that no roles will go. Credibility depends on being honest about the 120 reductions and the decision timetable. Middle managers are a critical delivery channel; excluding them again would turn a communication problem into an implementation risk.