Unblocking delivery across parallel programmes

Context

The organisation was running two digital programmes in parallel. On paper they had separate scopes, separate teams, and separate decisions to make.

In practice, the dependencies sat directly inside each other's work. Progress in one programme often required a choice that could only be made in the other.

The problem

The main issues identified were:

The programmes had overlapping decision points but no shared structure for resolving them
Leadership wanted cleaner separation than the actual systems and teams could support
Teams were waiting for certainty before moving, which turned dependency into delay

The organisation did not have a clarity problem. It had a sequencing problem.

The useful move was not cleaner separation. It was a sequence that let both sides move before the whole system felt solved.

My contribution

My role included:

Mapping where the dependencies were genuinely load-bearing and where they were administrative noise
Working with both programmes to identify decisions that could be made independently
Creating a sequencing model that let each team move without pretending the overlap had disappeared

Outcome

The work resulted in:

A shared view of which dependencies mattered and which did not
Fewer blocked decisions between the programmes
Both programmes returning to delivery after months of stalled progress

We worked with the dependency pattern that existed instead of wasting time designing one that would never exist.

Reflection

The instinct in situations like this is usually to redraw the structure until it looks rational.

That would have wasted time here. The useful move was to work with the dependency pattern that actually existed and build a delivery rhythm around it.