How Go NoGo works

1. Think — what do we believe?

Start with the release position the team is currently relying on.

Go NoGo records the declared position before the actual evidence is used to confirm or challenge it.

• What the system is expected to do
• Which customer journeys matter
• What changes are being released
• What testing is believed to be complete
• What may still be assumed
• Who owns the position
• What happens if something goes wrong

This creates the baseline against which the release can be examined.

2. Know — what has actually been established?

The declared position is then compared with what has actually been observed.

This is where the difference between expectation and reality becomes visible.

• What was actually found
• Whether the declared position was verified
• Where expectation and observation differ
• Whether a material gap exists
• The likely impact of that gap
• Whether recovery is understood
• Whether remaining exposure has been accepted

Go NoGo does not improve the release position simply because the team expected something to be true. The established position must be supported by what was actually found.

3. Proof — what evidence supports it?

Findings become stronger when they are supported by current, traceable evidence.

Go NoGo links evidence to the release position so the basis for that position can be reviewed later rather than reconstructed from memory, tickets, dashboards and conversations.

• What evidence exists
• What the evidence actually demonstrates
• What remains unsupported
• Where evidence is incomplete or missing
• Where evidence contradicts the declared position
• Who owns the unresolved gap
• What would need to change before the position improves

Contradictions and missing evidence remain visible. Confidence is not treated as proof.

4. Decision — what release position does the evidence support?

Go NoGo applies transparent, deterministic rules to the established findings and evidence.

The software produces a release position and shows the reasons behind it.

• What is established
• What remains exposed
• Which gaps require attention
• Who owns the next action
• What recovery or mitigation exists
• Whether the release is ready for a decision

Same evidence in. Same position out.

Go NoGo supports the decision. The accountable person still makes it.

Where Tier 1 and Tier 2 fit

Inside the product, Tier 1 and Tier 2 provide the working structure behind the Think and Know stages.

• Tier 1 captures the declared release position: what the team currently believes to be true.
• Tier 2 establishes the actual position: what has been observed and demonstrated in reality.

Showing those positions side by side makes it immediately visible where belief and established fact agree, and where they do not.

Where BDD, testing and automation fit

Testing and automation contribute evidence. They are not the whole release decision.

A passing test can demonstrate that a particular check succeeded. It does not by itself establish that the right business outcome, customer journey, release candidate or assumption has been examined.

BDD helps make expected behaviour explicit. Testing and automation can then provide targeted evidence against that behaviour.

Sometimes the missing evidence is a test. Sometimes it is an unclear requirement, an unsupported assumption, missing ownership, weak recovery, poor traceability or a journey that has never been demonstrated end to end.

The purpose is to strengthen the evidence behind the release decision, not simply to generate more tests.

Why deterministic rules matter

Go NoGo does not ask an AI model to decide whether a release is safe.

The release position is produced from explicit rules applied to the evidence and established findings.

That means the position can be explained, challenged, repeated and audited.

AI may assist with bounded activities around the process, but it does not replace the deterministic decision logic.