03 · Runs

Runs

Conduct acceptance sessions as controlled observation, with visible progress, clean evidence, and disciplined retest.

03 / Acceptance cycle

BriefOrient testers to purpose, data, access, and escalation.
ObserveCapture outcomes without coaching away genuine friction.
TriageRoute uncertainty and defects while context is fresh.
RetestVerify the fix and the affected business journey.

The session

Run a room, not a spreadsheet.

UAT execution needs facilitation. Give participants a clear purpose, reliable access, and a fast route for resolving ambiguity without altering the evidence.

Before

Brief the room

Confirm candidate build, role, data, case priority, evidence convention, and escalation route.

During

Protect observation

Let representative users interpret and act. Record confusion rather than coaching it away.

After

Close the loop

Resolve provisional outcomes, file evidence, assign defects, and publish the next state.

Always

Preserve build context

Every outcome must remain tied to its environment, data, role, time, and candidate version.

One shared language

Keep verdicts unambiguous.

P

Pass

The complete expected business outcome was observed and evidence is sufficient.

F

Fail

The observed result differs materially from the accepted outcome.

B

Blocked

The case could not reach a verdict because a prerequisite or dependency failed.

N

Not run

Execution has not started; it is not a proxy for blocked or deferred.

Field note

Report what changes a decision.

Progress by priority

Show critical journey execution and pass rate separately from aggregate totals.

Decision blockers

Name blocked journeys, unresolved critical failures, and missing ownership.

Evidence debt

Surface cases whose verdict exists but whose supporting record is incomplete.

Recovery forecast

State the next candidate, retest window, and decision point—not a vague confidence level.

Retest rule

A closed defect proves a fix was attempted. A passed journey proves the business outcome was restored.