A decision should preserve its evidence

Organisations usually preserve the outcome of important decisions.

They do not always preserve the decision itself.

Six months later, it may be easy to discover that a drilling programme was approved, a target was deprioritised or another tranche of capital was released.

It can be much harder to reconstruct why.

The reasoning may be spread across presentation decks, spreadsheets, emails, meeting minutes, geological interpretations and the memories of people who were in the room.

That creates a problem whenever the decision needs to be reviewed later.

A decision is a position taken on available evidence

A useful decision record should preserve more than:

Approved / Rejected

It should preserve the context:

• What was the hypothesis?
• What evidence existed?
• What evidence was missing?
• Which assumptions were material?
• What risks were known?
• What alternatives were considered?
• What was expected to happen next?
• What new information was the decision intended to generate?

That creates a structure like:

Hypothesis → Evidence → Assumptions → Alternatives → Decision → Expected learning

The sequence is particularly important in uncertain environments because decisions that later look wrong may have been entirely reasonable based on the evidence available at the time.

Conversely, a decision that happened to produce a good outcome may still have been poorly founded.

Hindsight changes the story

Human memory is very good at making the past look more obvious than it was.

After a successful drilling campaign, the geological interpretation can begin to look inevitable.

After a failed campaign, warning signs that were ambiguous at the time can appear obvious in retrospect.

Preserving the original evidence and reasoning protects against that distortion.

It lets a later reviewer ask:

Given what we knew then, was the decision reasonable?

That is a much fairer governance question than:

Did the decision eventually produce the desired result?

Decision gates should not become administrative checkpoints

Stage gates are often introduced to improve governance.

But they can become procedural.

A gate is held.

A paper is circulated.

A decision is recorded.

The organisation moves on.

The useful question is not whether the meeting occurred.

It is whether the gate made the underlying assumptions and evidence explicit enough to support a real decision.

For exploration, that may include:

• technical criteria,
• data quality,
• licence status,
• programme cost,
• funding availability,
• material risks,
• evidence quality,
• and remaining uncertainty.

The gate is valuable because it forces the organisation to state its position at a particular point in time.

Evidence should remain traceable

A material claim should be able to point back to its evidence.

For example:

North Ridge confidence has strengthened.

Why?

Perhaps because:

• a new drill intersection supports continuity,
• an updated geophysical model aligns with the structural interpretation,
• and geochemistry extends the anomaly.

If those links are preserved, the statement is auditable.

If they are not, “confidence strengthened” becomes another management assertion.

The same principle applies outside exploration.

A maintenance strategy, safety decision, shipping exception or infrastructure priority is easier to govern when the evidence chain is visible.

The next decision depends on the previous one

Decision history also matters because operational decisions are rarely isolated.

A first decision may approve data collection.

The second approves field validation.

The third approves drilling.

The fourth expands the programme.

The fifth stops it.

Each decision changes the information available to the next one.

If those decisions remain connected, the organisation accumulates a coherent history of how its view changed.

If they are stored as unrelated approvals, the learning is fragmented.

Evidence preservation is not bureaucracy

There is always a risk that governance becomes a burden.

The answer is not to capture everything.

It is to preserve the information that would matter if someone later asked:

Why did we do this?

For a material decision, a concise record of hypothesis, evidence, assumptions, alternatives, risks and expected learning may be far more useful than pages of meeting notes.

The objective is not documentation for its own sake.

It is continuity of reasoning.

Once we start preserving that reasoning, another architectural question appears.

Should every part of the operating environment live inside one large application simply because the decisions are related?

Or are some questions better handled by specialised systems that share meaning without sharing everything else?