First adoption step

Run one Reality Loop before the next serious commitment.

Bring one uncertain initiative. Materialize one candidate reality. Let stakeholders operate it. Capture what changed before scope, price, and engineering capacity harden.

This is not a training exercise or a generic discovery workshop. It is a first safe move: build enough to understand, capture the evidence, then decide whether to loop again, stop, broaden, or prepare a delivery baseline.

Session formats

The first session is sized to the risk, not the mythology.

90 minutesCommitment-risk triage

Name the initiative, map uncertainty, pick the first candidate reality slice, and choose who must experience it.

Half dayLoop planning and artifact setup

Draft the Build to Learn brief, prepare the decision log, and define what evidence would change the team decision.

One dayCandidate review and decision record

Review a candidate reality, capture observed discrepancies, record accepted behavior, and decide loop, stop, broaden, or baseline.

Workshop pathFirst loop to Freeze Gate

Use repeated loops to prepare a delivery baseline packet and Reality Check queue for a selected slice.

Who it is for

Use a first Reality Loop when a team is about to commit to a workflow, portal, modernization slice, AI-enabled process, service-management tool, or client delivery promise and still cannot safely explain what will happen when people operate the future system.

It is especially useful when scope seems agreed in meetings but the consequences of wrong scope would be expensive: rework, change orders, UAT conflict, user rejection, architecture churn, or a commercial promise the team cannot honestly price.

What to bring

One uncertain initiativeA workflow, portal, modernization slice, AI-enabled process, or client delivery commitment.
The commitment riskWhat happens if the team gets scope, rules, roles, or workflow order wrong?
Candidate reality sliceThe smallest executable interpretation that can expose meaningful disagreement.
Participants with consequencePeople who can operate, challenge, accept, or reject the candidate behavior.

What gets produced

RDD 01Build to Learn brief

Build to Learn brief

Names uncertainty, candidate slice, participants, constraints, and evidence needed.

RDD 02Reality Loop decision log

Reality Loop decision log

Captures accepted behavior, rejected alternatives, open risks, and next move.

RDD 03Freeze Gate baseline

Delivery baseline candidate

Prepares only if the slice has enough evidence to cross into engineering review.

Download the template collection

What not to expect

Do not expect a production estimate from unresolved intent.Do not treat the candidate reality as production software.Do not expect the first loop to settle every product question.Do not skip Reality Checks because stakeholders liked the workflow.