TIT programs exceeding $15 million run 45% over budget, 7% over schedule, and deliver 56% less value than predicted, according to McKinsey and the University of Oxford who have studied more than 5,400 projects. These numbers are cited often in boardrooms and bid documents. What is cited less often is why.

The program leaders who deliver consistently and under pressure do so because they make one governance decision differently from the start. They decide who owns what. Not on paper. In practice.

When structure is not enough
Last year, we were asked to engage in a €5–10M IT transformation that a leading prime contractor led in Europe. The program was well-structured: clear workstreams, defined delivery responsibilities, and experienced teams. On paper, everything looked great. As delivery accelerated, something predictable happened. Workstream leads, each operating rationally within their own scope, began making local architectural and delivery decisions to stay on schedule. Individually, each decision was sound. At program level, they began to collide. Integration risk accumulated, compliance exposure grew, and accreditation dependencies that crossed workstream boundaries had no single owner. The program hadn’t lost control, but the conditions under which it could lose control had been quietly assembling for weeks. This is the pattern that experienced leaders in regulated environments learn to read early. Not as a sign of failure, but as the inevitable test that every ambitious program will face. The question is never whether complexity will arrive. The question is whether your governance architecture is designed to hold when it does.

What governance actually is
The word governance has been absorbed by program management and drained of its meaning. It has become shorthand for documentation, reporting cycles, and steering committee agendas. That is not governance. That is administration. Governance, in the sense of determining whether a program delivers, is the continuous alignment among three things: what leadership intends, what the delivery structure is designed to execute, and what is actually happening on the ground. When those three things are aligned, programs absorb complexity without losing momentum. Leaders who operate at the highest level in regulated environments don’t wait for a surface report that alignment is under pressure. They build governance structures that surface it early.

The three governance decisions that define delivery
Leaders who consistently deliver at this level share one discipline that most program frameworks never explicitly require: they treat alignment as a live condition, not a baseline assumption. In practice, this comes down to three decisions.

The first is making decision authority explicit at every level, not inferred from titles or org charts. Every person in the delivery structure knows precisely which decisions they can make, which they must escalate, and who owns the escalation path. This is a governance structure designed to function under operational pressure, not merely to satisfy a program initiation document.

The second is governing dependencies, not just tracking them. A dependency on a Gantt chart is a fact. A governed dependency has an owner, a resolution timeline, and an escalation trigger. The difference between the two is a leader who sees the full picture and one who is working from an incomplete one. In a multi-vendor, security-constrained environment, that difference is rarely recoverable once it surfaces.

The third is maintaining accountability through presence, not reporting. The governance discipline that holds in high-security, institutionally complex environments is not produced by frameworks or dashboards. It is produced by embedded leadership: people inside the program structure, close enough to the reality of delivery to see where alignment is beginning to drift before any report reflects it. In the defense transformation above, that presence is what allowed the prime contractor to maintain full accountability and ownership.

Why the stakes are different in defense program delivery
In commercial delivery, a governance gap is a financial and reputational event. In defence, justice, and EU-regulated environments, the consequences extend into territory that a budget adjustment cannot reach. Operational readiness, institutional credibility, and the strategic commitments to partners and allies that depend on systems performing as promised. These are not KPIs. They are the actual stakes of delivery in the environments where the most ambitious program leaders operate. Leaders who understand this don’t approach governance as a compliance exercise. They approach it as the core discipline that makes ambitious delivery possible; the architecture that creates the conditions for everything else to perform. They build it in from day one and maintain it when complexity peaks. They treat every drift in alignment, however early or small, as the signal it actually is.

How impactful leaders in defense programs ensure successful delivery by actively “owning governance,” which means continuously aligning leadership intent, delivery structure, and the reality of execution through three key decisions.