Introduction

Telecom integrations are among the most complex programs executives undertake. They reshape markets, reconfigure infrastructure, alter competition and expose leadership reputations for years.

For many Chairs and CEOs, a program of this scale will be the largest and most demanding assignment of a career. It may define it.

The strategic case is often sound. The ambition justified. These programs matter – and they deserve to succeed.

Yet large programs repeatedly overrun on cost, miss schedule and underdeliver benefits.

Research from McKinsey, Bain, The Standish Group and Professor Bent Flyvbjerg shows this consistently. Delivering fully against the original commercial case is uncommon.

The reason is rarely weak leadership or lack of effort.

The difficulty lies elsewhere.

Approval Is Not Engineering

At approval stage, the plan fits on a handful of slides. Synergies are modelled. Milestones defined. The value case appears clear.

But approval is not engineering.

Before commitments are locked, one question matters:

What has been tested under real conditions – and what still rests on assumption?

Which dependencies are fully mapped? Which sequencing constraints are proven? Which synergy numbers rely on conditions not yet tested?

These questions sound simple. But in large telecom integrations they are decisive.

When Commitments Come Before Engineering

Major telecom mergers must satisfy regulators, investors and markets before delivery is fully engineered.

Regulators require commitments on coverage, investment and spectrum. Investors require quantified synergies. Markets expect timelines.

Those commitments are usually public.

Commitments are fixed – but engineering is not.

Targets are often announced months before the transaction closes. Delivery leadership may only be fully established after those commitments are made.

By the time the deal closes, the commitments are locked.

The delivery organisation inherits a plan shaped largely by commercial negotiation – along with assumptions and sequencing choices fixed before the engineering model was fully tested.

Engineering must now catch up with promises already made.

The gap is often larger than it first appears.

From Board Plan to Delivery Reality

At approval stage, the plan fits on a few slides. In delivery, it expands into thousands of interlocking decisions:

Network transitions

System migrations

Supplier coordination

Overlapping workstreams

Regulatory milestones

Customer migrations

Each introduces dependencies and sequencing constraints.

Committing to an outcome is not the same as engineering the path that delivers it.

That distinction determines success.

Experience Shows the Pattern Clearly

I first encountered this dynamic early in my career.

At International Computers Limited/Fujitsu, the 3900 mainframe program was given a three-year delivery target. The previous generation had taken roughly 7 years.

The schedule reflected commercial ambition.

Within months, critical assumptions had to be surfaced and the delivery model reset.

The program ultimately succeeded – but only after those assumptions were exposed and redesigned.

The same pattern appeared later in telecom infrastructure.

At Plessey Telecommunications, I was asked to lead the System X Public Switching program – prime contractor to BT – following several false starts, delivering the UK’s transition from electromechanical switching to digital networks under live national conditions.

The industry was navigating a technological discontinuity.

Software had suddenly become central to the network, and organisations across the sector were learning how to engineer and manage systems at a new level of complexity.

Milestones were revised. Sequencing rebuilt. Dependencies clarified.

Working closely with BT’s senior technical leadership, the program was re-planned around operational constraints.

The first major production release was delivered ahead of the revised schedule.

Different technologies. Different decades. The same pattern appeared: commercial commitments were set first. Engineering feasibility emerged under load.

The technology has changed dramatically since then. The pattern has not.

Integration Is an Engineering Program

Once approval is secured, the centre of gravity shifts from strategy to execution.

At that point telecom integration stops being primarily a financial exercise.

It becomes a large-scale engineering and operational program.

Networks must be re-architected

IT systems aligned

Operating models reshaped

Products redesigned

Customers migrated

Each step introduces dependencies, sequencing constraints and operational trade-offs.

These realities rarely appear clearly in the financial model.

Telecom mergers contain a hidden assumption: that the integration engineering program will succeed.

Preparation Determines Execution

Successful integrations rarely succeed through improvisation.

Speed in execution reflects preparation done much earlier.

Clear operating models

Standardised architectures

Defined integration playbooks

Dependencies mapped and owned

Programs do not fail because people stop trying.

They struggle when coordination replaces ownership.

Serious Terrain

Telecom integrations reshape operating models, supplier relationships, regulatory commitments and internal power structures simultaneously.

Network expansion programs, IT transformations and regulatory obligations are usually already underway. Integration must therefore be delivered while the organisation is already operating at full stretch.

Discomfort is inevitable. The real question is whether preparation matches ambition.

Protecting Value and Reputation

The most consequential risks rarely sit in headline commitments. They sit in the assumptions beneath them.

Leadership teams should identify which assumptions carry the greatest delivery risk – and show how those assumptions are being tested under real operational conditions.

At this scale a further question becomes unavoidable:

What independent scrutiny is stress-testing the assumptions embedded in the business case before commitments harden?

The strongest boards ask that question early – because they want the strategy to succeed.

About the author

David Hilliard is founder of Mentor, specialists in strategic program execution.

You can call him on 0118 359 2444 or email david.hilliard@mentoreurope.com.