Where value goes to die: Understanding the hidden gaps in transformation delivery

Sadie B. Okiji, Founder and CEO, ABPMX and PRINCE2 Ambassador

In her recent Flowtopia 2026 talk, Sadie B. Okiji, Founder and CEO of ABPMX and PRINCE2 Ambassador, argued that the biggest barrier is a lack of clarity about what value is, where it is created, and how it flows through the organization. Rather than disappearing altogether, value often becomes slower, diluted or disconnected as work moves through increasingly complex organizational systems. Somewhere between planning, governance, delivery and implementation, the original intent begins to fade.

A key reason for this disconnect is that organizations often mistake activity for value. Teams can be highly productive, deliver projects on time, and meet governance requirements, yet still fail to achieve the outcomes that matter most. rogress is too often measured by the work being completed rather than the value being created. As Sadie explained, understanding that distinction is essential because it helps reveal where value begins to diverge from the original intent.

Recognizing the difference between activity and value also helps organizations identify where value begins to break down. These points of disconnect typically emerge in three areas. Understanding where these gaps occur is becoming just as important as understanding how projects are delivered because recognizing them helps organizations preserve not only the outputs of transformation, but also the purpose behind them.

One of the first areas where value begins to drift is during the hand-off between teams. Complex change initiatives rarely transition directly from project initiation to the end user; instead, they pass through multiple delivery teams, technical specialists, governance groups, and operational functions. Documents, technical builds and decisions are passed from one team to the next.

While these outputs move successfully through the organization, the original intent often does not. Questions such as “Why are we doing this? Who is this for? What will actually change when the work is complete?” can gradually become less visible as work progresses, even though every team continues to deliver its part of the programme.

No one has necessarily done anything wrong; the system simply was not designed to carry meaning across organizational boundaries. Each hand-off acts like a compression; what gets compressed first is the “why”. By the time delivery reaches the end user, much of the context that informed the original business case has been lost.

A useful indicator of this issue is how easily teams can explain the work they are delivering. If a project cannot be described in simple terms, it often indicates a deeper problem with understanding its purpose. Similarly, if teams can explain what they are delivering but not who will benefit or what difference it will make, the programme may already be entering a stage where the hand-off gap exists. Keeping intent visible throughout delivery helps preserve the connection between project activity and the value it is intended to create.

The governance gap: When reporting replaces reality

Governance presents a different challenge. Over time, governance structures designed to provide assurance can become performance structures, where teams feel pressure to demonstrate success rather than openly discuss uncertainty. Many project professionals recognize the feeling of presenting a highlight report in which every RAG (red, amber, green) status is expected to be green, even when conversations outside the meeting tell a different story. The difference between those two conversations is where the governance gap begins to emerge.

Structured project management provides more than a delivery process. It gives practitioners the confidence to ask better questions, surface emerging risks and understand why governance exists in the first place. Good governance should reveal reality rather than obscure it. Honest reporting enables organizations to respond earlier, make better decisions and maintain trust throughout delivery.

The experience gap: Looking beyond go-live

The final gap is often the most subtle, yet it can have the greatest impact. Organizations frequently celebrate the successful implementation of projects and programmes. They mark the completion of milestones and the go-live of systems. From a delivery perspective, the project has been completed successfully. The more important question comes after go-live: Has anyone’s life actually changed?

A system may be functioning exactly as intended, but that does not necessarily mean life has improved for the people it was built to serve. Measuring success at go-live risks overlooking what matters most: whether the change has improved life for the end-user - the employee, customer, or citizen who ultimately benefits from the outcome.

Every organization will measure this differently, but the principle remains the same. Value is not confirmed simply because a system has been deployed; it becomes evident when people begin to experience the benefits the programme was designed to create.

Three shifts leaders can make today

Recognizing these gaps is only the first step. The next is leaders deciding what they can do differently. The first shift is to make value visible from the beginning. Instead of asking “What are we delivering?”, start by asking “What will change for the person at the end?” Establishing that shared understanding early on will help maintain intent throughout the delivery.

The second shift is to design governance around truth rather than comfort. Truth creates a stronger foundation for decision-making than reassuring reports that fail to reflect reality. The third shift is to stay curious after go-live. Continue asking whether change is actually landing, how people are experiencing it, and what impact it is having over time.

Closing the gaps

Project and programme management methods provide the structure needed to manage complexity, but realizing value requires something more fundamental. Organizations must keep sight of the original purpose behind their work.

The hand-off gap shows how intent can become compressed as work moves between teams. The governance gap reminds us that truth matters more than appearance. And the experience gap demonstrates that implementation is only the beginning of understanding whether value has been realized.

None of these gaps is inevitable. All of them can be addressed, but only if leaders know where to look and recognize the warning signs before value begins to drift. Perhaps the most important question is also the simplest: What is actually different for the people this project/programme was intended to serve?