Fragmented

Ownership

Teams and departments pursuing incompatible strategies in parallel, without a mandate to resolve conflicts.

Migrations that cross organisational boundaries, which is most of them, are vulnerable to this pattern. Without a clear, centralised strategy and an unambiguous mandate for who leads it, individual teams optimise for their own goals. Each makes locally reasonable decisions. Collectively, those decisions produce an incoherent whole.

We have found a simple test for whether this pattern is active: ask five senior stakeholders, independently and without warning, to describe what the migration is for and what success looks like. In our experience, this test returns genuinely consistent answers in fewer than a third of programmes at the point when it first becomes worth asking.

Post-acquisition integrations are the most acute expression of this pattern. Two organisations, each with established ways of working and proprietary technology investments, are asked to converge. Without a decision, made explicitly, with authority, and early, about who leads and on what terms, both will defend their existing approach. The result is not integration. It is parallel operation with a shared name and a growing reconciliation bill.


The consequences over time are predictable:

  • Significant rework when incompatible decisions - made in good faith by different teams - eventually collide. The collision is rarely clean.
  • Knowledge siloed by team, preventing the programme from learning and improving across waves.
  • Governance that is contested rather than functional, with no single view of what exists or who owns it.
  • Employee experience that deteriorates as teams receive conflicting guidance from multiple directions.


Watch for this signal

If different teams cannot independently articulate the same migration strategy, alignment has been assumed rather than created. Assumed alignment is one of the most expensive planning frictions in transformation programmes.

Root error: teams controlling their own domain rather than exposing it to shared decision-making.

NEXT: Pattern 3 - All-or-Nothing Planning
Visit icpnet.com

Share on social