For Programme Directors, CEOs, and Programme Sponsors
Up to 80% of programme defects originate in requirements and decision-making — not delivery. The decision that will cost your programme $80 million is probably already made. It was made in a requirements meeting, or a design review, or a procurement approval, by someone who had good intentions but incomplete evidence. When the consequences surface — at the gate review, at the inquiry, at the Parliamentary committee — the decision cannot be found. Not because it was hidden. Because the tools your programme uses were never designed to hold it.
The decision that will cost you $80 million is probably already made
You will not find out for another three years.
It was made in a requirements meeting, or a design review, or a contract approval. It was made by someone who had good intentions, good credentials, and the information available to them at the time. It was not a bad decision by any reasonable standard. It was an undocumented one.
When the consequences surface — at the gate review, at the inquiry, at the Parliamentary committee — the decision cannot be traced. Not because it was hidden. Because the tools your programme uses were never designed to hold it.
The requirements are in Jira. The architecture is in DOORs. The cost estimate is scattered across a spreadsheet and buried in Sharepoint folders. Email threads and Teams chat hold procurement approvals. The decision that connected all three exists in a slide deck from a meeting three years ago that nobody can find.
This is not a management problem. It is a structural one. And it is the root cause of more programme failures than any other single factor.
The problem is not complexity. It is fragmentation — and no existing vendor solves it.
Every year, the nations managing the most complex programmes in the world — defence acquisitions, nuclear infrastructure, critical national programmes — spend hundreds of billions of dollars on tools, processes, governance frameworks, and oversight mechanisms. And every year, major programmes in those same nations exceed their budgets by 30 to 60 per cent, slip their schedules by years, and deliver less than their sponsors committed to.
The standard diagnosis is complexity. The actual diagnosis is decision drift.
Decision drift occurs when the original intent of a programme — the requirements it was meant to satisfy, the constraints it was meant to respect, the options that were considered and rejected — becomes disconnected from the decisions that are being made in the present. When today’s decisions cannot be connected to yesterday’s evidence, the programme is navigating without a map.
The consequences are measurable:
- Up to 80 per cent of programme defects originate in requirements and decision-making — not in delivery.
- Rework consumes between 20 and 35 per cent of major programme budgets.
- The cost of correcting a decision error discovered in delivery is 30 to 100 times the cost of catching it at the requirements stage.
- One in every six major programmes becomes what analysts call a black swan event — budget overrun exceeding 200 per cent, schedule overrun exceeding 70 per cent.
These are not the consequences of incompetent teams. They are the consequences of a structural gap: no tool in the standard programme stack was designed to make decisions traceable.
What your tools were built to do — and what they were not built to do
The tools that manage most large programmes today were built between the 1980s and the 2000s. They were built to manage data and information: requirements documents, design files, bill-of-materials records, procurement orders, change notices. They do this well.
None of them were built to manage decisions.
Your requirements management system holds the requirements. It does not hold the decision about which requirement interpretation was selected when two stakeholders disagreed, the evidence that resolved the disagreement, and the authority that signed off on the resolution.
Your product lifecycle management system (Solidworks, Teamcenter, Windchill) holds the design. Your ERP (SAP, Oracle) holds the procurement. Your requirements management tool (Jira, DOORs) holds the specifications. Decision threads live in email, Teams chat, Sharepoint folders, and meeting minutes that referenced them. None of them hold the decision about which design option was selected, the options that were rejected, the criteria used to select between them, and the risks accepted in making the choice.
The decision — the act of choosing, the evidence that supported the choice, the reasoning that connected evidence to conclusion — lives between the tools. It lives in someone’s head, in a meeting minute in a folder no one maintains, in an email chain that disappeared when the programme manager moved to a different role.
The reconciliation spreadsheet is not a symptom of poor programme management. It is the consequence of a tool ecosystem that was never designed to hold decisions. The spreadsheet exists because someone has to bridge the gap between the system that holds the requirements and the system that holds the design and the system that holds the cost. The bridge is the decision. The spreadsheet is the only place it lives.
Clarity is the infrastructure that replaces the spreadsheet — not with a better spreadsheet, but with a programme model where every decision is a first-class object, held with its evidence chain, its authority, its options considered and rejected, and its full traceability to every artefact it touched.
Three programmes, one structural problem
Decision drift manifests differently across programme types. The three archetypes below cover the most common patterns. Every programme director will recognise their programme in at least one of them.
Archetype 1 — The inherited decision
Programme type: Major defence acquisition with alliance or political constraints
The defining characteristic of this programme type is that the most important decision was made before the programme formally existed.
A political agreement commits the nation to a capability. A ministerial directive mandates a platform selection. An alliance obligation imposes a technical standard. In each case, the decision that sets the programme’s fundamental parameters — what is being built, to what specification, by when, with whom — was made at a level above the programme, by people who had strategic authority but not engineering accountability.
The programme inherits the decision. It does not inherit the evidence that would have justified it.
What the programme team typically receives is: a mandate, a timeline, a set of political commitments, and a set of contractual obligations with partner nations. What it does not receive is: the options that were considered before the mandate was issued, the criteria against which those options were evaluated, the risks that were accepted in selecting the mandated path, or the conditions under which the commitment could be revisited.
The programme begins at the point where the decision has already constrained the solution space, without the evidence chain that would allow the programme to understand how constrained that space actually is.
The consequences unfold predictably. The engineering team begins working within the mandated parameters, discovering as they proceed that the constraints are more severe than the mandate indicated. Requirements that were assumed to be satisfiable within the mandated platform turn out to require significant deviation from the baseline. The deviation requires a change to the baseline. The change requires evidence that the original baseline was correctly specified. That evidence does not exist.
Every change is contested. Every escalation requires a decision authority that can only say what was intended, not what was evidenced. The programme accumulates ambiguity faster than it resolves it.
This is not a failure of the programme team. The programme was handed an untraceable decision and asked to deliver against it.
Decision accountability infrastructure changes this at the point of inheritance. The first act is to build the evidence chain retrospectively: documenting the inherited constraints, the options the mandate foreclosed, the assumptions embedded in the political commitment, and the conditions under which the mandate would require revisiting. This is not revision of history. It is the creation of the programme’s baseline — the explicit record of what is known, what is assumed, and what is accepted risk.
With that baseline, every subsequent decision is traceable to the original constraint. Every change is evaluated against the evidence that justified the constraint it is asking to modify. The programme navigates with a map rather than from memory.
Archetype 2 — The 30-year accountability challenge
Programme type: Long-lifecycle programme with through-life obligations (nuclear, submarine, critical infrastructure)
The defining characteristic of this programme type is that the decisions made today must be defensible to people who do not yet exist, in forums that have not yet convened, under standards that have not yet been written.
A nuclear facility designed in 2026 will be operated for 60 years and decommissioned over the following 20. The engineers who designed the containment structure will have retired before the first decommissioning decision is made. The regulatory framework under which decommissioning will be governed does not yet exist. The organisation that will manage the programme in 2080 may not have the same name as the organisation managing it today.
The question that every long-lifecycle programme director must be able to answer — for a regulator, for an inquiry, for a successor programme team — is: why was this decision made?
Not what was decided. Why. With what evidence. Against what alternatives. With what risk accepted. Under what conditions would the decision have been made differently.
In most programmes, this question is unanswerable after five years. The team has changed. The documents are in systems that have been decommissioned. The meeting minutes reference analyses that are in someone’s personal archive. The decision exists in the programme’s history as an outcome — a design choice, a procurement commitment, a safety basis — with no traceable path back to the reasoning that produced it.
This is not a records management failure. It is an infrastructure failure. The programme was never given the tools to hold the reasoning, only the results.
Long-lifecycle programmes also face a compounding accountability challenge at the implementation level. A decision made at the design stage about a containment approach, a structural material, or a safety system will generate consequences at every subsequent stage of the programme’s life: at construction, at commissioning, at first operation, at every inspection, at every life extension assessment, and ultimately at decommissioning.
Without a traceable decision chain, every life extension assessment begins from scratch. Every decommissioning decision is made without the benefit of the original design reasoning. Every incident investigation must reconstruct the original intent before it can determine whether a deviation from that intent caused the problem.
Decision accountability infrastructure for long-lifecycle programmes means that the 30-year answer is built into the programme record from the first decision. Not because someone will remember. Because the record was constructed to survive the loss of everyone who was present.
Archetype 3 — The structured evidence bid
Programme type: Tier 2–4 defence supplier competing for a contract requiring structured evidence
The defining characteristic of this programme type is that decision accountability is a procurement prerequisite, not a programme management choice.
Defence prime contractors and government programme offices increasingly require their supply chain to deliver structured, traceable evidence packs rather than unverifiable document collections. A tender response that cannot demonstrate traceability from requirement to design to option selection to risk acceptance is a tender response that will not succeed.
For a 30-engineer engineering firm competing for a £5 million defence contract, the cost of assembling a compliant evidence pack through traditional means — hiring MBSE consultants, operating specialist tooling, maintaining dedicated compliance documentation — often exceeds the profit margin on the contract. Many firms do not bid. Those that do absorb costs that make the work uneconomic.
The structural problem is that the evidence for a compliant bid is not generated by programme work — it is assembled after programme work has been done, by a process that is parallel to the engineering rather than integral to it. The team builds something, then documents what they built. The documentation process is expensive, slow, and produces evidence that cannot be independently verified against the programme record.
When decision accountability is built into the programme from the first decision, the evidence pack is a by-product of the work rather than a separate activity. Every option considered is already documented with its evidence. Every decision is already traceable to its requirements. The bid submission is a report generated from the live programme record — not a documentation effort that happens after the engineering is complete.
This changes the economics of participation. The cost of producing a compliant evidence pack falls from weeks of consultant time to hours of report generation. The quality of the evidence pack rises from a document collection to a structured, independently verifiable decision chain. The competitive advantage is structural.
What decision accountability looks like in practice
A programme with decision accountability infrastructure looks different at every gate — to the programme team, to the programme sponsor, and to every external party that has oversight of the programme.
At the gate review, the evidence for every committed decision is present in the programme record, not assembled in the week before the review. Every option considered is documented with the reasoning for its rejection. Every assumption is tagged and traceable to the evidence that supported it when it was made. Every risk accepted is recorded with the confidence level that existed at the time of acceptance.
The gate review is a review of decisions made, not a reconstruction of decisions that cannot be found. It is shorter, it surfaces real issues rather than documentation gaps, and it produces decisions rather than actions to close documentation.
When the programme changes, the consequences of the change are visible across the decision graph before anyone commits to it. Not estimated — visible. The options that the original decision foreclosed are on record. The assumptions that the change invalidates are identified. The risks that the change introduces into decisions already made are traced to the point where they enter the evidence chain.
When an external party arrives — a regulator, an alliance partner, a prime contractor, an inquiry — the evidence chain is generated from the live programme record. The programme does not prepare for the audit. It is already audit-ready.
Mission Control for your programme
The model that decision accountability infrastructure creates is Mission Control.
In Mission Control, every function has a structured view of the same programme. Every decision is recorded when it is made, with the evidence available at that moment. Every deviation from expected behaviour is visible to everyone with authority to respond to it. The programme is always navigable — not by the people who have been there from the beginning, but by anyone who can read the record.
This is what Clarity delivers for complex programmes.
Every decision in a Clarity programme carries a live evidence score — the DeZolve Truth Vector — computed at the time the decision is made from the evidence that exists in the programme record at that moment. The evidence chain is structurally immutable. It cannot be altered retroactively. It can be independently audited by any authorised party without Clarity’s continued operation.
Every organisational function — engineering, finance, risk, regulatory compliance, supply chain, security — has a structured view of the same underlying programme model, at the lifecycle stage where that function operates. Not a report exported from someone else’s system. Not last week’s snapshot. The same programme, their layer, in real time.
No tool is decommissioned. No data is migrated. Clarity sits above your existing systems as the connected intelligence layer. Your requirements management system, your product lifecycle management, your ERP — they keep doing what they do. Clarity builds the decision intelligence layer above them.
The 30-year answer
Every programme director faces a version of this question eventually.
If I am not here in 30 years, can the decision I made today be defended by someone who has never met me, using only the record I left behind?
For most programme directors, working with the tools available today, the honest answer is no.
With decision accountability infrastructure, the answer is yes.
The decision record is structured, immutable, and independently auditable. The evidence chain is live, connected to the programme data that substantiated the decision. The options considered are on record. The risks accepted are documented with the level of confidence that existed at the time of acceptance.
The inquiry can come at any time. The answer is always the same: here is the decision, here is the evidence, here is who made it, and here is what they knew when they made it.
Where to begin
The right time to establish decision accountability infrastructure is before the first gate review.
The decisions made in the first 18 months of any programme determine its cost and schedule performance across its entire lifecycle. Establishing the evidence chain at the point those decisions are made — not reconstructing it after they have propagated through subsequent phases — is the only approach that captures the full value.
That said, entry is possible at any point in the programme lifecycle. If your programme has existing requirements in a management tool, designs in a product lifecycle management system, and costs in an ERP, Clarity connects them. The evidence chain begins from the point of deployment forward.
Decision accountability infrastructure is not a transformation. It is the layer that connects the work your team is already doing, makes every decision they make traceable and defensible, and gives every function a structured view of the programme they are jointly managing.
“Instead of asking people what happened, you’ll be able to see it. That’s the difference between managing information and managing certainty.”