The Gap Is Opening Now: Why Parallel Execution Is a Structural Problem

Look at the market signals we mapped last quarter alongside the live implementations now visible across the sector, and a pattern becomes clear. Mortgage Lenders aren’t waiting to finish internal transformation before engaging with the ecosystem, they’re doing both at the same time. Pilots are now live, industry infrastructure including Smart Data and tokenisation is in implementation. The participation in neutral infrastructure and shared standards is active. Internal coherence and external interoperability are running in parallel.

The trajectory is leveraging digital completion infrastructure, partnering with property marketplaces to engage earlier in the property journey and investing in infrastructure collaborations, alongside focused transformation of internal points of friction within the mortgage journey.

A cohort of UK lenders are already operating across both axes of Horizontal Digital Integration, doing the internal and external work at the same time. The question is: why can’t most lenders do the same? The answer is structure.

The Sequencing Instinct

Last month, we explored that HDI operates across two axes: internal, where lenders organise themselves for end-to-end journey coherence, and external, where they connect and interoperate with the participants around them in the property transaction. We argued that these two dimensions are inseparable.

That argument still holds. But there is a follow-up question we did not fully address: if internal and external are inseparable, why does almost every lender treat them as sequential?

The default posture across the market is to prioritise internal transformation first. Get the operating model right. Fix the data definitions. Build the journey teams. Then, once the foundations are in place, turn outward to ecosystem engagement, partner strategy and interoperability standards.

It sounds rational. It feels disciplined. But the ecosystem is not waiting for anyone’s internal programme to finish.

The regulatory and infrastructure trajectory we mapped in our market signals update is creating a competitive divergence right now. Lenders who are structured for parallel execution are already in the room, shaping standards, building institutional knowledge, developing the operational habits for interoperability. Lenders who are sequencing internal-then-external are falling behind.

The deeper problem is that the sequencing instinct is a structural symptom. The way most lenders are organised makes parallel execution difficult by default, and the result is that internal-first feels like the only responsible path. Three things create this problem.

The scope problem

Most lenders have Journey Managers or Product Owners who own the mortgage journey end to end. This is genuine, meaningful work to optimise handoffs between origination and underwriting, reduce cycle times, improve case management, and drive toward faster and more consistent outcomes.

But the journey they own is the lender’s mortgage process, not the customer’s property transaction.

The customer’s journey starts when they decide to move and ends when they have keys. The mortgage is one part of that full transaction. The estate agent, the conveyancer, the valuer, the broker, the search provider are all participants in the same journey. The work inside a lender to design for how the organisation’s contribution connects to what happens before it and after it is rarely owned clearly by anyone.

This matters because the ecosystem infrastructure being built now is organised around the customer’s transaction, not the mortgage process alone. NPTN, PEXA, the frameworks emerging from OPDA, CFIT and the FCA: all of these are designed for data and evidence that travel with the transaction across organisational boundaries. A Journey Manager whose scope stops at the lender’s boundary can optimise internally but cannot design for how the organisation participates in the wider journey. And participation is where the direction is unfolding.

The business case problem

Internal transformation and ecosystem participation are typically evaluated as separate investments with separate business cases. The internal case is built around operational efficiency, speed to offer, cost reduction. It is quantifiable, near-term, and speaks the language of the annual planning cycle.

The ecosystem case is harder. The returns depend on partner readiness, market adoption and regulatory timelines. They are longer-horizon and more contingent. In any prioritisation exercise, the internal case wins because it is more legible to the people making the decisions.

Ecosystem work rarely gets rejected outright. It gets deferred. It sits in the backlog behind more quantifiable internal initiatives, not because anyone has decided it is unimportant, but because the business case structure systematically disadvantages work whose value depends on what happens beyond the organisation’s walls.

The planning cycle mismatch

Internal transformation runs on programme cycles: 12 to 18 months, with milestones, gates and defined scope. Ecosystem participation requires something different. It is ongoing, adaptive engagement with external partners, standards bodies and regulatory developments that do not conform to internal planning timescales.

Most lenders try to force ecosystem work into programme structures. The effect is either to slow it down, because every engagement needs to be scoped and business-cased before it can begin, or to strip out the adaptiveness that makes it valuable, because the programme needs fixed deliverables and measurable outcomes on a quarterly cadence.

These three things together are what make sequential execution feel rational. Internal first, external later is the default output of a structure that separates the two. The operating model creates the sequencing instinct.

Designing in Two Directions

If the operating model creates the sequencing problem, then the operating model is what needs to change. The practical question is what that change looks like.

Journey Managers and Product Owners already design the mortgage journey internally. The change is that they also need to design outward: how the lender’s part of the journey connects to the ecosystem around it. The scope of the role extends. The number of roles does not necessarily need to.

In practice, this means the same team that is redesigning an internal workflow is also asking a different set of questions. What data do we need to receive, and in what format? What do we pass on, and to whom? Where do our processes create friction for the customer because we are not aligned with what happened before us or what happens after us? What ecosystem standards do we need to build to? If we change this process internally, does it break or enable an external integration point?

This is what parallel execution looks like when it is working. One team designing in two directions simultaneously. Internal optimisation and ecosystem participation become two outputs of the same way of working, not two workstreams competing for the same resources.

The business case problem resolves itself when the work is unified. You do not need a separate case for ecosystem participation when it is embedded in the same journey design work that is already funded. The planning cycle problem eases when ecosystem engagement is a continuous dimension of how journey teams operate, rather than a separate initiative that needs its own programme structure.

Chris’s article makes an important point about neutral infrastructure: that scalable change requires shared rails that allow data to move securely between participants without locking customers into closed ecosystems. He is right. But the corollary for every lender reading this is that connecting to neutral infrastructure requires an internal operating model that is designed for connection. A lender whose journey teams are scoped to the organisation’s own walls, whose business cases are built around internal returns, and whose planning cycles cannot accommodate adaptive external engagement, will struggle to plug into that infrastructure however willing it may be in principle.

The Competitive Divergence

The evidence in our market signals update describes a gap that is opening in real time.

The lenders engaged in the partnerships and standards work shaping the emerging ecosystem are building institutional knowledge and partner relationships that will compound over time. They are learning what interoperability actually requires in practice and discovering where their internal definitions and processes need to adapt. That learning only happens by doing it, and it cannot be compressed into a catch-up programme later.

The lenders still waiting for internal transformation to finish, or for the ecosystem to mature further, are making a bet that they can close the gap when the time is right. That bet looks increasingly expensive. Becoming ecosystem-ready is a structural and cultural shift that takes time to build, and the building has to start before the infrastructure is fully formed.

We have spent much of the past year arguing that the UK mortgage market has reached a level of digital maturity but remains systemically stuck. The evidence continues to support that diagnosis. What has changed is that the pathway is now visible, and some lenders are already walking it.

The question for every lender is whether your organisation is structured to meet the ecosystem as it arrives. The answer sits in your operating model.