How the Diagnostic works

1. Choose the critical journey

Start with the customer journey that matters most to the release.

That might be a payment flow, customer onboarding, a regulated process, a critical operational workflow, or any journey where failure would have a meaningful consequence.

• The journey being released or changed
• Why it matters
• The consequence if it fails
• Who is accountable for the release decision

2. Record the position being relied on

Before looking at what has actually happened, capture the position the team currently believes to be true.

This creates the baseline for the assessment.

• What the system is expected to do
• What evidence supports that position
• What is still assumed
• Where evidence is incomplete or missing
• Who owns the position or gap

This becomes the declared position for the journey.

3. Examine what has actually been demonstrated

The Diagnostic then compares the declared position with the evidence available.

This is where the difference between expectation and demonstrated behaviour becomes visible.

• What was actually observed
• Whether the declared position was verified
• Where a gap exists
• The impact of that gap
• Whether recovery is understood
• Whether the remaining risk has been accepted

4. Make gaps, ownership and recovery explicit

A release does not need every uncertainty to disappear.

It does need the remaining uncertainty to be visible and understood.

Go NoGo brings the unresolved parts of the release into one place so they do not remain scattered across tickets, dashboards, test reports and conversations.

• What is supported by evidence
• What remains assumed
• What is missing
• Where expectation and observed behaviour differ
• Who owns the next action
• What recovery or mitigation exists
• What needs to change before the position improves

5. See the release position

Go NoGo applies transparent, rules-based logic to the information captured in the Diagnostic.

The software shows the strength of the current release position and the reasons behind it.

That gives the person accountable for the release a clearer basis for deciding whether to:

• Proceed
• Resolve a material gap
• Strengthen weak evidence
• Add recovery or mitigation
• Accept a known risk
• Carry out further targeted validation

The software supports the decision. The decision remains human.

What the Diagnostic brings together

Each assessment keeps the release information connected around the customer journey being examined.

• Intended behaviour
• Evidence
• Assumptions
• Observed findings
• Gaps
• Ownership
• Recovery and mitigation
• Remaining exposure
• The current release position

Where BDD, testing and automation fit

Testing and automation are part of the evidence, not the whole assessment.

A passing test can prove that a particular check succeeded. It does not automatically prove that the right journey, business consequence or release assumption has been examined.

BDD scenarios can make the expected behaviour of the journey explicit. Targeted testing and automation can then be used where additional evidence is needed.

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

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