The Data Modernisation Pressure Point

The Pressure Point of Data Modernisation

You’ve convinced the stakeholders. The business case is approved. The programme is agreed. The backlog is sized. Dates are committed.

The outgoing system is old, but it is known. Everyone believes the scope is understood. The modernisation is underway.

Feel familiar?

At the start of a data migration, the problem feels finite. The platform may be ageing, but its boundaries appear clear. We believe we are replacing something we understand.

The Unwinding Begins 

Discovery begins in earnest. Workshops and documentation reviews help, but nothing is as revealing as dismantling the legacy system itself. It is like pulling at a loose thread.

You uncover:

• Business logic embedded in stored procedures

• Nested transformations buried in legacy ETL

• Calculations inside semantic layers

• Manual Excel adjustments no one documented

• Data quality issues absorbed downstream

• Operational processes quietly running inside the warehouse that only one person fully understood

The backlog grows.

At this stage, it still feels manageable. It feels like refinement.

The Pressure Point

Discovery shows no sign of slowing. In fact, it accelerates. New work is identified faster than work can be closed.

Burn-up charts flatten. The gap between completed work and total scope widens. Velocity appears inconsistent. Confidence erodes. Previously agreed end dates begin to look unachievable.

This is when leadership anxiety appears. Questions follow:

• Did we underestimate?

• Was the scope wrong?

• Do we have the wrong team?

• Are we losing control?

In reality, this is predictable. There is always a phase in serious data migrations where discovery outpaces delivery.

This is not classic scope creep. No one is asking for new features.

You are uncovering accumulated complexity:

• Years of technical debt

• Hidden dependencies

• Implicit assumptions

The backlog is not expanding because the team is careless.

It is expanding because the organisation is finally seeing its system clearly.

This is the pressure point.

Why This Happens

Legacy data platforms evolve organically:

• Patches layered on patches

• Logic duplicated in multiple places

• Temporary fixes becoming permanent

• Reporting adjusted to compensate for upstream flaws

Documentation rarely reflects reality.

When you modernise, you disturb the sediment. Everything that was hidden becomes visible.

The critical distinction is this:

This is structural complexity surfacing, not uncontrolled scope growth.

Without that reframing, the narrative becomes “the project is failing.”

With it, the narrative becomes “we are seeing the truth.”

The Inflection Point

This phase does not last forever.

Eventually, something changes.

Patterns emerge.

• Issues stop being unique

• Reusable approaches form

• Migration templates stabilise

• Engineers become more proficient

• Discovery slows

Delivery begins to outpace uncovering.

The backlog peaks. Then it begins to fall.

The project moves from archaeology to engineering.

The pressure releases.

The Leadership Lesson

Every serious data modernisation contains this moment.

The mistake is not hitting the pressure point.

The mistake is being surprised by it.

Experienced leaders:

• Expect the backlog to grow before it shrinks

• Separate structural discovery from true scope change

• Protect teams from panic rebaselining

• Communicate uncertainty honestly

If your backlog is growing mid-modernisation, it may not be failure.

It may be the first honest view of the system you are replacing.